Roles are the most flexible way of defining access privileges by function (assigned/authorized to different users).
The principle is as follows: Privileges are assigned to roles according to “Doc type” modules, and users are associated with different roles.
Astuce
Don’t build roles according to your company’s hierarchy, but according to the functions people have in the company.
Default setting in silicon ioi #
You can see that there are 3 categories of roles per module family:
- xxx Users
- xxx Managers
- xxx Master managers
As well as specific families:
- System Manager
- Web Site Manager
- Blogger
- Translator
- Report Manager
- All > everyone
Astuce
Master managers" are people who have control over the configuration of the family concerned. You shouldn’t associate a manager with the role of master manger, as they risk changing a configuration without knowing the consequences. They are not people who have a hierarchical position superior to that of managers.
With xxxx corresponding to the main functions in a company:
- Sales
- Purchases
- Item
- WMS
- Eshop
- CRM
- Accounting
- HRM
- Manufacturing
- HelpDesk
- Workers
Assign roles to users #
Choose the roles to assign to each user:
Role profiles #
If you want to manage users in a simple, linear way, you can define role groups in the “Role profile” module and simply associate the most appropriate role pack with the user.
There’s nothing to stop you customizing a user with additional roles.
Some useful parameters #
Security settings for the user concerned:
For password complexity, go to “System Settings” in “Minimum password score”.
Default roles associated with doc types/modules #
Each doctype/module has its own set of reassigned roles. These roles are autocreated in the system if new doctypes/modules are added to Silicon ioi.
These pre-assigned roles are visible in the doctype of the module concerned.
Example:
Level/Level #
Some doctype functions are more secure and have a level higher than zero. You must be part of this role to access this level.
Sélection/Select #
Giving this privilege enables you to select data linked to this doctype in another doc type.
Example:
In the “ioi Chart of accounts”/“ioi General account” doc type, I give permission to select an accounting charge in modules where it is used.
Lire/Ecrire/Créer/Supprimer " Read/ Write/Create/Delete " privileges #
These are the classic privileges:
- Read/Read: doctype access privilege.
- Write: modification privilege. Provided other criteria are met, e.g. the document must be in preparation or in draft.
- Create: document creation privilege.
- Delete: privilege to delete a document. This is subject to other criteria being met, such as the data in the document not being used elsewhere. Or that the document is in preparation or draft/draft.
Permission manager role #
This module lets you know the exact status of a module/doctype according to a chosen role, and if you are “System Manager”, to directly alter/change these privileges for the chosen role.
Astuce
The “Restore original permission” button lets you return to the original standard configuration.
Activity log #
This module lets you view the connection history of different users.
Access log #
This module lets you view the usage history of export functions and the list generator.
System Setting, low-level parameters #
Here you define Silicon ioi’s essential low-level parameters.
The “Enabled Onboarding” parameter enables a user to access a training session on the use of a module. However, training sessions must be defined.
Attention
We strongly advise you not to alter these standard formats.
Also define the number of backups to keep.
These are ready to be downloaded into the “Download backup” module:
