Skip to main content
Every check against an agent asks one of two questions:
  1. Can this user reach the agent? Chat with it, see it in a catalog, read its details.
  2. Can this user change or destroy it? Update its config, delete it, view or rotate its secrets, change who can reach it.
Only the agent’s owner or a superuser can update, delete, or manage the secrets of an agent. On Nasiko Cloud and on a self-hosted Enterprise server, a user with the admin role can also change who reaches it, rename it, and transfer its ownership. Making an agent public or sharing it with an org unit hands out no management rights.
A deleted agent is denied to everyone. No ownership, grant, or public flag overrides a deletion.

What grants view and chat access

A user can reach an agent if any of these is true: Grants are additive. An agent can stay privately owned and still be reachable by a whole org unit.
Plans: Pro and Enterprise. Self-hosted: Enterprise license.
The org unit and organization rows apply on Pro and Enterprise. A self-hosted open-source server decides access by ownership, is_public, and per-user grants. On the Nasiko Cloud Free plan, making an agent public, sharing it with an org unit or the whole organization, and transferring its ownership are refused with a prompt to upgrade. Public agents are available from Individual up. A coding agent’s harness agent belongs to one user. It can’t be shared, made public, or given to another owner, and attempts return 409 with "code": "agent_not_shareable".

Managing grants

In the dashboard, open the agent and use its Access tab to share it with users and agents or make it public. The Access tab works on every plan and on a self-hosted server. On Pro and Enterprise, and on a self-hosted Enterprise server, the tab also shows how many org units, and whether the whole organization, can use the agent.
Plans: Enterprise (dedicated or self-managed). Self-hosted: Enterprise license.
The nasiko-ee access commands below are part of the admin CLI for Enterprise deployments. From that CLI:
--user (-u) and --agent (-a) repeat and combine with --public in one call. --agent <other-agent-id> shares this agent with another agent, so the other agent lists it among the agents it can reach (access accessible-agents <other-agent-id>). This is an access grant, not the agent-to-agent allowlist that limits which agents an agent may call. On a self-hosted open-source server, the agent’s Access tab and POST /api/agents/{id}/grants/agents manage the agent-to-agent allowlist instead. See Agent access API. Inspect current access:
user-agents works for users you can see: an admin sees everyone, and a manager sees the people in their units.

Example: share with one user, private otherwise

The agent stays private, and that one user can chat with it.

Managing an agent

These require ownership, the admin role, or superuser. View or chat access isn’t enough:
The new owner must be an active user who doesn’t already own an agent with the same name. A harness agent can’t be renamed. Updating, deleting, and managing an agent’s secrets need ownership or superuser. See secret management. API reference: Agent grants API.