Skip to main content
Invite a client or a teammate to only the websites they work on. They see those websites and their links, contacts, reports and tasks. They don’t see your other clients’ websites or the people who work only on those. You need the owner or admin role.

Invite someone to selected websites

  1. Open Settings, then Members, and choose Invite someone.
  2. Enter their email address.
  3. Choose a Role. Viewer can view websites and links. Member can also manage them. Admin can also manage people and settings.
  4. Under Websites, choose Selected websites and tick each website they need.
  5. Choose Send invitation. If the email can’t be sent, copy the code and send it yourself. The code appears only once and expires in 14 days.
They join by signing in with the same verified email address. A forwarded code lets nobody else in.

Check what they see

Website grants apply to the app, the API, the CLI and agent connections:
  • Websites, Links, Contacts, Reports, Changes and Home tasks show only their websites. Exports cover only their websites too. The full workspace export in Settings isn’t available to them; an API export covers one of their websites at a time.
  • Members lists only the teammates who share one of their websites, plus people with access to every website. A shared teammate’s websites show only the shared ones.
  • A not-found response can mean that a record is outside your access. It does not prove that the record never existed.
The workspace name and link tag names are shared across the whole workspace. Keep client names out of tag names when clients share a workspace.

Limits for an admin with selected websites

An admin limited to some websites can invite and manage people only inside those websites. They see only those invitations. On the Agent page they see their own API keys and agents, plus ones limited to their websites. They can’t change or remove people who reach other websites, including staff with every website. If invitation creation is refused with INVITATION_UNAVAILABLE, ask a workspace owner to review the request. The refusal does not identify a hidden member or invitation. Because the invitation is refused instead of sent, the refusal can still show that the address already has access or an open invitation.

Agents and API keys follow the person

Owners and admins create API keys and approve agents on the Agent page. A credential’s access is limited by its recorded grant and the person’s current membership. Project restrictions work on every plan, including without a subscription. If an older server returns PLAN_FEATURE_REQUIRED, keep the restriction and ask its owner to update the server. When a limited admin issues a new credential with All websites, it records that admin’s current website list. Later additions to the admin’s access do not widen that recorded list. Older credentials stored with an all-websites grant may widen with membership changes. Review those credentials and revoke/reissue them before relying on a fixed client boundary. Narrowing someone’s websites narrows their existing keys and agents on the next request. Removing them stops those keys and agents.

Change or remove access

In Settings, then Members, open the person’s actions menu:
  • Edit access changes their role or websites from the next request.
  • Remove from workspace removes them and stops their keys and agents.
  • Cancel invitation stops an unused invitation code from working.
To stop one agent or key without removing the person, revoke it on the Agent page.
  • The invitation expired or was cancelled. Ask an owner or admin for a new invitation.
  • The app asks for the email address the invitation was sent to. Sign in with that address, or ask for an invitation to the address you use.
  • A website is missing. Ask an owner or admin to add it under Edit access. A key or agent that recorded selected websites keeps them, so create a new key or approve the agent again to reach the added website.

Next step

To choose what each agent may do on those websites, see Choose scopes for the task. For how AgentLinkOps stores and separates your data, see Security and data.