> ## Documentation Index
> Fetch the complete documentation index at: https://documents.xobito.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Staff Members
> Invite teammates into your Xobito workspace, change their role, and remove people who've left.
A **staff member** is anyone other than the workspace owner who can log into your Xobito workspace. Every staff member has exactly one role, which decides what they can see and do.
The workspace owner is not a staff member — they have an `is_admin` flag that bypasses the permission system entirely. Everyone else listed under **Team → Staff** is subject to their assigned role.
## The staff list
Go to **Team → Staff**.
Each row shows the teammate's name, email, current role, and status (active / inactive).
## Invite a new staff member
You'll see a form asking for name, email, phone, password, and role.
By default, only the **Agent** role exists (with just `tenant.chat.view`). If that's all they need, pick Agent. Otherwise, create a richer role first in [Roles & Permissions](/team/roles-permissions).
The teammate is created immediately. They can log in right away with the credentials you set.
Share the login URL and initial password over a private channel — the invite doesn't email credentials automatically in every setup.
## Edit a staff member
Click any row to open the staff member's profile.
You can:
* Change their **name**, **email**, or **phone**.
* Change their **role** — they get the new role's permissions on their next page load.
* Toggle their **status** — inactive staff members can't log in.
* Reset their **password**.
Changing someone's role changes their permissions **immediately**. If they're mid-task when you revoke access, that specific action may fail. Communicate before big changes.
## Remove a staff member
Use the delete button on their row (or inside their profile). The account is removed and can no longer sign in.
Activity Log entries created by the staff member remain in place — Xobito keeps the audit trail even after the user is gone.
## The default role — Agent
When a new workspace is created, a single role is auto-generated:
| Role | Permissions |
| --------- | ----------------------- |
| **Agent** | `tenant.chat.view` only |
That gives the new teammate access to the **Live Chat** inbox and nothing else. If you need them to also handle contacts, send campaigns, or edit templates, either:
* Extend the Agent role by ticking more permissions, or
* Create additional roles (e.g. "Manager", "Marketing", "Support Lead") and assign the right people to each.
Most teams create a "Manager" role that has most tenant permissions except the destructive ones (`*.delete`) and sensitive ones (`tenant.whatsmark_settings.edit`, `tenant.staff.*`, `tenant.role.*`). Then only the workspace owner handles those.
## Permissions to manage staff
To use this page, a user needs:
| Permission | Allows |
| --------------------- | --------------------------- |
| `tenant.staff.view` | See the staff list |
| `tenant.staff.create` | Add new staff members |
| `tenant.staff.edit` | Edit existing staff members |
| `tenant.staff.delete` | Remove staff members |
The workspace owner always has all four.
Giving someone `tenant.staff.create` means they can invite other users. Combined with `tenant.role.create`, they can effectively grant themselves any permission. Only assign staff-management permissions to fully trusted teammates.
## What to read next
The full list of permissions you can combine into a role.
Audit trail of what each staff member has done.