Cette fonctionnalité est actuellement en Accès anticipé. Si vous êtes intéressé, veuillez contacter notre équipe de support technique client ou votre responsable de la réussite client pour vérifier si votre organisation est éligible.
What are roles in SafetyCulture?
Roles define what users can do in SafetyCulture. In most organizations, team members need different levels of access depending on their responsibilities. For example, a site supervisor shouldn't have the same controls as a global admin, and a frontline worker shouldn't have the same access as either. Roles let organizations match each user's permissions to their actual job. There are two types of roles:
Global roles apply across your entire organization.
Group and site roles apply only within the sites or groups a user is assigned to.
Delegating these roles allows organizations to hand user management to site supervisors or regional managers without giving them full admin access. It keeps control close to the people who run each group or site, while admins stay focused on the wider organization.
For existing users, the Permissions tab is now called Roles, and permission sets are now called global roles that work exactly the same way.
Exploring roles in SafetyCulture
Global roles
Global roles are a set of permissions assigned to users at the organization level. They control what a user can do across the entire organization, including which features they can access and what actions they can perform. The permissions available for a global role depend on the user's seat type.
Global roles are managed from the Roles tab in the web app. Users with autorisation « Gestion de la plateforme : autorisation » can create new global roles, configure their permissions, and assign them to users.
Group and site roles
Group and site roles are a set of permissions assigned to users at a group or site level. Unlike global roles, which apply across the entire organization, group and site roles only apply within the specific sites or groups a user is assigned to. Currently, the permissions available for group and site roles are limited to user management and can only be assigned to users on a full seat.
Granular permissions
The actions available to users with an assigned role depend on which permissions are configured for their role.
Permission | Description |
|---|---|
Add users | Add new users to the organization by adding them directly to their assigned group or site. Managers can also view and share existing invite links for their assigned group or site if an admin has already created them. New users are assigned the default global role for the seat type selected. |
Manage membership | Add or remove existing users' membership in their assigned group or site. |
Edit user details | View users' profiles and update their details, including name, time, notification and device settings, and user fields. |
View users | View a list of members in their assigned group or site. |
Deactivate users | Deactivate users in the organization. Deactivation applies across the entire organization, not just the assigned group or site. Deactivated users lose access to SafetyCulture and their seat is freed up. Only global admins can activate deactivated users. |
Delegated user management
Group and site roles let managers handle user management within their assigned sites or groups, without needing global roles. Depending on the permissions configured for their role, managers can add users, manage membership, edit user details, view users, and deactivate users.
Group and site roles are additive, which means they add on top of a user's existing global permissions and only apply within their assigned sites or groups. A user can hold different roles across multiple sites or groups but can be assigned only one role across them.
Role inheritance
Role inheritance lets you assign a role once and have it apply automatically down the site hierarchy, so you don't have to set access site by site. Site role inheritance follows the same rules as a user's site membership. For example, if a user is assigned a role at a higher-level site, they automatically inherit that role for all nested sites below it in the hierarchy. Users can't be assigned a different role for sites below the higher-level site.
