> For the complete documentation index, see [llms.txt](https://polser.gitbook.io/polser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polser.gitbook.io/polser-docs/admin/users-and-phone-numbers.md).

# Users and phone numbers

Everything to do with your team, the people, their roles, and the numbers they work from, lives in **Settings → Users**.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FCNSjotzn63jW8aueOcmz%2FScreenshot%2001-09%20at%2013-52-29.png?alt=media&amp;token=8d3c85bd-d4e9-4425-a65e-2b468a99e86d" alt=""><figcaption></figcaption></figure>

The list shows everyone on the account with their name, email, role (**Admin** or **Member**), and how many numbers they have assigned. The row menu (the three dots) is where you change a person's role, edit their name, or remove them.

## Phones visibility

Decide this before you start inviting people, because it governs what every new user can see the moment they join. It's an account-wide setting in **Settings → Admin → Phones visibility**, and it has two options:

* **All members see all numbers.** Every member sees the conversations of every number. Useful for covering absences and sharing load, at the cost of busier inboxes and less separation between people.
* **Members see their assigned numbers only.** Each member sees only the conversations of the numbers assigned to them. Cleaner inboxes and privacy between colleagues, but nobody covers anyone else without an explicit handover.

Why it comes first: imagine you don't want new sales agents to see each other's conversations. If visibility is set to "all members see all numbers," every new person you invite can immediately see everyone else's chats, which is exactly what you wanted to avoid. Set the mode that fits your team first, and every user you add afterwards inherits it.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2F3UOHWYpj3S6HokOzWvWL%2FScreenshot%2001-09%20at%2016-07-03.png?alt=media&amp;token=62503f1e-8be8-4097-9e91-8234379b1abb" alt=""><figcaption></figcaption></figure>

The setting applies to the whole account, not to individual people, and **admins always see all numbers regardless of it**. It's also separate from assignment: assignment decides which numbers a member *has*, visibility decides whether they can also see the *others*. The two work together.

{% hint style="warning" %}
This changes the whole team at once. Switching to "All members see all numbers" exposes conversations that were previously private, so let the team know before you do it.
{% endhint %}

## Adding someone to your team

Adding a person is a three-step sequence, and two of the three steps are theirs, not yours.

{% stepper %}
{% step %}

### Generate the invite link

In **Settings → Users**, click **Invite new team member**. A window opens with an invite link that you copy and share with the person through whatever private channel you like (email, WhatsApp, internal chat). The refresh icon regenerates the link, and the clipboard icon copies it.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FTB7ACgNVMws0sJStf1kA%2FScreenshot%2001-09%20at%2013-55-05.png?alt=media&amp;token=fd4c921c-9d1a-47a6-aad6-d13fd25203cc" alt=""><figcaption></figcaption></figure>

Everyone joins as a **Member**: the invite has no role choice, so if you want someone to be an admin you promote them afterwards.

{% hint style="warning" %}
The invite link expires **7 days** after it's generated (if it lapses, generate a new one from the same window). Anyone with the link can join as a member, so share it only with the right person and over a private channel.
{% endhint %}
{% endstep %}

{% step %}

### They register

When the person opens the link, they sign up with their email and a password, then **verify their email address** by clicking the link in the email Polser sends them. Their account isn't active until they do.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FGbkjxedA8MPVpHaJDyFF%2FScreenshot%2001-09%20at%2013-56-20.png?alt=media&amp;token=c324d34e-4015-43ec-ba7a-834f1ce327bb" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The verification step is the one that catches admins out. A new user will **not appear in your users list until they have verified their email**, so if you've shared the link and someone isn't showing up yet, this is almost always why. Ask them to check their inbox (and their spam folder) for the verification email and complete that step.
{% endhint %}
{% endstep %}

{% step %}

### Assign a number, or make them an admin

What's left depends on the role you want the person to have:

* **For a member,** assign at least one number so they can work (see **Assigning phone numbers** below). Whether this is strictly required depends on the **Phones visibility** setting you chose above: if members only see their assigned numbers, a member with none sees nothing, so you must assign one; if all members see all numbers, they can work without an assignment.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FSbX1geLp7pdT5lCPPER1%2FScreenshot%2001-09%20at%2014-48-23.png?alt=media&amp;token=ec8c52d3-aed5-46b3-8984-23d32a4fef59" alt=""><figcaption></figcaption></figure>

* **To make someone an admin,** promote them from the row menu (the three dots, then **Promote to admin**). Admins see all of the account's numbers, so they don't need any assigned.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FlaHEo9EsyR0llThx9z0T%2FScreenshot%2001-09%20at%2014-55-41.png?alt=media&amp;token=82bea73d-f991-4279-82c5-7c838ba15fee" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

For the full breakdown of what each role can and can't do, see [Roles & Permissions](broken://pages/7305538cf2cdc7c99ae94e20c58c41c626fcf4c3).

## Assigning phone numbers

Numbers are assigned per person. Click someone's row to open **Edit user**, where you'll find their **Name** and a list of **Assigned phone numbers** as checkboxes, each showing the number's name and digits. Tick the numbers you want to give that person and press **Save**. Changes apply across the workspace immediately.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FSbX1geLp7pdT5lCPPER1%2FScreenshot%2001-09%20at%2014-48-23.png?alt=media&amp;token=ec8c52d3-aed5-46b3-8984-23d32a4fef59" alt=""><figcaption></figcaption></figure>

Because it's a checkbox system, two things follow:

* **A person can hold several numbers,** useful for anyone who covers more than one line.
* **A single number can be held by several people,** which is what makes different team setups possible. See [Ways to set up your team](/polser-docs/admin/ways-to-set-up-your-team.md) for the common models.

A member needs at least one number to work (a number is what connects them to a WhatsApp line). Giving each number a clear display name, not just the digits, is what keeps this screen readable as the account grows, so it's worth doing well from the start.

{% hint style="info" %}
Removing a number from a person immediately takes those conversations out of their inbox. Before you reorganise numbers with the team working, be clear about who ends up responsible for what.
{% endhint %}

## Removing someone

When a person leaves the team, open the row menu (the three dots) and choose **Delete member**.

Despite the name, this **deactivates** the account rather than erasing it: the person loses access, but their conversation history and anything recorded in the CRM are kept. A deactivated user still appears in the list, greyed out.

<figure><img src="https://2865962218-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuXtAMCUsINRibvDAbve6%2Fuploads%2FBwPDt2mrwXtMpOA5a3Uy%2FScreenshot%2001-09%20at%2015-00-03.png?alt=media&amp;token=d9b275ae-0b0e-4ba8-aafa-65522acf860b" alt=""><figcaption></figcaption></figure>

Before you remove someone, decide what happens to their numbers and open conversations: the numbers they had assigned become free to reassign, and it's worth transferring their open conversations to whoever will continue them. A number with nobody watching it is a channel that keeps receiving messages no one sees.
