No permissions

Objects without permissions are not displayed, either in the left-hand nor in the right-hand part of the window. If a user is to be assigned "no permissions" for a sub-area, this must also be assigned to the "Everyone" group.

Referenced objects: **No Access** is displayed for objects to which the user has no permissions and, e.g. are integrated in input components and or are referenced to elsewhere.

A store is to be completely hidden from a user.

Viewable

This permission defines whether an object is displayed or not by SiteArchitect for a selection or in the navigation.

Referenced objects: If the user on a referenced object has "Viewable" permission, the information not worthy of protection such as ID, display name, UID, etc. is displayed to them.

The user can examine the structure of a store.

Read

This permission controls access to the content.

Referenced objects: The data of a referenced object, for example, the thumbnail of a picture in an input component, is only shown to the user with "Read" permission.

The user cannot only see the structure of the Page Store but also the content of pages and sections.

Change

The user can make changes to objects and to the content of the object and create sections.

For editors who, e.g. are only to be able to edit articles.

Create / Delete object

The user can create or delete objects, however, not folders.

With this permission the editor can enter new content in the system or remove content.

Create / Delete folders

The user can add new folders to the stores or remove folders again. Lower-level folders, pages and sections are then also only removed if the user has "Delete" permission for them. Elements (and the folders as parent nodes), for which the user does not have any permissions to delete are retained.

With this permission the editor can affect the structure of the website.

Release

The user can release changed objects. The release is performed by a workflow. The "Release" permission relates to precisely the transfer of the object into the workflow's status, the "Release Status". Permissions for performing the other steps are controlled separately by assigning permissions for executing workflows.

With this permission the user can release content which is then deployed with the next generation of the project.

See / Change metadata

The user can view any metadata available for the project or change the content of the metadata.

Change permissions

The user can change editorial permissions for groups and users.

Ideally, only the project administrator has this permission.