Create a custom role

Create a custom role

A custom role lets you build a permission set that none of the default roles cover. You might want a team lead who can see their own team's employee codes, or someone who can upload organization documents and nothing else. Custom roles sit alongside the default roles on the Roles & permissions screen.

A custom role controls what someone can see and do in Rise. It doesn't set their job title or position; those live on the employee's profile.

Create the role

1. Open the Custom roles tab

Go to People > Settings > Roles & permissions, then open the Custom roles tab. Any custom roles your organization already has are listed here.

2. Name the role

Click + Create custom role, enter a name and an optional description, then click Save. The Save in this dialogue saves the name and description only. Permission changes are saved separately in step 4.

3. Set the permissions

The new role starts with every permission at its lowest level. Some start at No access and others at View only, depending on the permission. Work through the list and set each one to the level you want.

For what each permission level means, see How to manage employee roles and permissions.

4. Save the permissions

Click Save at the bottom of the page.

What a custom role can't do

Check your role against these limits before you build it.

Access scoped to one location, department or team. Permissions apply across the whole organization. You can give a role full access, limited access, or no access to a type of information without restricting it to a single location.

Payroll access. You can't assign the Payroll role on this screen. Payroll administrators are set up by the Rise support team. See Add or remove payroll administrators.

Use across more than one organization. A custom role exists only in the organization where you create it. If you run more than one, create the role again in each.

If the role isn't working

Compensation options are greyed out. Compensation access isn't set on this screen. It's managed under User management, where your organization's Owner decides who can see compensation.

A report says the user doesn't have permission. A report runs only if the role has access to every column in the base report, not only the columns that were selected. Where specific columns are restricted, the empty state names the fields the role is missing.

The permission is granted, but the page still won't open. Contact Rise support with the role name and the permission you granted.