User permissions via group membership

The editorial permissions (e.g., create, change, remove, release), just like the assignment of these permissions to project groups or project users, are rigidly specified by FirstSpirit.

Comparable specification is not possible for user permissions as each FirstSpirit project sets completely different requirements regarding user permissions. Therefore, when user permissions are defined, neither the permissions, i.e., the possible operations on an object, nor the group structures are defined using FirstSpirit. This definition is project-specific, differs for each project, and is the responsibility of the project administration and template development. (For further documentation, see Defininig groups)

The group structures and user permissions used in the project can therefore differ greatly from those described here by way of example.

In FirstSpirit, user permissions are assigned on the basis of groups. Unlike the group structures created in FirstSpirit for the assignment of editorial permissions (see first section), the groups used here can have a hierarchical structure – i.e., a group can contain several subgroups – and so reflect the hierarchies within a company.

The group hierarchy is presented to the editor in the form of a tree view in which the permissions can be configured.