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

# Add and manage users

> Invite a colleague, choose their role, resend or withdraw an invitation, change a role or remove a user — and the few things Beacon will not let anyone do.

Your company's admins add and manage users on **Settings → Users & permissions**. You can also open it from your account menu.

If you are not an admin, the page shows only your own row and tells you to ask an admin on your team.

This guide covers the **Company users** tab. Linking each user's Slack and HubSpot accounts has its own guide: [Linked accounts](/linked-accounts).

## Invite a user

<Steps>
  <Step title="Choose Invite user">
    On the **Company users** tab, choose **Invite user**.
  </Step>

  <Step title="Enter their work email address">
    Use the address they will sign in with. If Beacon has already found this person in Slack or HubSpot, they are listed under the address box. Pick one to fill the address in.
  </Step>

  <Step title="Choose their role">
    Every user has one role. See [Roles and areas](#roles-and-areas) below.
  </Step>

  <Step title="Send the invitation">
    Choose **Send invitation**. Their row appears with the status **Invited**.
  </Step>
</Steps>

### What happens next

* Beacon sends **one email invitation**, and it names your company.
* **Nothing is shared until they accept.**
* When they accept, they set up their sign-in with their first name, last name and a password.
* They join in the role you chose the first time they open Beacon. Their status changes to **Active**.
* The role is only applied if the person who invited them is still an admin at that moment.

<Tip>
  Open the invitation in a private window, or in a browser where nobody is signed in to Beacon. A browser that is already signed in to Beacon skips the sign-up step.
</Tip>

## Roles and areas

The **Roles** tab, on the same page, shows each role and what it can open, page by page. Roles are fixed by Beacon. You can see them, but not edit them.

* **Leadership** sees the whole company.
* A **Domain lead** has one area and sees the figures for that area.

**Admins** add and remove users and change roles. Being an admin does not let anyone see more data.

## Resend or withdraw an invitation

Open the invited person's row.

* **Resend invitation** sends the invitation email again.
* **Withdraw invitation** cancels it. Nothing was shared.

## Change a role

Open the user's row and choose **Change role**. The new role applies straight away.

## Remove a user

Open the user's row and choose **Remove user**. Their access ends straight away.

## What Beacon will not let anyone do

The page refuses these, and says why in a sentence:

| You try to… | What happens |
| - | - |
| Change your own role | Refused. Another admin has to do it. |
| Remove the last admin | Refused. There is always at least one admin. |
| Invite an address that already has an invitation waiting | Refused. Resend the existing invitation instead. |
| Invite someone who is already a user | Refused. |
| Send an invitation without a role | Refused. Choose a role first. |
| Act on another user without being an admin | Refused. Ask an admin on your team. |

Only your admins change who can do what. **Beacon never changes it on its own.**

## One person, one email address

Each user is one person with one email address. Invite people at the address they will sign in with. That is also the address Beacon looks for when it matches their Slack and HubSpot accounts.

## Related

<Columns cols={2}>
  <Card title="Linked accounts" href="/linked-accounts">
    How Beacon links each user's Slack and HubSpot accounts, and what waits for you.
  </Card>

  <Card title="Use the Connections page" href="/use-the-connections-page">
    Connect the tools Beacon finds your colleagues in.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.