> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armature.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing your Armature team and invitations

> Invite team members, assign roles, and manage pending invitations in your Armature workspace. Admins and owners can invite by email or shareable link.

Armature organizes users into workspaces. Every workspace has a set of members, each assigned a role that determines what they can see and do. Admins and owners can invite new members either by sending an email invitation or by generating a shareable link. Role permissions are enforced across all parts of the product — workflows, runs, tool monitors, MCP servers, alerts, and settings.

## Roles

Armature has four roles. Roles are cumulative: each role inherits all permissions of the roles below it.

| Action                                      | Viewer | Editor | Admin | Owner |
| ------------------------------------------- | :----: | :----: | :---: | :---: |
| View workflows, runs, servers, and monitors |   Yes  |   Yes  |  Yes  |  Yes  |
| Create and edit workflows                   |    —   |   Yes  |  Yes  |  Yes  |
| Trigger workflow runs                       |    —   |   Yes  |  Yes  |  Yes  |
| Apply workflow changes                      |    —   |   Yes  |  Yes  |  Yes  |
| Sync MCP server capabilities                |    —   |    —   |  Yes  |  Yes  |
| Invite and manage team members              |    —   |    —   |  Yes  |  Yes  |
| Revoke pending invitations                  |    —   |    —   |  Yes  |  Yes  |
| Manage billing and subscription             |    —   |    —   |   —   |  Yes  |

### Role descriptions

**Viewer** — Read-only access. Viewers can browse workflows, inspect past runs, review tool monitor history, and view MCP server configurations, but cannot make any changes.

**Editor** — Can create and edit workflows, trigger runs on demand, and apply proposed workflow changes. Suitable for engineers who own workflows day-to-day but do not need to administer the workspace.

**Admin** — Everything an editor can do, plus the ability to sync MCP server capabilities, invite new team members, and revoke pending invitations. Suitable for tech leads and platform engineers who manage the workspace configuration.

**Owner** — Full access including billing management. There is exactly one owner per workspace. The owner role cannot be assigned via invitation; ownership can only be transferred by contacting Armature support.

<Note>
  API keys are frozen to the creator's role at the time of creation. If you change a member's role after they have created API keys, those keys continue to enforce the original role until revoked and recreated.
</Note>

## Inviting team members

Only admins and owners can send invitations. If your current role is viewer or editor, the **Team** section shows your role but does not display the invitation form.

<Steps>
  <Step title="Go to Settings → Team">
    Open **Settings** in the sidebar and select **Team** from the section navigation.
  </Step>

  <Step title="Choose an invitation method">
    Armature offers two ways to invite someone:

    **Email** — Enter the recipient's email address. Armature sends them an invitation email with a link to join the workspace.

    **Link only** — Generate a shareable invitation URL without an associated email address. Anyone who has the link can use it to join before it expires. Copy the link and share it through your own channel (Slack, a password manager, etc.).

    <Tip>
      Use email invitations when you want a specific person to join and an audit trail linking the invite to their address. Use link-only invitations for bulk onboarding or when email delivery is unreliable.
    </Tip>
  </Step>

  <Step title="Set the role">
    Select the role the new member will have when they accept the invitation: **Viewer**, **Editor**, or **Admin**. You cannot invite someone as Owner.
  </Step>

  <Step title="Send or create the invitation">
    * For email invitations, click **Send invite**. Armature sends the email and the invitation appears in the pending list below. If email delivery fails, the invitation is still created and the invite link is shown so you can copy it manually.
    * For link-only invitations, click **Create link**. Copy the invite URL immediately — it is shown once in the dashboard. Store it somewhere secure before sharing.
  </Step>
</Steps>

## Pending invitations

The invitations table lists all outstanding invites, with the following information:

| Column           | Description                                                                               |
| ---------------- | ----------------------------------------------------------------------------------------- |
| **Email / type** | The email address the invite was sent to, or "Link-only invite" for address-free invites. |
| **Status**       | `Pending` (not yet accepted), `Accepted`, `Revoked`, or `Expired`.                        |
| **Role**         | The role that will be assigned when the invite is accepted.                               |
| **Created**      | When the invitation was created.                                                          |
| **Expires**      | When the invitation link stops working.                                                   |

## Revoking an invitation

Click **Revoke** next to any pending invitation and confirm. The invitation link stops working immediately. Members who have already accepted the invitation are not affected — revoking only prevents the link from being used again.

<Warning>
  Invitation links do not expire instantly when revoked, but Armature validates revocation status on acceptance. A revoked link will be rejected even if someone clicks it before the server processes the revocation.
</Warning>

## Removing a member

Member removal (offboarding an existing workspace member) is handled through Armature support. Revoking their API keys in **Settings → API keys** immediately cuts off programmatic access while the offboarding is in progress.