Skip to content

Terminal > Knowledge & collaboration

Roles and permissions

Compare Warp team, workspace, and factory roles, check your access, and manage team admins.

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

A role defines what you can access and which actions you can take in Warp. Your effective permissions also depend on your plan, memberships, and applicable policies.

Team roles govern access and administration within a team. Enterprise workspace roles apply across teams. Factory roles determine who can run work and configure factories.

For example, an Enterprise workspace member who is an Engineering team admin can administer that team and its factories without workspace billing authority. A factory Editor can configure a factory without being a team admin.

In the Warp Factories web app, open the account menu and confirm the selected team. Your badge shows “Member,” “Admin,” or “Workspace admin.” A self-serve team owner also shows “Admin”; this badge does not distinguish ownership.

Admins can open Admin panel and inspect their entry in the team’s member list for the exact role. If your badge says “Member,” ask the person who invited you or a known team admin for help. If you cannot identify an admin, contact support. The Admin Panel is not a member-accessible directory.

RoleResponsibilitiesLimits
Team ownerAdministers a self-serve team and can transfer ownership to another memberExactly one owner per self-serve team; plan restrictions still apply
Team adminManages the team’s membership, invitations, and configurable settings; can add admins on supported plansCannot transfer ownership or change the owner’s role; does not automatically gain workspace administration
MemberUses team resources within the applicable policiesMembership alone does not grant team administration; factory access is determined separately

Adding an admin does not add or replace the owner. Enterprise ownership belongs to the workspace; teams created inside it do not require a team owner. See Workspace roles.

Additional admins are not limited to Enterprise. Standard plan support differs by product:

PlanAdditional team admins
FreeNot included
Build, Max, and BusinessSupported
EnterpriseSupported, with separate workspace and team roles
PlanOwnership and administrationFactory access
StartOne team with one owner; no additional admins in the standard planOwner inherits Admin; other members have Editor access
ScaleOne team with one owner; the owner and team admins can add adminsOwner and team admins inherit Admin; other members have Editor access
EnterpriseOne workspace owner; workspace owner and admins can add workspace admins; workspace admins and team admins can add admins for the relevant teamWorkspace admins inherit Admin on every team’s factories; team admins inherit Admin only on their team’s factories

Account-specific access can differ. If a role control does not match your expected access, confirm the selected team and plan with your owner or contact support.

You must already have administrative access to the team. The plan must support additional admins before you can promote a member.

  1. Open the Warp Admin Panel in a browser and open the team’s member list.
  2. On the member’s row, open the three-dots menu. Click Promote to team admin or Demote team admin.
  3. Complete any confirmation and check that the member’s role updates.

Admins with factory-role management access see an editable role column instead. To promote a member, choose Team Admin from their role dropdown. This changes team administration, not a factory role.

On standard Free or Start accounts, the promotion option is not shown. Adding purchased usage does not by itself establish that an account supports additional admins. Review the relevant plans before changing a subscription.

Workspace roles apply to Enterprise administration. Self-serve customers manage team roles instead. In an Enterprise workspace:

  • Workspace owner or admin - Is an admin of every team in the workspace, including teams they do not personally belong to.
  • Team admin - Administers only their team, without workspace-wide membership, settings, or billing authority.
  • Workspace member - Can have different team memberships and roles without becoming a workspace admin.

Changing an independent workspace role does not rewrite existing team roles. A demoted workspace admin can retain a separately assigned team-admin role.

See Workspaces for Enterprise teams for the workspace role definitions and procedures.

Factory user and Editor are factory-access roles, not team membership roles. Owners and admins inherit factory Admin access within their team or workspace.

A team-wide factory role can apply across the team’s factories. A factory-specific assignment applies to one factory; it does not change the person’s team or workspace role.

An Editor can attach an existing integration. Connecting a new shared integration or initiating delegated setup requires a team owner or admin on self-serve, or a workspace owner or admin on Enterprise. An Enterprise team-admin role alone is not enough. Personal account linking is separate.

See Managing factory permissions for factory capabilities, defaults, and overrides.

Team admins manage team settings and membership. Workspace admins additionally manage workspace-wide controls and inherit team administration. Available controls depend on the plan and any enforced workspace policies.

Where the plan includes spending controls, team admins set limits for their team and its members. Enterprise workspace owners and admins can manage those limits across the workspace’s teams. See Enterprise spending controls for usage caps and self-serve purchase limits for limits on additional purchases.

Viewing usage, purchasing usage, changing payment details, and managing subscriptions are separate actions. See usage visibility for reporting access and Managing factory plans and billing for browser billing routes.

Members use shared resources, configure permitted personal settings, and run work within the applicable policies and factory role. A Member role is not a promise of read-only access.

A team-admin role does not override a workspace policy or make a plan-locked setting editable. See How settings enforcement works for the difference.

This procedure applies to a self-serve team. Only the current owner can transfer ownership.

The previous owner becomes a Member and loses administration access. If the team supports additional admins and you still need that access, ask the new owner or another admin to grant it separately. If the new owner’s email is not on a work domain, Warp disables team discoverability.

  1. Open the Admin Panel in a browser, confirm the team, and click Teams.
  2. Find the existing member who will become the owner. Open their member-actions menu and click Transfer ownership. If the list uses an editable role column instead, choose Owner from that member’s role dropdown.
  3. In the confirmation, click Transfer. The page reloads with your updated access. Ask the new owner to confirm their Owner role.

In the Warp app, the alternative route is Settings > Teams, then the member’s three-dots menu > Transfer ownership.

For independent Enterprise workspaces, follow Changing workspace roles. Transferring workspace ownership does not transfer team roles.

Team roles are distinct from the controls on shared resources. For sharing policies, see the Admin Panel. Factory roles do not grant external repository permissions or permission to merge pull requests.

Confirm that you are administering the intended team and that its plan supports additional admins. Standard Free and Start accounts do not offer promotion.

In an Enterprise workspace, check whether you are changing a team role or a workspace role. Ask a workspace admin to handle workspace-wide changes.

Factory settings work, but administration access is denied

Section titled “Factory settings work, but administration access is denied”

Factory Editor access does not grant team or workspace administration. Ask an owner or admin to review the shared resource or setting you need. Do not create a second personal connection to work around a shared-integration permission failure.