Roles

For any enterprise or its workspaces, roles determine what its members can do. Customize your own or use the built-in roles predefined.

Roles define what members can do within your enterprise and its workspaces. In addition to the built-in roles, you can create custom roles with granular permissions tailored to how your organization operates.

Two scopes: enterprise and workspace

Roles exist at two levels, and the two sets of roles are distinct.

  • Enterprise roles govern access to enterprise-wide settings, billing, members, and the catalogs of shared resources (rulesets, tools, models, templates, and more).
  • Workspace roles govern access within a single workspace: its code, compliance state, docs, and membership.

Each member has one role at the enterprise level. Within an individual workspace, a member can be assigned a different role that applies only there. A member who is an enterprise Viewer might be a workspace Admin in the one workspace they own, for example.

Built-in enterprise roles

Seven roles are available by default at the enterprise level.

RoleSummary
OwnerFull control, including deleting the enterprise and managing owners
AdminEverything except deleting the enterprise or assigning the Owner role
Compliance OfficerApproves compliance decisions and reads findings and audit activity; cannot author rulesets
Ruleset ManagerAuthors and publishes enterprise rulesets; reads properties and workspace context
Billing AdminSubscriptions and payment methods only, no product configuration
MemberCan create workspaces and view enterprise-level information
ViewerRead-only access to the information they are granted

Owner has every enterprise permission. Only an Owner can delete the enterprise or grant the Owner role to someone else.

Admin has every enterprise permission except deleting the enterprise, and cannot assign the Owner role. In practice an Admin runs day-to-day administration: managing members and teams, configuring agents, tools, models, integrations, and secrets, and approving staged ruleset changes (enterprise.rulesets.approve) and compliance exceptions (enterprise.compliance.approve), not just viewing them.

Compliance Officer is the compliance governance role. It approves, rejects, and revokes compliance exceptions, decides finding challenges and break-glass reviews, and reads findings and the audit log across every workspace without any workspace content access. It can read rulesets, enterprise properties, and the workspace list so it understands what a decision applies to, but it cannot author or publish rulesets. That separation is deliberate: the people who judge exceptions are not the people who write the standards those exceptions bend.

Ruleset Manager is the standards authoring role. It creates, edits, and publishes enterprise rulesets and their applicability conditions (enterprise.rulesets.manage and enterprise.rulesets.approve), and reads enterprise properties and the workspace list so it can scope a ruleset to the right workspaces. It holds no compliance approval authority, so a Ruleset Manager cannot grant exceptions to the rules they wrote. Give a person both roles through a team grant or a combined custom role when one person genuinely does both jobs.

Billing Admin is a finance-focused role. It can view and manage billing, manage payment methods, and view usage, plus see the member list and browse the templates and modules catalogs so spend can be reconciled against who and what is consuming it. It has no access to enterprise settings, agent or tool configuration, secrets, or integrations.

Member is the standard role for people doing the work. A Member can create workspaces and has read access across most enterprise areas (members, teams, usage, rulesets, compliance, workflows, tools, models, agent configuration, integrations, settings, secret names, templates, and modules) but cannot change enterprise-level configuration. This role replaces the legacy "Editor" enterprise role; existing Editors are migrated to Member automatically.

Viewer is read-only and cannot create workspaces. It can see the member list, teams, usage, compliance state, and the templates and modules catalogs.

When a directory group mapping or an invitation could give one person more than one built-in role, the higher role wins, in this order: Owner, Admin, Compliance Officer, Ruleset Manager, Billing Admin, Member, Viewer. Custom roles never replace a built-in role this way.

Built-in workspace roles

Five roles are available by default within a workspace.

RoleSummary
OwnerFull control of the workspace, including deleting it
AdminManages workspace configuration and membership; cannot delete it
MaintainerEditor capabilities plus workspace rulesets, editable property values, and optional exceptions
EditorWorks in the workspace: edits code and docs; no settings or members
ViewerRead-only access to workspace content

Owner has every workspace permission except central compliance approval and is typically the person who created the workspace. Only an Owner can delete it.

Admin has every workspace permission except deleting the workspace and central compliance approval. Admins manage settings, the target branch, membership, rulesets, compliance, tools, workflows, secrets, and docs.

Maintainer is for the team that owns a workload without owning its membership or settings. It has everything Editor has, plus:

  • Workspace rulesets. Create, edit, and approve rulesets that live in this workspace (workspace.rulesets.manage and workspace.rulesets.approve). Enterprise rulesets stay with the Ruleset Manager.
  • Workspace-editable properties. Set the values of properties the enterprise has marked as editable by the workspace (workspace.properties.manage). Enterprise-controlled values stay read-only.
  • Optional exceptions. Apply, approve, reject, and revoke exceptions on optional rules in this workspace (workspace.compliance.exceptions.apply_optional), with a justification recorded under the Maintainer's name.

A Maintainer cannot change settings, manage members, or decide anything that needs central approval.

Editor can do the work without changing how the workspace is governed: view and edit content (Terraform code, canvas, plans and applies), manage docs, view and trigger compliance evaluations and submit exceptions for review (workspace.compliance.manage), and view rulesets, tools, workflows, secret names, members, and settings. Editors cannot change settings, manage membership, or approve ruleset or compliance changes.

Viewer has read-only access: view content, rulesets, compliance, tools, workflows, docs, members, and settings.

Who can decide a compliance exception

Exception authority is split by what the rule is, not by who owns the workspace.

  • Optional rules can be decided locally. Workspace Owners, Admins, and Maintainers grant, approve, reject, and revoke exceptions on optional rules in their own workspace. The same authority applies in the dashboard, the public API, and the MCP tools, and every decision carries the deciding person's name.
  • Required rules cannot carry a standing exception at all. A rule is required when the rule itself is marked required, or when the workspace has marked it required. A ruleset being required only controls whether it applies; an optional rule inside a required ruleset can still receive an exception.
  • Challenges and break-glass reviews always go to a central approver: an enterprise Owner, Admin, or Compliance Officer, or a custom workspace role that explicitly holds workspace.compliance.approve.

See Compliance for how requests, grants, and reviews work.

Access from a linked GitHub repository

When a workspace is linked to a GitHub repository, enterprise administrators can let the repository's own collaborator permissions grant workspace access. The setting lives in the enterprise Roles settings and applies to every GitHub-linked workspace in the enterprise.

SettingWhat a GitHub collaborator gets
OffNothing. Only Infracodebase roles grant access.
Grant workspace access from GitHub repository permissionsRead or Triage on the repository grants Viewer.
Let write access grant EditorWrite, Maintain, or Admin grants Editor; Read or Triage grants Viewer.
Let repository administrators grant MaintainerAdmin grants Maintainer; Write or Maintain grants Editor; Read or Triage grants Viewer.

A few things to know about how this works:

  • It only adds. Repository access never lowers a role someone holds through Infracodebase. People without repository access (subject matter experts, compliance reviewers, support) are invited through roles as usual.
  • It needs the person's own GitHub account. Access is checked live against the collaborator's linked GitHub identity, not the enterprise's app installation. Someone who has not connected their GitHub account gets nothing from this setting.
  • It fails closed. When GitHub cannot be reached, Infracodebase falls back to the last remembered read decision, which can grant Viewer but never Editor or Maintainer.
  • Administrator mapping is opt-in. Enabling it is a separate choice beneath the Editor setting. Existing enterprises keep their current behavior until an administrator turns it on.

Seeing where access comes from

A person's effective permissions in a workspace combine every grant that applies to them: a direct assignment, teams, directory groups, enterprise-level authority (an enterprise Admin can manage every workspace, a Compliance Officer can read every workspace's compliance state), and a linked repository under the setting above.

The workspace Members page explains this. The Your access card at the top lists each grant that applies to you and the combined capabilities they add up to. Your GitHub access is verified live for your own account only, so the card says when that check could not complete. In the members table, each member's role shows the other grants recorded for them, such as a team or enterprise authority, so a role label is never mistaken for the whole picture.

Removing someone's direct assignment removes only that grant. The confirmation names what they keep, or says access ends immediately when there is nothing else.

Permission domains

Permissions are the individual capabilities that make up a role. Each permission belongs to a domain (a feature area), and most domains expose a view permission plus one or more management actions (manage, approve, create, delete).

Enterprise permissions are organized into these domains:

DomainWhat it controls
billingSubscription tier, plan changes, and payment methods
usageUsage trends and spend breakdowns
membersMember list, invitations, removals, and role assignment
settingsEnterprise name, slug, feature flags, and enterprise deletion
teamsCreating teams and managing team membership
agentAgent tool permissions and deny/ask rules
rulesetsEnterprise rulesets, including approving staged changes
complianceCompliance settings, state, and exceptions
propertiesDefining workspace properties and their enterprise values
toolsConnectors and tool access
modelsModel selection and parameters
workflowsWorkflows available to the enterprise
secretsEnterprise-level secrets
integrationsVersion control connections and repository linking
workspacesCreating, viewing, managing, and deleting workspaces
templatesDiscovering and promoting workspaces as templates
modulesDiscovering and promoting workspaces as modules
auditThe enterprise audit log
tokensEnterprise access tokens

Workspace permissions are organized into these domains: settings, members, content, rulesets, compliance, properties, tools, workflows, secrets, and docs.

The rulesets and compliance domains exist at both scopes and carry view, manage, and approve actions. The approve action is separate on purpose: a member can be allowed to draft a ruleset or submit a compliance exception without being allowed to approve it. Workspace compliance adds a fourth action, exceptions.apply_optional, which decides optional-rule exceptions only and never stands in for approve. See Rulesets and Compliance for what those areas govern.

Custom roles

Custom roles let you define exactly what a member can and cannot do. Instead of fitting everyone into one of the built-in roles, you can create roles that match the way your teams actually work.

To create a custom role, go to your enterprise settings and navigate to the Roles section. Give the role a name, a description, and then select the permissions it should have from the domains above. A role can hold any combination of permissions, so you can make it as broad or as narrow as you need.

For example, you might create a "Security Reviewer" role that can view all workspaces and manage and approve rulesets but cannot edit content or change enterprise settings. Or a "Tool Administrator" role that can configure connectors (tools.manage) and manage secrets but has no access to billing or member management. Or a "Standards Lead" role that combines the Compliance Officer and Ruleset Manager permission sets for the one person who does both.

Custom roles appear alongside built-in roles when you invite members or change someone's role, and they work the same way at both the enterprise and workspace level. A custom role always shows under its own name, even when its permissions happen to match a built-in role.

Assigning roles

Roles are assigned when you invite a member or from the People page in your enterprise settings.

Role assignment is bounded by what the assigner already holds: you can only grant a role whose permissions are a subset of your own. This prevents privilege escalation: a member with members.roles.assign cannot promote someone into a role that holds permissions the assigner lacks. It is also why only an Owner can grant the Owner role.

Access tokens

The same permission catalog is used by enterprise access tokens, so any permission you can grant to a role can also be stamped onto a token for CI or automation use. Scope tokens to the narrowest set of permissions the job requires. Exception decisions are the one thing a token cannot do on its own: they are recorded under a person's name, so they need a signed-in user or a personal access token.

Best practices

  • Start with built-in roles and create custom roles only when the defaults do not match your access requirements.
  • Use Billing Admin for finance staff rather than granting full Admin just to manage the subscription.
  • Keep standards and approval apart. Give Ruleset Manager to the people who write rules and Compliance Officer to the people who judge exceptions. Combine them deliberately, not by default.
  • Use Maintainer for workload owners. It lets a team run its own rulesets, properties, and optional exceptions without handing them membership or settings.
  • Separate approve from manage on rulesets and compliance when you want a review step, so one role drafts changes and another approves them.
  • Name roles after their function, not after teams or individuals. "Security Reviewer" is more durable than "Sarah's Role".
  • Keep the number of custom roles manageable. A handful of well-defined roles is easier to maintain than dozens of highly specific ones.
  • Review permissions periodically as your organization's needs change.