Team members and roles

Add the people who use 9bx, and decide what each person can see and do with roles and permissions.

Contents: Who can use it · Team members · Add a member · Invite status · Roles and permissions · Create a role · Edit permissions · Scope · Example · Tips · FAQ

Who can use it

People whose role has the team-member or roles permission. The Team members page exists only when your plan does not include HR; with HR you add people under HR → Employees (Employees), and the same invite flow applies.

Where: Settings → Team members and Settings → Roles.

Team members

The page lists everyone who signs in to the organization ("Everyone who signs in to {org}: their role, branch and invite status").

Column	Meaning
Member	Name and email, with an Inactive tag if the account is switched off
Role	The role they hold
Branch	Their branch
Department	Their department
Status	Invited, Link expired or Active

Click Add member to add one, or Edit on a row to change details. With nobody yet: "No team members yet. Add the people you work with."

Add a member

1. Click Add member ("Add team member").
2. Enter First name, Last name, Email address (they sign in with it) and optionally Mobile.
3. Choose their Role, Branch (default: Default branch) and Department (optional).
4. With HR in your plan, choose Worker type (blank means Full-time).
5. Keep Send welcome email on. They get a secure link to set their own password; the link works once and expires after a few days. If you turn it off, type a Password of at least 8 characters and tell the person yourself.
6. Click Add member. You see "{name} was added. A welcome email is on its way to {email}."

Your plan limits the number of users; the setup wizard shows "{used} of {limit} users on your plan".

Invite status and resending

Status	Meaning	What to do
Invited ("Link expires {date}")	The person has not set a password yet	Wait, or Resend invite
Link expired ("Expired {date}")	The link is too old	Click Resend invite; the previous link stops working
Active	They have signed in	Nothing

Use Edit to change role, branch or department. Changes apply at the person's next page load.

Roles and permissions

A role is a named bundle of permissions. Every organization starts with built-in roles, and you can add your own. The Roles page shows a card per role and New role.

Create a role

1. Click New role ("Create role"). In Start from choose:

Starting point	What you get
Empty	No permissions; start blank
Member	A read-only baseline
Agent	An operator baseline; the most popular
Manager	A branch-admin baseline
Duplicate existing	Copy any custom role

2. Enter Role name (for example "Billing officer") and a short description. The slug is generated.
3. Pick a colour and a two-letter mark shown on member rows.
4. Choose the Scope.
5. Click Continue to permissions.

Edit a role's permissions

The permissions page ("Edit permissions") shows modules on the left and permissions on the right. A summary panel on the right lists what members with the role can and Cannot do, and the Changes since last save (Added, Removed).

Control	What it does
Module list	Move between modules (CRM, tickets, phone, HR ...)
Search permissions in this module...	Filter the list
Select all / Clear all	Switch all permissions in view on or off
Expand all / Collapse all	Open or close the groups
Sensitive only	Show only sensitive permissions (for example payroll, exports, deletes)
Apply preset	Replace the working selection with a preset ("Apply 'Agent'?"); nothing saves until you click Save changes
Switch beside a permission	Grant or revoke it. Inherited access (marked "inherited") stays on
Save changes ({n})	Saves; changes apply to every member of the role immediately
Discard changes	Reverts to the last saved state

A role cannot be completely empty ("Keep at least one permission granted"). You can delete a role from its card; assigned members need another role first.

Where a role applies (scope)

Scope	Meaning
Organization	The role applies to every branch and team
Branch	Granted per branch; the same person can hold different roles in different branches
Team	The most specific; granted per team, best for narrow roles

A separate setting decides how much data a person sees in each module: own records, a branch, a branch and everything beneath it, or everything. See Organizations and branches.

Example scenario

Padma Net Support wants billing staff to see invoices and payments but not edit tickets. Rafiq clicks New role, starts from Member, names it "Billing officer", scope Branch, then on the permissions page turns on the billing permissions and the Clients view and uses Sensitive only to confirm nothing risky is on. He adds Imran with Add member and chooses the new role and branch Uttara.

Tips

• Start from the closest built-in role and remove, rather than building from Empty.
• Check the Cannot list before saving.
• Prefer branch-scoped roles for branch managers.

Troubleshooting and FAQ

A person cannot see a menu item. Their role lacks the permission or your plan lacks the module.

I cannot delete a role. People still hold it; move them first.

The invite email did not arrive. Check spam, then Resend invite.

I cannot reduce a role to nothing. At least one permission must stay.

Adding a member fails "limit". Your plan's user limit is reached; add users to the plan in Plan and billing.

Related pages

Workspace admins · Organizations and branches · Security · Employees