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

# Invite Team Members, Assign Roles, and Control Access

> Add team members to your Labrador projects, assign roles, and control what each person can see and do across your accessibility audits.

Labrador is built for team-based accessibility auditing. On Plus and Enterprise plans, you can invite colleagues directly into a project, assign each person a role that matches their responsibilities, and work through audits together in real time, without passing spreadsheets back and forth or managing access outside the platform.

<Info>
  Team collaboration, including invites and role management, is available on Plus and Enterprise plans only. Free and Core plans support a single user per account.
</Info>

## Inviting a Team Member

When you invite someone to a project, Labrador sends them an email with a link to join. If they don't already have a Labrador account, they'll be prompted to create one before accessing the project.

<Steps>
  <Step title="Open your project">
    From the Projects dashboard, click the project you want to add a team member to.
  </Step>

  <Step title="Click the Teammates button">
    Find the **Teammates** button in the project view and click it to open the team management panel.
  </Step>

  <Step title="Enter the team member's email address">
    Type the email address of the person you want to invite into the invite field.
  </Step>

  <Step title="Select their role">
    Choose the role that matches what you want them to be able to do on the project. See [Roles and Permissions](#roles-and-permissions) below for a description of each option.
  </Step>

  <Step title="Send the invitation">
    Click **Invite**. The team member will receive an email invitation to join Labrador and access the project.
  </Step>
</Steps>

## Roles and Permissions

Labrador gives you three roles to choose from when inviting a team member. Assign the role that reflects what each person actually needs to do, this keeps audit data accurate and prevents accidental changes.

<CardGroup cols={3}>
  <Card title="View-only" icon="eye">
    Can view all project content, criteria results, logged issues, and comments, but cannot make any changes. Ideal for clients or stakeholders who need to review findings without editing anything.
  </Card>

  <Card title="Developer" icon="code">
    Can update the remediation status on issues and leave comments, but cannot modify criterion results or project settings. Designed for developers who are tracking and resolving reported issues without needing edit access to the audit itself.
  </Card>

  <Card title="Editor" icon="pen-to-square">
    Full access to create and edit pages and components, evaluate audit criteria, log issues, manage custom fields, and update project settings. Use this role for auditors and team leads.
  </Card>
</CardGroup>

<Tip>
  When in doubt, start with the most restrictive role that still lets the person do their job. Use the **Developer** role for teammates who only need to update remediation status and leave fix-related comments, they won't accidentally alter your audit results or criterion assessments. You can update a team member's role at any time from the Teammates panel.
</Tip>

## Team Seat Limits by Plan

The number of people you can add to your projects depends on your Labrador subscription. Here's how each plan compares:

<Tabs>
  <Tab title="Free">
    The Free plan supports a single user only. You cannot invite team members or share project access on this plan. It's suited for running a full audit solo, with one active project slot at a time.
  </Tab>

  <Tab title="Core">
    The Core plan also supports a single user. While it unlocks Jira integration and three new projects per month, it does not include team invites or collaborative features.
  </Tab>

  <Tab title="Plus">
    The Plus plan is priced **per seat at \$55/month** and includes full team invite and management capabilities. Add as many seats as your team needs, each seat covers one team member across your projects.
  </Tab>

  <Tab title="Enterprise">
    The Enterprise plan includes **unlimited team seats** under custom pricing. It also adds SSO, dedicated support, personalized onboarding, and custom integrations for larger organizations.
  </Tab>
</Tabs>

For a full breakdown of what each plan includes, see the [Plans and Pricing](/plans-and-pricing) page.

## Removing a Team Member

If someone no longer needs access to a project, you can remove them at any time from the Teammates panel.

<Steps>
  <Step title="Open the Teammates panel">
    Navigate to the project and click the **Teammates** button to open the team management panel.
  </Step>

  <Step title="Remove the team member">
    Locate the team member you want to remove and select the option to remove them from the project.
  </Step>
</Steps>

Removing a team member revokes their access to the project immediately, they will no longer be able to view or interact with any project content. However, their historical contributions remain intact. Issues they logged, comments they left, and criterion results they recorded are all preserved in the project exactly as they were.

<Warning>
  Removing a team member cannot be undone from within the project. If you need to restore their access, you'll need to send a new invitation and reassign their role.
</Warning>