Add Role

A role is a named bundle of permissions. Instead of granting capabilities to each user one by one, you build a role once — "Support Agent", "Billing Clerk", "Technician" — decide exactly what that role can see and do, then assign the role to your staff. Every user who holds the role inherits its permissions, and editing the role updates everyone who holds it.

Roles control the whole surface of the CRM: which sidebar items appear, which buttons are shown, and which actions the backend will accept. A user only ever sees and can do what at least one of their roles permits.

Where to find it: Sidebar → User Management → Roles.

Who can manage roles

Creating, editing, and deleting roles is restricted to the Admin — the branch's own main user. Reseller-tier users (Senior Partner, Partner, Agent) and the Manager role can view roles, so they can see which role they hold, but they cannot create or change role definitions.

This restriction is deliberate. A role row is shared by everyone assigned to it, so allowing a reseller to edit "their" role would let them silently grant or revoke permissions for every peer in their hierarchy. Role authoring belongs to the branch Admin only.

Senior Partner, Partner, and Agent are positions in the reseller hierarchy with identical capabilities — none of them is a branch authority. The branch authority is the Admin.

The built-in roles

AltRadius ships a set of predefined roles you can assign immediately or use as a starting point. You can edit their permissions, but the built-in roles cannot be deleted.

Role	Purpose
Admin	The branch's own main user / branch authority.
Manager	Senior branch staff.
Sales Manager / Sales Team	Branch sales staff.
Support Manager / Support Team	Branch support staff.
Senior Partner / Partner / Agent	The three reseller-hierarchy positions. They have identical roles, scopes, and permissions — each manages only its own customers and downline.

Create a role

Step 1 — Open the role builder

Go to User Management → Roles and click Add Role.

Step 2 — Name the role

Field	What it does	Notes
Role Name	A unique name describing the access level (e.g. Admin, Support Agent, Technician).	Required. Must be unique within the branch; max 255 characters.

Step 3 — Assign permissions

Below the name is the Assign Role Permissions area. Permissions are organised as a searchable tree, grouped by module. On the left is a list of modules; select a module to see its permissions on the right, expand a group to reveal the individual actions, and tick the ones this role should have.

• Use the search box to jump to a permission by name across the selected module.
• Ticking a parent permission selects all of its children; you can then un-tick individual actions you want to withhold.
• At least one permission must be selected before the role can be saved.

Step 4 — Save

Click Save. The role becomes available immediately in the Users form for assignment.

The permission modules

Permissions are grouped into modules that mirror the product's areas. The exact set you see depends on what your own role is allowed to grant — you can only hand out permissions you hold yourself. The current modules are:

Module	What it governs
Dashboard	Which dashboard tiles a role can see — system status, customers, finance, networking, top highlights, router graphs.
Customer Management	Customers, services, invoices, billing, comments, documents, quotes, vouchers — create / view / update / delete / restore.
Tickets	Support tickets and ticket actions (reopen, close, archive, mark read) and recipients.
Finance	Invoices, transactions, credit notes, payments, the branch ledger, and finance dashboard.
Networking	Routers (NAS), IPv4 networks, and system/network status.
Scheduling	Scheduled actions and jobs.
Tariff Plans	Internet plans — create / update / delete / restore.
Administration	Languages, currencies, locations, countries, and tariff settings.
User Management	Roles, users, partners, partner settings, partner packages, package assignment, and router (NAS) assignment.
Config	System configuration — payments, localization, ticket config, templates, integrations, networking config, finance config, customer categories.
Logs	Activity, authentication, usage, notification, and service logs.
Tools	Utility tools such as MAC Lookup.

Within User Management, a few permissions deserve a note because they map to the reseller model rather than a simple add/edit/delete:

• Partners → Add Senior Partner / Add Partner / Add Agent are separate permissions because creating a reseller requires being above the level you are creating. Only the Admin can create a Senior Partner; a Senior Partner (or Admin) can create a Partner; a Partner (or above) can create an Agent.
• Users → Switch Account and Reset Password are Admin-only.
• Roles → Add / Update / Delete are Admin-only (view is available to the reseller tier and Manager).

Assign a role to a user

Roles are attached to a user on the Add / Edit User form (see Add User). Open the user, pick one or more roles in the Role field, and save — the user immediately inherits every permission in those roles. A user may hold more than one role, in which case their effective permissions are the union of all their roles.

Edit or delete a role

• Edit: open a role from the list, adjust the name or permission ticks, and save. The change applies to every user who currently holds the role.
• Delete: built-in roles cannot be deleted. A custom role can be deleted by the Admin; the system blocks deletion of roles it protects and shows "This role cannot be deleted."

Troubleshooting

Symptom	Likely cause	What to do
A user can't see a page you expected	The page's permission isn't in any role they hold.	Add the relevant module permission to one of their roles, or assign a role that has it.
"This role cannot be deleted / updated"	The role is a protected built-in.	Built-ins can be edited but not deleted; create a custom role instead if you need a fresh one.
A reseller can't create a Senior Partner	Only the Admin can create a Senior Partner.	Create the Senior Partner from the Admin account, or elevate the user appropriately.
You can't grant a permission you can see elsewhere	You can only assign permissions you hold yourself.	Have an Admin grant it, or assign it from an account that holds the permission.