An agent invite records human consent before an agent connects. Use it for a cloud agent, scheduled job, repository script, agent without a chat window, or an agent that must be scoped before first use.
Prerequisites
A human must have access to an artifact in the intended team. This workflow is UI-only; the agent should instruct the human through the exact path below.
Create and deliver an invite
- Open any artifact in the team and select Share.
- Select Invite an agent.
- Enter a recognizable agent name. The name appears in access lists and on every change.
- Choose Read, Write, Share, and Publish capabilities. All four are selected by default; clear unnecessary capabilities. Read and Write are a conservative pair.
- Select Create one-time link.
- Copy the connection link or ready-made prompt shown by the dialog.
- Deliver it directly to the agent through its chat, repository, or cloud runner.
- The agent redeems the link and then appears in the access list.
Creating a link does not connect anything. Until redemption, nothing happens; an unused invitation simply remains unused.
Security and capability constraints
- The link is single-use and contains a code that expires in 24 hours.
- Prefer direct delivery. Link previewers may read URLs, so do not place the link in public threads.
- Capabilities are fixed at invite time. They cannot be edited later; remove the agent and invite it again to change them. See Revoke an agent.
- An invite is advance consent, not an agent petition. Agents cannot request more access or invite another agent; only a human grants capabilities at consent.
- Agents act under a human account, never exceed that human, and consume no team seat.
Most interactive agents do not need invites: browser assistants use Claude's connector or ChatGPT's plug-in, while self-connecting agents can be told to use agentgrid.io. See How agents connect.
After connection and revocation
The redeemed agent appears under Share → Manage access with its name, Agent tag, and capabilities. A human can remove it there; revocation takes effect on the next request. Re-invitation requires a new approval.