Create a custom role

This article shows you how to create a custom role in MobilityManager. Custom roles let you build access profiles that sit between the built-in roles, granting exactly the permissions your organisation needs.

When to create a custom role

The three built-in system roles — SystemAdmin, FleetManager, and Driver — have fixed permission sets that cannot be edited. When none of them fits, a custom role lets you assemble your own combination. Common examples include a tenant administrator who only manages users, a finance clerk who works Belege (expense documents) but not vehicles, or a read-only auditor.

Before you start

Creating, editing, and deleting custom roles requires the roles:manage permission, which the SystemAdmin role holds. If you lack this permission the action is refused.

Note: A custom role has no permissions when it is first created. It grants nothing until you assign permissions to it in a separate step.

Create the role

1. Open the roles area and choose to create a new role.
2. Enter a name. The name is required and must be unique — you cannot reuse the name of an existing role, including a system role.
3. Optionally enter a description to explain what the role is for. This helps other administrators pick the right role later.
4. Save. The role is created as a custom (non-system) role.
5. Assign the permissions the role should carry (see the related article on assigning permissions).

Editing and deleting

You can rename a custom role or change its description at any time, as long as the new name does not clash with another role. You can also delete a custom role you no longer need.

Warning: Custom roles apply across the whole platform, not just one tenant. Assign a custom role to a user for a specific tenant, but design the role's permissions with that platform-wide scope in mind.

After creating

Once the role exists and has permissions, it appears in the role picker used during user administration. Assign it to users per tenant just like any built-in role. Because permissions only take effect once assigned, remember to complete the permission step before handing the role to users.

Tip: Name custom roles for the job they represent, such as "Tenant User Admin" or "Expense Clerk", rather than for a person. Roles you can read at a glance are far easier to audit than a long list of individual permissions.

Related

• Assign permissions to a custom role
• The permission catalog and categories
• Assign and remove user roles
• The FleetManager role and its permissions