Roles and permissions

The built-in roles, custom roles, per-workspace roles and exactly what each permission allows.

Every person's access comes from roles. A role is a set of permissions, and GraphKit checks the permission on the server for every request, whether it comes from the web app, the API, Kit, Autopilot or an MCP client. Team members are free: only connected accounts use seats.

To invite people, change their roles or remove them, see Members.

Where roles apply

There are two kinds of role:

  • Organization roles apply to the organization and to every workspace in it. Owner and Manager are built in, and you can create your own.
  • Workspace roles apply to one workspace. Admin, Operator, Inbox agent and Viewer are built in, and you can create your own.

One person can hold different workspace roles in different workspaces. For example, someone can be Admin of client A, a custom Reviewer in client B, and have no access to client C. Agencies usually give their own staff an organization role and give client staff workspace roles.

If someone has both an organization role and a workspace role, they get everything either role allows in that workspace. A second role never takes access away.

Built-in roles

RoleWhereTypical person
OwnerOrganizationWhoever owns billing and security. Can do everything.
ManagerOrganizationAccount managers who run every client. Everything except billing changes, buying infrastructure, the security policy and managing owners.
AdminWorkspaceThe client's own lead, or the admin of a direct workspace.
OperatorWorkspaceSomeone who builds and runs campaigns.
Inbox agentWorkspaceSomeone who only answers replies (an SDR or a setter).
ViewerWorkspaceSomeone who watches results, such as a client stakeholder.

You cannot edit the built-in roles. Clone one to start a custom role from it.

Custom roles

Open Organization → Roles and choose Create role, or Clone on any role. Pick the scope (organization or workspace), name the role and tick its permissions in the matrix. Each row is an area (sending accounts, leads, campaigns, inbox, and so on), and each tick is one action in that area.

  • A workspace role can only hold workspace permissions. Billing, branding, seats, roles, the security policy and workspace management belong to organization roles.
  • Deleting the organization and managing owners belong to owners only and are never part of a custom role.
  • Everyone can always open the workspaces they belong to and see the organization's name.
  • When you edit a role, everyone who holds it gets the new permissions on their next request.
  • You cannot delete a role while anyone holds it. Give those people another role first. Pending invitations for a deleted role are cancelled.

Creating, editing and deleting roles needs Manage roles (Owners and Managers have it).

No one can give more than they have

GraphKit stops people from handing out access they do not have themselves:

  • You can only assign a role, or create or edit one, if you hold every permission in it.
  • You can only change, suspend or remove someone if you hold every permission they have. A Manager cannot change an Owner, and a workspace Admin cannot change an organization member.
  • Nobody can change their own role, suspend themselves or remove the last owner. Owners hand over with Transfer ownership (see Members).

Permission matrix

This table is generated from the permissions GraphKit enforces.

AreaPermissionOwnerManagerAdminOperatorInbox agentViewer
Workspaces and organizationSee the organization (organization.read)YesYesYesYesYesYes
Workspaces and organizationOpen the workspace (workspace.read)YesYesYesYesYesYes
Workspaces and organizationAgency overview (organization.overview)YesYes
Workspaces and organizationManage workspaces (workspaces.manage)YesYes
Workspaces and organizationDelete the organization (organization.delete)Yes
Sending accountsView (senders.read)YesYesYesYesYesYes
Sending accountsConnect and configure (senders.connect)YesYesYes
Sending accountsRemove (senders.remove)YesYesYes
InfrastructureView (infrastructure.read)YesYesYesYesYesYes
InfrastructureConfigure (infrastructure.manage)YesYesYes
InfrastructureBuy and renew (infrastructure.purchase)Yes
LeadsView (leads.read)YesYesYesYesYesYes
LeadsAdd and edit (leads.import)YesYesYesYes
CampaignsView (campaigns.read)YesYesYesYesYesYes
CampaignsEdit (campaigns.edit)YesYesYesYes
CampaignsLaunch (campaigns.launch)YesYesYesYes
InboxRead (inbox.read)YesYesYesYesYesYes
InboxReply (inbox.reply)YesYesYesYesYes
InboxRead private (inbox.read_private)YesYesYes
Analytics and exportsView analytics (analytics.read)YesYesYesYesYesYes
Analytics and exportsExport data (data.export)YesYesYesYesYesYes
Kit and AutopilotUse Kit (kit.use)YesYesYesYesYesYes
Kit and AutopilotRun Autopilot (autopilot.manage)YesYesYesYes
IntegrationsManage integrations (integrations.manage)YesYesYes
DevelopersAPI keys (api_keys.manage)YesYesYes
DevelopersWebhooks (webhooks.manage)YesYesYes
MembersManage members (team.manage)YesYesYes
MembersManage roles (roles.manage)YesYes
MembersView audit log (audit.read)YesYesYes
MembersManage owners (owners.manage)Yes
SecuritySecurity policy (security.manage)Yes
BillingView billing (billing.read)YesYes
BillingManage billing (billing.manage)Yes
BillingAllocate seats (seats.allocate)YesYes
BrandingManage branding (branding.manage)YesYes

Asking for something in a workspace you belong to without the permission returns "forbidden". Asking for something in a workspace you do not belong to returns "not found", so its existence is not revealed.

Kit, Autopilot and MCP

Kit acts as the person using it, with exactly their permissions. If their role lacks a permission, Kit says so and stops. Consequential actions (sending, deleting, inviting, API keys, billing) still ask for approval. Autopilot acts with the permissions of the person who turned it on. MCP clients act as the person who connected them. Roles, the security policy, members' sessions and ownership can only be changed by a person in the app, never by Kit or a connected app.

Limit a teammate's inbox

An admin can limit a workspace member's inbox to some accounts, for example so each rep sees only their own LinkedIn conversations. Organization roles are never limited. See Unified inbox.

API keys

API keys belong to a workspace, carry their own scopes, and act on behalf of the person who created them: a key stops working while its creator is suspended or after they are removed. Create them in Settings → API keys (needs API keys). See Authentication.

On this page