Creating and configuring

Users and rights

One way in which work can be divided up in the editorial department is differentiating between an editor in charge and a group of editors. Editors are to be able to edit documents but not to go live with unverified changes.

The editor in charge is to be able to create and edit ChangeSets. Moreover, he is to be able to perform quality assurance and assign the statuses “accepted” and “rejected” for this purpose.

The editors only need the rights to work in ChangeSets and to change the status between “in processing” and “approved”.

You will find a more detailed explanation on the individual statuses in chapter Fehler: Referenz nicht gefunden Fehler: Referenz nicht gefunden.

An“editors” group should be created if there is not yet one available. In our example it is sufficient for this group to receive the rights “only in ChangeSets”.

You can also set up separate groups for editors in charge and editors if you would only like to offer the editor in charge the possibility of deleting documents. Since the ChangeSet (and thus the deleted documents) can only be published by the editor in charge, doing this is not absolutely necessary however.

Depending on how your website is structured in the editor, it is sufficient for you to give the group access to the website folder. The transformations and editor settings do not need to be able to be changed for our example.

You can also set up different user groups for different work, each of which can only edit a smaller section of the website. So there can be a group for example which only takes care of editing news and receives no access to the remaining contents of the website. In the ChangeSet overview these users can then only see changes to documents to which they have access.

Configuration button for the group settings

Change of assignment

Apart from the above mentioned settings in the group, the editor in charge also needs the “Live Editor”role. This is necessary in order to create and configure ChangeSets. Besides, he could not publish ChangeSets without this role. He does not necessarily need reading/writing rights on the productive area.

 

Difference between software releases

Up to release 4.0.6: ChangeSets can be seen and entered by all users with the editor role. A ChangeSet can be editet published or deleted by the user who created it, or by users with the admistrator role or the user administrator role.

Since release 4.0.7: ChangeSets can only be seen and entered by the user who created it, or by users with the admistrator role or the user administrator role.Rights with respect to ChangeSets have been introduced as a new feature. These rights are associated to groups and grant all members of the group the right to see and enter, or edit, or publish and delete the respective ChangeSet.

Compatibility upon upgrading: Upon upgrading to release 4.0.7 (or subsequent) the rights for all existing ChangeSets are initially set in a way, that the editors can work as they have been used before. These initial rights can be altered at any time later by the user and group administration function.

Administrators or user administrators can set the rights to any of the following options while they create a new ChangeSet:

• Full access: creator (default from release 4.0.7)
• Full access: creator; read: all users
• Full access: creator; read & edit: all users
• Full access: all users (default up to realease 4.0.6)

​The access for those editors who did not create the ChangeSet, has been restricted to read & edit up to release 4.0.6. It is now possible, to grant the publishing right for any particular ChangeSet to these editors.