User management

This tutorial deals with some of the main aspects of user management and focuses on group-oriented rights management.

Assigning rights to groups

For this reason, groups need to be created first. The advantage of using this unified way of assigning rights is that the rights of individual users are derived from the rights of the group. It is much more time consuming if you were to assign individual rights directly.

• First step: create groups for basic rights and then groups with special rights. These rights are often related to responsibilities within your company. We recommend that you choose to name the groups according to responsibilities and use that as a starting point for assigning rights.
• If a user needs to have special rights, create a group with these special rights. That way if, at some time in the future, another user needs exactly the same rights, you only have to add that new user to the group.
• If you need to remove a specific set of rights from a user, just move the user out of the group. It is very difficult to be sure that no rights have been unintentionally retained if you assign rights to individual users and not to groups.

What happens if I delete a user that has checked in versions? Will octoplant prevent me from deleting this user? Will the versions that the user checked in be deleted as well?

If an administrator deletes a user, it is of no importance whether the user has checked in a version. Even when a user is deleted, all their versions, which they checked in, will remain unchanged on the server. Documentation related to these versions will remain unchanged. Details such as the user’s name (as well as the timestamp and the computer) can be seen in the Change history even after a user has been deleted.

Check-In or Check-Out a component, an error message will be displayed. The deleted user will no longer be able to login.

Related Topics

• Active directory binding