Skip to main content
All CollectionsMember and role management
[new] General Overview of Roles and Permissions
[new] General Overview of Roles and Permissions

General Overview of Roles and Permissions in the Application

Adhémar de Saint Just avatar
Written by Adhémar de Saint Just
Updated over 6 months ago

There are three main levels in the architecture of our application. The levels are:

  • organization

  • site

  • team

Architecture of Fabriq

How are the permissions structured?

The permissions are structured around 4 actions.

Action

Explication

Creation

Creation of an item

Modification

Modification of an item

Sharing

Sharing with another team

Viewing

Viewing an item

Note: When you have a higher-level permission within the same level or in a higher level, you automatically obtain all lower-level permissions.

👉🏼 Example: I am a site admin, so I can view, access, create, and modify all items on my site, even if I am not part of the teams.

Rights associated with different levels:

Organization Level

The organization level is the highest. The roles assigned at this level typically belong to the administrators of the global deployment of Fabriq within your company.

This role is assigned to the group project manager. The aim is to structure the application and standardize elements at the group level.

Role

Permissions

Client admin

The role of admin client grants all permissions in the application:

  • Read

  • Modify

  • Create

  • Share

API admin

All permissions of the admin client + access to tokens. Tokens allow for the automation of data export or import.

Site Level

The roles assigned at this level are most often given to users responsible for the deployment project of Fabriq on their site.

Role

Permissions

Site admin

The site admin role grants all permissions at the site level:

  • Read

  • Modify

  • Create

  • Share

Communicator

The communicator role grants the user the right to share communications across the entire site, even if the person is not part of the teams with whom they share the communication. This is the only additional right granted to them.

To go further:

Team Level

Role

Permissions

Admin

The admin team role allows for the creation of all structural elements within the team. For example, by structural elements, we mean: indicators, routines, dashboards, inviting members, etc.

Coordinator

The coordinator role involves coordinating the team's daily activities that do not impact structural elements. For example: scheduling routine instances.

Member

The member role is the most commonly used. This role is assigned to users who will collaborate within the team.

Auditor

The purpose of this role is to read information rather than collaborate.

Did this answer your question?