Roles
Overview
The Roles screen is your starting point for managing who can do what in Int4 Suite. A role is a named bundle of permission groups that you assign to users — for example, a "Tester" role might combine "Display test cases" and "Execute test cases" so you only have to grant one thing instead of many.
From this screen you can browse every role defined in your tenant, search for one by name or description, see at a glance how many permission groups each role bundles together, and jump into a role to inspect or edit it. Use the Create New button to start building a new role from scratch.
Roles themselves do not grant access until they are assigned to users from the Users screen. A role can combine several permission groups, and each link inside a role can be narrowed to a specific project scope so the same role grants different capabilities in different business areas. Deleting a role is blocked while any user is still assigned to it.
Tasks
How to create a new role
- Click Create New in the toolbar. The button is greyed out if you do not have permission to create roles — see "Prerequisites & permissions" below.
- Fill in the role's name, description, and permission group links on the create screen that opens.
- Save the role. It then becomes available for assignment to users from the Users screen.
Field reference
| Field | Description |
|---|---|
| Name | The role's display name. Acts as a link to the role detail screen. |
| Permission Groups | How many permission groups this role bundles together. Each link can also be tied to a project scope, so the same permission group may appear more than once if it is granted in different scopes. |
| Created By | The username of the person who originally created the role. |
| Created At | When the role was created, shown as a relative time (for example, "3 days ago"). Hover to see the exact timestamp. |
| Description | The free-text description entered for the role. Truncated in the grid; hover or open the role to read the full text. |
Tips & edge cases
- Roles only take effect through user assignments. Creating or editing a role does not grant anyone access by itself. Open the Users screen and add the role to a user to make it active.
- Roles cannot be deleted while users are assigned. If a delete is blocked, first remove the role from every user that still has it, then try again.
- Permission groups inside a role are replaced as a whole when you edit it. When the role detail screen saves your changes, the full list of permission group links is rewritten — there is no per-row edit. Always review the complete set before saving.
- Scope on a link matters. A permission group inside a role can be tied to a specific project scope, or left without a scope. A link without a scope grants the bundled permissions only on resources that themselves have no project scope — it is not a wildcard across every scope.
- The Create New button is disabled unless you have the Role: Write permission. The list itself is still visible to anyone with Role: Read.
- No bulk operations. You can only edit one role at a time, and there is no way to assign a role to many users from this screen — that happens per user on the Users screen.
Related features
Prerequisites & permissions
About permissions. Int4 Suite controls what you can see and do through roles and permission groups assigned to your user. Each role grants permissions on a specific resource (for example, Test Case, Automation Object, System Under Test) at one of four levels: Read, Write, Delete, or Execute. Some permissions are further narrowed by project scope, so you may have access to one part of the system but not another.
If a button is disabled or a list comes back empty, missing permissions are the most likely cause. Ask an administrator to review your role assignments, or check IAM → Users if you have the User: Read permission.
To use this screen you need:
- Role: Read — to view the list and open any role.
- Role: Write — to enable the Create New button and to create or edit roles.
- Role: Delete — to delete a role from its detail screen.
These permissions are not scoped — roles are administrative resources that exist tenant-wide, so any of your assignments that include the activity above will grant access on this screen regardless of project scope.