Skip to main content
Agents have exactly two roles: Owners manage the agent, Users run it. Everything on this page is configured from the Access tab of the agent.

​
Owner vs. User at a glance

As an Owner you tune exactly what Users can see and what they can create on the agent — and you can add as many Owners as you like to share that control.
Access tab showing Owners, Users, General Access, File Sharing, Task Visibility, and User Permissions

​
Give someone access

Everyone below is added from the Share button at the top of the agent, which opens the Share This Agent modal. The same controls also live in the Access tab of the agent configuration.
Share → type their email in Add people → pick the role next to the Share button → Share.
  • Can manage this agent = Owner
  • Can use this agent = User
A direct email grant sticks: it keeps working even if General Access is lowered later.

​
User permissions

Per-agent switches that control what Users see and what they can do with the agent. Owners always see everything.
User Permissions section listing the per-agent User settings, each set to Show or Hide
Three rules worth remembering:
  • Visible is not editable. Showing the instructions lets a User read the prompt, never change it.
  • Hiding something does not disable it. Hide Connectors and the agent still uses Gmail — the User just doesn’t see it listed.
  • Permissions are per agent, not per person. Everyone with User access gets the same view.
Out of the box every visibility setting is Show, and Create triggers and Make a copy are Allow. Organization admins can ship different defaults with Agent Default Settings.
If you switch Create triggers to Don’t allow while Users already have triggers, Gumloop asks what to do:
  • Keep running — they keep firing. Users cannot create, edit, or activate triggers, but can still view, deactivate, and delete their own.
  • Disable them — they are switched off.
Owners can still manage those triggers from the Triggers tab. Allowing creation again does not reactivate disabled triggers.
When Make a copy is allowed, a User can duplicate the agent and becomes the Owner of their copy. The copy carries the whole configuration — instructions, model, connectors, skills, knowledge, subagents — even the parts your visibility settings hide from them, so treat copying as a separate decision from what a User can see. Turn it off if the agent’s setup should not leave your control.Copying applies to the custom agents you build. Gumball and Gumloop’s built-in agents cannot be copied, and an organization custom role that restricts agent modification blocks copying too.
Example setup — an internal support agent everyone talks to: General Access Organization, Show Instructions Hide, Show Connectors Show, Create triggers Don’t allow.

​
Task Visibility

A task is one conversation with the agent.
Task Visibility section with the dropdown open, showing Their tasks only and Team tasks
  • This setting only exists on team agents, and new team agents default to Team tasks.
  • On a personal agent, Users see only their own tasks, so the setting is hidden.
  • Owners always see every task on either kind of agent, and any task can also be shared separately.
Task access normally includes task-linked artifacts, but a password-protected file may still require an unlock unless you have password-free file access. It never grants access to another person’s private persistent workspace files.

​
File sharing

Default behavior sets sharing for every file the agent generates.
File Sharing section with the Default behavior dropdown open, showing Default, Organization, and Anyone
These defaults apply to new files only. A file’s team, organization, public, or password-based access grants viewing access, not editing access. Invite an Editor to the file separately when someone needs to manage it. See Agent artifacts (files).

​
Requesting and claiming access

A User who needs to manage the agent opens the ⋮ menu in the agent header and chooses Request Owner access, then picks which Owner receives it. That Owner approves or denies it from their inbox. See Request Owner Access.
If an agent’s Owners are unavailable, an organization admin in the same organization can manage it through administrative access and claim durable ownership. Claiming does not require every existing Owner to be gone: it changes the canonical creator and adds an Owner grant, and existing Owners remain. See Claim an ownerless agent.
Organization admins can reach any agent in the organization through their admin override, even without a grant. Admin access is not the same as being an Owner — that’s why Claim Ownership exists.

​
FAQ

They no longer apply to agents. An editor becomes an Owner; a viewer or use-only person becomes a User whose visibility you tune with User Permissions. Skills still use Editor, Viewer, and Use Only. See Sharing a skill.
No. Show Instructions grants read-only access. Editing the agent requires Owner access.
Not today. User Permissions are per agent, not per person. If one person needs more, make them an Owner, or make a copy of the agent with different settings.
An agent always needs someone who can manage it. Add a second Owner first, then demote or remove the original.
An organization admin can open it and use Claim Ownership to take it over.

Agents

The agent builder, tab by tab.

Agent triggers

Who can create triggers, and what happens when you turn that off.

What can a User see on my agent?

Quick answer with the eight settings.

Sharing roles

Owner vs User, and roles on skills.