Sharing, teams and roles

In a company account the organisation holds billing, users and security settings. Each person has a personal space. A team is a shared space where members find and run agents and use team connectors. Gumloop suggests keeping most agents personal and creating teams only when several people maintain the same agents.

Roles on an agent

• Owner: can configure the agent (only Owners see the builder tabs).
• User: can run it and see their own tasks.

Team members get User access to team agents by default; being on a team does not let you edit. Owners can let Users create their own triggers, and can choose whether task history is visible to the team.

Whose accounts? By default every runner uses their own connected accounts ("user-owned"). Two shared options:

• Use Team Default: a team connector everyone uses, added by a team admin.
• Agent-owned credentials: everyone who can access the agent acts through one pinned account without seeing it. It must be explicitly enabled, may need admin permission, and can't be combined with public link sharing. Choose it deliberately: anyone with access can now act as that account.

Sharing options include specific people, teams, the whole organisation, or a public link. Skills and artifacts have their own sharing.

Continuity: plan for people leaving. Gumloop has guidance for keeping agents running and for claiming ownerless agents. Shared team agents with team connectors survive departures better than personal ones.

All users draw from one shared credit pool; teams affect access, not billing.