Organizations & roles

An organization (also called a workspace, or tenant internally) is the container for everything you do in Delegate: its agents, members, skills, connected integrations, budget, and billing. Every agent and task belongs to exactly one organization, and data is isolated between organizations.

How organizations are created

The first time you sign in, Delegate creates an organization for you and makes you its Admin. You can rename it and fill in its details from the Organization area (visible to admins).

You can belong to more than one organization — for example, your own and a client's. Use the organization switcher near the top of the left sidebar to move between them. Your role is per-organization, so you might be an Admin in one and a User in another.

Roles: User and Admin

Each member has one role within a given organization: User or Admin. Separately, every agent has an owner, and can be shared with colleagues as a Viewer or Editor — that's a different axis from the role below, and it's covered in Sharing an agent.

Capability	User	Admin
Create, configure, and run agents	✅	✅
Use tools and attached skills	✅	✅
Manage their own profile and preferences	✅	✅
Switch between organizations they belong to	✅	✅
Open the Organization settings area	—	✅
Invite, edit, and remove members; set roles	—	✅
Control who is allowed to join the organization	—	✅
Set the organization's default bootstrap instructions & company identity	—	✅
Govern skills (visibility scope, authoring, status)	—	✅
Manage available models	—	✅
View usage & spend, and set budgets	—	✅
Manage the subscription and billing	—	✅
Manage integrations (GitHub, Slack, …)	—	✅

In short: Users get work done with agents; Admins also run the organization.

Admins can also open any agent in the organization, whether or not it was shared with them. For the full picture of how organization roles and per-agent access combine, see Who can do what; for the exhaustive list, Permissions reference.

What admins manage

The Organization area (left nav, admins only) groups these settings:

• General — organization name and ID, default bootstrap instructions (guidance sent to every agent on its first task session), company identity (shared context all agents can reference), and support access.
• Integrations — connect shared services such as GitHub, Slack, Google Workspace, and DocWorker, and register custom tools.
• Users — invite members, edit them, change roles, and remove access.
• Skills — govern reusable skills across the organization (visibility, who may author them, status).
• Models — control which AI models are available.
• API Keys — bring your own Anthropic/OpenAI key so eligible models run on your account.
• Usage & Spend — review token usage and cost per agent and per model.
• Budget — hourly, daily, and monthly limits enforced on every task.
• Billing — manage the subscription and view invoices.

Custom tools and integrations

Organization → Integrations is where you connect the outside world to your agents. Alongside GitHub and Slack, you can register custom tools — your own HTTP or MCP endpoints that agents can call — and review the organization's egress allow-list, which controls the hosts those tools are permitted to reach. See Custom tools and Connections.

If you're building agents into your own product, the Building an integration guide covers this end to end.

Adding members

Admins add members from Organization → Users. You can also control who is allowed to join via an email allowlist, so only approved accounts can be added to the organization. See Members & access.

tip

Not sure who can do what? Ask any agent — it can search this documentation and explain roles, or point you to the right Organization setting.