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

# Invite to Workspace

> Information about workspace and project invites

## How to invite team members to your workspace?

<CardGroup cols={2}>
  <Card title="Workspace invite (Team)" icon="user-plus">
    Add people who need ongoing workspace access.
  </Card>

  <Card title="Project invite (Collaborators)" icon="users">
    Give access only to specific projects.
  </Card>
</CardGroup>

Workspace invites are managed in **Team**.
Project-level invites are managed in a project's **Collaborators** tab.

## Choose Member or Guest first

Choose role based on access scope:

* **Member**: Internal teammate who needs broad workspace access.
* **Guest**: External collaborator who needs access only to specific projects.

For full role behavior, see
[Workspace roles](/workspaces/roles-and-seats#workspace-roles).

By default, new users are assigned the **Reviewer** project role when invited to
a workspace. Workspace admins and project owners can change project roles to
**Contributor** when users need to publish and load models. Learn more in
[Project roles](/workspaces/roles-and-seats#project-roles).

## Invite from Team (workspace-level)

Use this path when someone needs ongoing workspace access:

<Steps>
  <Step title="Open Team">Open **Team** from the workspace menu.</Step>

  <Step title="Start invite">
    Choose the **Members** or **Guests** tab, then start an invite.
  </Step>

  <Step title="Send invite">Enter email addresses, select role, and send.</Step>
</Steps>

### Bulk inviting

Use bulk invite when adding many users at once.

<Steps>
  <Step title="Copy email list">
    Copy a list of emails to your clipboard. Emails can be separated by spaces,
    commas, or semicolons.
  </Step>

  <Step title="Paste once">
    Paste the list into the first email input in the invite modal.
  </Step>

  <Step title="Send invite set">
    Speckle splits the list into individual inputs so you can send in one pass.
  </Step>
</Steps>

### Invite to a single project

Use this path when someone should only access one project (or a small set).
Invite them as a Guest to keep access limited to invited projects. Learn more in
[Workspace roles](/workspaces/roles-and-seats#workspace-roles).

<Steps>
  <Step title="Open project">Open the target project.</Step>
  <Step title="Open Collaborators">Go to the **Collaborators** tab.</Step>
  <Step title="Send invite">Add the person and send the invite.</Step>
</Steps>

People invited from **Collaborators** always join as Guests.
If a person later needs broad workspace access, update role in **Team**.

## FAQ

<AccordionGroup>
  <Accordion title="With SSO enabled, do users still need an invite?">
    Existing workspace members can sign in with SSO without a new invite.
    First-time users still need an invite so they can be added to the workspace
    with a role before accessing projects.
  </Accordion>

  <Accordion title="Can I add a user without them accepting the invite?">
    No. A user must accept the invite before they are added to the workspace or
    project.
  </Accordion>

  <Accordion title="Why can't I directly add new users to a project without account setup and invite acceptance?">
    Speckle requires each collaborator to have their own verified account before
    access is granted. This keeps identity ownership, audit history, and access
    control traceable per user. To speed up onboarding, send invites in bulk
    from **Team** and ask users to complete account verification before project
    kickoff.
  </Accordion>

  <Accordion title="Why is inviting a user not working?">
    Check that you are a workspace admin, confirm the email is valid and not
    already pending, and verify whether domain protection or SSO rules are
    blocking the user.
  </Accordion>

  <Accordion title="I can invite to projects but not to workspace. Why?">
    Inviting people to the workspace requires workspace admin permissions.
    Project invitations can be done through **Collaborators** with project-level
    ownership permissions.
  </Accordion>

  <Accordion title="What if a user was denied through workspace discoverability?">
    Send a direct invite from **Team**. A denied discoverability request does
    not prevent a workspace admin from inviting that user directly.
  </Accordion>

  <Accordion title="Can a Guest be a Contributor on a project?">
    Yes. A Guest can be assigned the **Contributor** project role in projects
    where they are added as a collaborator.
  </Accordion>

  <Accordion title="Can a project collaborator become a workspace Member later?">
    Yes. People invited through **Collaborators** join as Guests first. A
    workspace admin can later change their workspace role to Member from
    **Team**.
  </Accordion>

  <Accordion title="Does changing workspace role remove existing project access?">
    Not automatically. Workspace role changes adjust default behavior, but
    explicit collaborator assignments on projects remain until changed.
  </Accordion>
</AccordionGroup>