The following article will discuss the types of permissions and limitations they provide, from a user configuration perspective (People).
Introduction
In the user configuration form, whether you are creating a new user or editing an existing one, you will find a gear icon in the upper right corner accompanied by the text "Permissions." It will be gray if the "Administrator" user type is selected. Remember, this implies that this user can view and modify anything they want. It will turn purple if "Regular" is selected. In this case, permissions must be assigned manually; otherwise, the user cannot access anything other than the home screen.
Permissions
If you select "Regular" as the user type, "Permissions" will turn purple. After clicking "Permissions," a new form will appear with two dropdown fields.
- Tool - This will display a list of all Terrand modules. These are:
- Permission Type - This will show the access we can grant to that Tool/Module. These are:
- None - This is the same as not assigning it directly.
- Read-only - The user will only be able to view within the module.
- Administrator - They will be able to configure and create, as well as view, within the module.
The table below details the differences in user capabilities by module, depending on whether they have Admin or Read-only permissions.
Module |
Admins |
Read-only |
People |
Creation and editing
|
View of users (and their export) and teams |
Structure |
Creation and editing of types (structure) Creation and editing of sites/assets |
View of site/asset types and sites and assets |
Inventory |
Creation and editing of warehouses Creation and editing of materials Creation and editing of stock |
View of warehouses, materials, and stock |
Charts |
Creation and viewing of dashboards |
View of created dashboards and export |
Reports |
Downloading reports |
|
Business |
Creation and editing |
Detailed view |
Training |
Creation and editing |
List and detail view |
It's important to clarify that within the "Processes" section, you'll see the option to specify:
- "None" - This would be the same as leaving it unassigned; as the name suggests, it denies access to the module.
- "Read Only" - Indicates that this user will be able to access the module and read processes, but not act on them.
- "Admin Read Only" - The user will be able to read processes and, if necessary, configure or edit the processes they are associated with.
- "Administrator" - If you want the user to have complete freedom within the module. You can also select whether they belong to one (or more) departments: this allows a user to create and configure processes for each department they are assigned to.
Conclusion
We conclude the article by inviting you to review the hyperlinks to delve deeper into each module for more information. And if you can't find the information you're looking for, don't hesitate to contact us.