The SOFOS360 authorization system uses the so-called authorization roles. In such an authorization role you indicate per element within SOFOS360 which rights apply. The following rights are possible:
In addition, it is also possible to make a certain right dependent on the content of a certain field. For example, think of
In this context, an element refers to a component of the SOFOS360 data model (also called an entity). The data model of SOFOS360 describes the data world of SOFOS360. Using the data model all data as you see it within SOFOS360 can be stored. By assigning rights to parts of the data model you determine what a user may and/or may not see and/or change. Within the data model a number of main elements can be distinguished, which you will also recognize as such within SOFOS360. Examples are: Substance, Employee, Organization. Pot and Article. Such a main element in turn consists of other elements. For example, the main element Substance consists of up to 37 sub-elements which in turn can also consist of other elements.
In total, there are more than 330 elements that you can all authorize individually. Fortunately, SOFOS360 has a tool to simplify authorization. Moreover, smart authorization allows you to set the permissions on a main element without having to set the permissions on the individual sub-elements. Compare this to securing a building with rooms. You can, of course, put a lock in the front door of the building as well as in the door of each room, preventing unauthorized persons from entering the building and the rooms. However, the lock on the front door of the building should be enough to keep unauthorized people out. You can achieve the same within the SOFOS360 with smart authorization. However, it is not always clear which elements are main and which are sub-elements. Moreover, the function of some elements is not immediately clear. To help you with this, below you will find a table for each element in SOFOS360 in which the main and associated sub-elements are listed and it is indicated whether the main element can be hidden via the authorization field 'Navigate' in the menu. When all main elements of a menu item are hidden then the entire menu item will be hidden.
Substance
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Substance |
Substance name, Blend components, Linked GHS pictogram, Linked departments, Linked employees, Linked H phrases, Linked P-phrases, Free text (substance), substance solubility, texts, additional tramp texts, substance use, advised use, steam pressure, viscosity, Free text type (substance) |
Yes |
Room
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Space |
Free text (Space), Free text type (space), complex, room, building, location, table, section, shelf, shelf section, rack, drip tray, floor, wing, cabinet type, has a roof, has walls, space usage, protection level |
Yes |
CMR registration
| Main elements | Sub-elements | Toegang via het menu |
|---|---|---|
| Process (CMR) | Process name, process description, process step name, process exposure time, substance used, risk identification, personal protection, site protection, process step exposure time, substance consumption, substance usage (CMR) | Yes |
| Process administration (CMR) | Yes |
Stock
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Article |
Article group, article note, article description, article instruction, article name |
Yes |
| Pot |
Pot (Base), Potential Pots (Distribution Process), Pot (Distribution Process), Pot (Reprice), Pot (Repack/Repack Process), Pot (Back to Supplier), Pot (Back to Warehouse Process), Pot (Move Process) |
Yes |
| Pot history | Yes | |
| Issue form | Yes | |
|
Collectively erase pot history |
Yes | |
| Mark collective pots as consumed | Yes | |
| Process scan file | Yes |
Order
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Order request | Order request line | Yes |
| Order | Order line | Yes |
Waste
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Waste packaging | Waste type, Waste | Yes |
| barrel | Waste stream, Eural code, Barrel (base), Barrel (distribution), Barrel (donated to), Barrel (redistribute), Barrel (received from), Barrel (received) | Yes |
| Barrel separated | Yes | |
| Shipment | Shipment Rule, Making Shipment | Yes |
Information portal
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Substances Information Portal | Information portal (Document), Information portal (Substance name), Information portal (Pot), Information portal (Substance) | Yes |
Third party database
| Main elements | Sub-elements | Access via the menu |
|---|---|---|
| Import of substance data | DBD (BIG info), DBD (Database info), DBD (Search result) | Yes |
| Updating substance information | DBD (Substances to be updated) | Yes |
| Substance data replacement | DBD ( Linking Substance), | Yes |
Settings
The settings menu items can all be hidden from the menu via their names by unchecking the navigation right.
Reports
Reports can also be authorized but this is done in a different way than described above. To authorize one or more reports, locate the Authorisation (Type of Permissions) 'Report (SOFOS360)' and edit it by clicking the pencil. Then uncheck the 'Read' box. You have now indicated that the user(s) with the current role may not read any report. Then you use Permission on content (entities) to indicate under which condition the user may read a report. You do this by checking the 'Write' field and using the criterion to indicate when the user is allowed to read the reports.
Because you initially hide all reports, you sometimes have to think 'the other way around' to make certain reports visible. For example, if you want to hide all Inventory reports, then select 'Show all reports that not appear in the 'Inventory' section in the criterion. The criterion then becomes: