Skip to main content
The Team & Roles page lets you share your agent’s dashboard with other people without handing over your whole account. Each person you add is a collaborator, and each collaborator gets a role that decides, page by page, whether they can view or edit — or see nothing at all. Find it on the dashboard at Team in the sidebar.
This page and the API Keys page are always owner-only — they can never be granted to a collaborator, no matter the role. Managing who has access, and issuing programmatic keys, stays with you.

​
How access works

  • Collaborators sign in with their own Agentheya account and open your agent from their own dashboard — you never share a password.
  • A collaborator’s role is a set of per-area permissions. For each dashboard area the role grants one of: no access, View (read-only), or Edit (read and change).
  • View covers reading a page; Edit covers anything that changes it (saving, sending, deleting). A collaborator only ever sees the pages their role grants.
  • Everything is scoped to this one agent. A role and its grants never leak to your other agents.
Team & Roles is a plan-gated feature. On a plan that doesn’t include it, the page shows an upgrade banner instead of the controls below.

​
Collaborators

The Collaborators card lists everyone with access to this agent. The counter next to the title shows how many seats you’ve used against your plan’s limit. Each row shows:

​
Adding a collaborator

Click Add collaborator, enter an email, and pick a role. What happens next depends on whether that email already has an Agentheya account:
  • They already have an account → access is granted immediately and the row shows Active.
  • They don’t yet → a Pending row appears and they get a one-time invite email. The link lets them set up an account (email + password, or Google / Microsoft / Okta), and the role you chose applies the moment they accept. Invite links expire after 7 days — use Resend invite to send a fresh one.
The seat count includes pending invites, because the grant exists the instant you add someone. If you hit your plan’s collaborator limit, remove an unused invite or upgrade to add more.

​
Managing collaborators

  • Change a role — pick a different role from the row’s dropdown; it takes effect right away.
  • Resend invite — shown only on Pending rows; re-sends the invite with a fresh link (counts against your invite-email quota).
  • Remove — revokes access. You’ll be asked to confirm; removal is final.

​
Roles

A role is a named bundle of per-area permissions. There are two kinds: built-in roles that cover the common cases, and custom roles you define yourself.

​
Built-in roles

Four ready-made roles ship with every agent. They can’t be edited or deleted, but you can duplicate any of them as a starting point for a custom role.
No built-in role includes Designer Chat (the AI Designer). Because the Designer can change almost every setting, that area is left out of the presets — grant it deliberately, and only through a custom role.

​
Custom roles

Click Create custom role (or duplicate a built-in one) to open the role editor. Give the role a name (up to 40 characters) and an optional description, then set the access level for each area: None, View, or Edit. Each group has bulk None / All view / All edit shortcuts. A custom role isn’t fixed once created — re-open it from its Edit (pencil) action any time to adjust its permissions, and duplicate any role, built-in or custom, to spin up a variant without starting from scratch. You can keep up to 20 custom roles per agent. Areas are grouped the same way the sidebar groups pages:
Some areas are flagged sensitive in the editor — grant them with care:
  • Designer Chat — the AI Designer can modify almost every agent setting, so this grant is close to full edit access.
  • Pricing — sets subscriber pricing tiers (Stripe Connect setup itself stays owner-only).
  • Connectors — MCP / OpenAPI / Composio connections and their credentials.

​
Deleting a role

You can delete a custom role from its row. If any collaborator is still assigned that role, deletion is blocked — reassign those people to another role first, so nobody is silently left without access.

​
In practice

Bring on a copywriter. You want someone to sharpen the agent’s Purpose, Rules and knowledge without touching billing or integrations. Add them with the Content Editor role — they can edit the content pages and test in Preview, and never see Pricing, Connectors or Users. Hand off day-to-day support. Your support lead should work the inbox and manage subscribers but shouldn’t redesign the agent. Give them Support Agent — Conversations, Users and Handoff editing, read-only logs, and can test in Preview — nothing else. Let a contractor wire up an integration, then lock it back down. Add them as Integrations Manager while they connect a CRM and configure channels. When the work is done, switch their row to Analyst (Read-only) or Remove them entirely. Grant exactly one page. You want an analyst who only ever sees Monitoring. Create a custom role with View on Monitoring and None everywhere else, and assign it — they land on Monitoring and can’t reach anything more.