Permissions assignment in FirstSpirit

FirstSpirit provides a well thought through and diverse permissions assignment system. A differentiation is made between the following permissions:

Editorial permissions

Editorial permissions which are valid for a FirstSpirit user (e.g. editor) and can be assigned on the following levels:

• at server level: Users are created in Server and Project Properties and as a result are given access to the FirstSpirit system (login).
• at project level: Users are assigned to individual projects in the Project Properties and as a result acquire access to the respective FirstSpirit project. In addition, users can be assigned to groups, which are to be given uniform permissions. The users and groups defined in the project properties are subsequently used for the assignment of editorial permissions and permissions for workflows.
• at object level: Detailed permissions for individual objects, pages, nodes, stores, etc. are assigned in SiteArchitect using the Extras / Change Permissions function (context menu), both for individual users and for groups.

Rights to execute workflows

Permissions for executing workflows are a special type of editorial permissions which relate to the workflows within a project only.

These permissions can be defined in various places:

• in the workflow in the Template Store itself. Here, general permissions for starting and switching a workflow can be configured, independent of the object on which the workflow is executed.
• at object level.
  Here, in turn, a differentiation is made between permissions
  • for starting and
  • for forwarding workflows (transitions).

User permissions

User permissions solely relate to the generated and deployed site. In general, it is possible to tell whether user permissions are used within a project by the use of a login page.

User permissions assignment and checking in FirstSpirit takes place using the so-called Permission module.