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

# Users and roles

> Who can sign in, and what they can change

Nudge is invite-only. An address nobody invited cannot sign in, however valid its Google account is. Manage everyone from **Settings → Users**.

## Inviting someone

**Add user** takes an email address and sends the invite. Until they sign in for the first time they sit in a **Pending invites** list, where you can revoke the invite if you sent it to the wrong place. Revoking an invite has no effect on anyone who already has an account.

## The two roles

* **Member** works leads. Contacts, inbox, calls, messages, deals: everything the daily job needs. They cannot change settings, edit triggers, or manage people.
* **Admin** does all of that plus configuration: triggers, templates, fields, connections, API keys, and inviting or removing users.

Give reps Member. Keep Admin for the one or two people who actually own the setup, because an admin can change automation that messages your entire database.

Two guard rails you will run into by design: you cannot change your own role, and you cannot remove the last remaining admin — neither by demoting them nor by revoking their access. A workspace with no admin has no way back in.

## Approving and removing access

Users you have invited show a status. You approve, reject, deactivate or reactivate from the same table. Deactivating is the one to reach for when someone leaves: it cuts their access immediately while their history stays intact.

Nobody is ever deleted, and that is deliberate. Everything a person did — the messages they sent, the notes they wrote, the changes they made — stays attributed to them. Instead, revoked people drop out of the list behind a **Show N revoked** link at the bottom, and searching by name still finds them. Reactivating brings someone back exactly as they were.

If a status was set with a reason, hover the status to read it, along with who set it and when.

## Who sends what (standalone)

On a standalone workspace everyone in this table is also a **contact owner** — leads get assigned to them, and there is no separate owners list to keep in step. Each row carries their send setup:

* **WhatsApp number**, the line their messages send from
* **Language**, which decides which template version their contacts receive
* **Working hours**, which gate when their contacts get contacted (click the hours to set days, times and timezone)

A row marked **No login** owns contacts but has no account — you can still set its send config, or invite the address to give them access. Contacts nobody owns appear as a **No owner** count at the bottom; automation skips them until someone owns them.

<Note>
  HubSpot workspaces keep a separate **Contact owners** page instead, because owners come from HubSpot's own directory and may not have a Nudge login at all.
</Note>

## Notifications

Each user chooses what they want to hear about, in-app through the bell or by email, per event: a new contact arrives, a contact replies, a call completes, a status changes, a document is received, or a task falls due. Task reminders always go only to the person who set the task.

Admins can additionally opt into an email when a HubSpot sync fails.