Skip to main content
Every agent carries its own access settings. They decide who can find it, who can put it to work, and who can change how it behaves. Open an agent’s ⋮ menu and choose Access to see and change them.

​
What access covers

Access comes in four roles, weakest to strongest: View, Use, Edit, Owner. Each role includes everything to its left. The agent’s creator starts as its owner. Someone can use an agent every day without being able to change how it behaves. That is the normal arrangement for a shared team agent.

​
General access

Every agent has a general-access level that applies to everyone in your workspace, and a separate one for people outside it. Use this to answer the broad question: should the whole workspace reach this agent, or nobody outside a short list? General access applies to everyone in the workspace by default. Fine-tune it with grants.

​
Grants to people and teams

When general access is too broad, grant a role to specific people or to teams. A grant gives one person (or every member of a team) the role you pick, on this one agent. Grants stack with general access: whoever has the highest role wins. Some examples:
  • A hiring agent used by recruiting only: no workspace access, then grants for the recruiting team.
  • A shared support agent the whole workspace can message, but only two people can edit: general access Use, plus Edit grants for those two.
  • An agent still being built: no access for the workspace, and View or Use grants for the people reviewing it.
Workspace owners and admins can always see, message, and edit every agent in the workspace, whatever its access settings.

​
People outside your workspace

Opening an agent beyond your workspace lets people without a Skydive account email or message it from their own channels. What they can do depends on the general-access level for people outside:
  • Use (the default): anyone who reaches it can message the agent.
  • Any other level: outsiders reach nothing.
A publicly reachable agent can be messaged by anyone who finds it, including unidentified senders over email or text. Use it for agents meant to face customers or the public, not for anything that touches private workspace data.

​
Managing access

Open the agent, click the ⋮ menu, and choose Access. The dialog lists general access and every person and team grant. Add someone with Share, pick their role, and changes apply immediately. Removing someone’s access stops them on their next view refresh. Access changes also send the affected person an email. Only the agent’s owner (or a workspace owner or admin) can open the Access dialog.

​
Sharing an agent

In the same ⋮ menu, choose Share for a link to the agent’s profile, plus a profile card you can download as an image. Whether a teammate can open the link follows their access: no access and the link shows nothing; View or above and it opens the agent.

​
Access and shared memory

Access and memory go together. Everyone who can message an agent draws on the same memory. A widely shared agent is a shared space: knowledge one person teaches it helps everyone. Keep private or sensitive details out of a shared agent, and keep the workspace level at View when the work itself shouldn’t be visible to the rest of the workspace.

​
What an agent itself can reach

Access governs people. What the agent can reach is a separate question, answered by the credentials you connect and the proxy that holds them.

Integration permissions

How credentials are scoped, and why the agent never sees a raw token.

Roles in your workspace

Owner, admin, and member, and what each can do.

Teams

Grouping people, and granting them agent access together.