Define groups
FirstSpirit provides the "Permission" module for the assignment of user permissions. It uses the CMS_INPUT_PERMISSION permissions definition component, which has to be configured by the project developer first before being used by the editor.
Possible groups can be:
internal users | external users | |
|---|---|---|
by topic / subject |
|
|
by hierarchy |
|
|
Permissions assignment / checking | Permissions can usually be assigned like editorial permissions. | In general, users must register first and then receive access to protected areas through a login function. |
The groups.xml file
groups.xml configuration file in server monitoring
The groups are entered in the groups.xml configuration file. This can be reached via server monitoring. As a default, the
- Anonyme Besucher (Anonymous visitors),
- Registrierte Mitglieder (Registered members) and
- Kunden (Customers)
groups are entered under the group name "GroupsFile".
Depending on the requirements, groups can also have several sub-groups. On the one hand, these hierarchies can be manually entered in the groups.xml file, on the other hand, they can be automatically generated from the Content Store with the help of BeanShell scripts.
Individual users can be entered in the users.xml file in an analogous way. The "Permission Service" group module of the FirstSpirit Personalisation module can subsequently access this.
Detailed information on configuring services and modules and on the groups.xml file are given in the FirstSpirit Manual for Administrators.
The service.ini file
On the one hand, the path to the groups.xml file must be entered in the service.ini configuration file. This is already configured as a default. On the other hand, the symbolic names of the available group hierarchies must be entered. As a default, the group hierarchy "GroupsFile" is already entered here. If necessary, the configuration of service.ini file can also be carried out via server monitoring.