Weblication^® user types / authorizations

In Weblication^® CMS, users are divided into the following user types:

• Administrators
• Maintenance users
• Designer
• Cloud user
  
• Public users
  

The number of administrators / maintenance users / designers and cloud users and public users that can be used within a Weblication^® CMS installation is activated via the license key. The number of these users already differs in the licensed Weblication^® bundle (e.g. Core Business, Grid Classic, etc.) and can be increased via additional user packages.

Userrights to files, directories and functions are differentiated by the system based on the user type. On the other hand, authorization for access to the file and directory structure is granted by assigning predefined roles in the file properties and directory settings.
Tip:
The rights report tool gives you a quick overview of which rights are set for files and directories in the content project.

You define the user type of a Weblication^® CMS user in the user administration. When editing a user, you can select the administrator or maintenance user type on the one hand and the public user type on the other. It is not possible to switch between administrator/maintenance user and public user, as this preselection must already be made when creating a new user (maintenance user or public user).

A user of the type"Administrator" always has all rights. This applies to access to files and directories below the domain as well as editing layout templates, CSS, etc.

For this user type, the stored values for owner, user and groups and assigned role in the file properties or in the directory settings have no effect. As an administrator, you have full rights everywhere, which you can only influence in very few cases (e.g. workflow settings).

A user of the type"Maintenance user" has the rights that are assigned to them directly as an owner/user or via a group membership with an assigned role.

Rights for editing etc. are assigned for files via the file properties (rights) and for directories via the directory settings (rights).
The scope of rights to files and directories is determined by the role assigned in each case. For example, maintenance users can delete files in one directory but not in another. Roles are therefore not assigned directly to the user object, but via the files or directories to the users or groups stored there.

When files and directories are created, the rights settings that are set in the file template or directory template are used. By default, the BASE templates are defined in such a way that these settings are set to inheritance and are therefore taken from the default file settings of the same or higher-level directory.
If the owner is not entered in the template, the user who created the file or directory is entered as the owner.

In general, we recommend using inheritance (see Inheritance principle) for the settings for file or directory permissions. You also have the option of defining project user groups in the project settings in order to restrict the selection of users and groups there.

Regardless of the editing rights, a maintenance user can be granted further authorizations and functions via the user administration.

A user of the type"Designer" is available from CMS version 15.

This is an editor/maintenance user with extended rights for customizing CSS files and designing pages.
The user may edit all CSS or SCSS files under layout/styles and install new variants, as well as select the variants for administrators in the editor.
In terms of licensing, the user type is treated like an editor.

A user of the type"Cloud user" is a public user (see below) with extended rights in the cloud.

If the user has viewing rights to a directory, they can call up the file explorer in the cloud for this directory and, depending on their authorization, upload and delete files there, for example.