• No results found

User Management

In document Aligned Elements User Manual V (Page 127-131)

In the menu User Management->Manage Users, you may add, modify and disable users. Users cannot be deleted (this would make the project history inconsistent) but they can be disabled.

Dialog for management of users

A user must belong to one or more user groups. A user group defines the permissions/rights with regard to the available document object types.

When a new user is added, the initial default password is the same as the user name and has to be changed after the first login.

If a user has forgotten the password or failed to log in correctly more than three times, the administrator can reset the password to its default value i.e. the user name.

New users are optionally notified via email about having received a user in a project (provided that Email settings have been set up).

6.2.1 Assigning electronic certificates to user

The Column “E-certificate” provides the possibility to add a certificate (for digital signatures). Click the Assign link to upload the user’s electronic certificate. In conjunction with uploading the

certificate, the password of the certificate has to be added.

6.2.2 Copying users to other projects

To copy new or existing users to other projects, tick the check box Copy users to other projects

in order to display the Copy column in the User Form.

Select the users to copy and click OK.

Optionally, select to overwrite/amend information to existing users if found in the target project(s).

Then select the target project(s) in which to copy the selected users.

Note! If you have made changes to users in the User Form, the changes are applied to the users before the copy action takes place.

Note! The current logged in user must have User Management privileges in the target project(s) in order for the copy to function.

If the User does not exist in the target project(s), a new User with the corresponding user data is created. For the new user, the default password will be the same as the user name.

If a User with the same name as the copied user exists in the target project(s), the Full name, Email, Windows domain and user groups (provided that they exist) are copied to the user in the target project.

Disabled users cannot be copied.

Passwords are never copied. Password reset does not apply to copied users.

If a user group associated with the copied user exists by name in the target project(s), the user will be automatically be associated with that user group.

If the user exists in the target project(s), copied user group associations are only added to the target user, user groups are never removed as a result of the copy action.

Note! If no user groups can be associated with the copied user in the target project(s), the user will not be created in the target project(s).

6.2.3 User Group Management

To edit the user groups select the menu User Management->Manage User Groups. In the user group dialog, you can add new user groups and also adapt the permissions/rights for each type of document object.

The rights for a user group listed per document object type

Use the Restrict button to the right to restrict a user group from editing a particular attribute or selecting a particular enumeration value for an enum attribute.

Clicking on the column names to tick or un-tick all checkboxes in a column. 6.2.4 Using Windows password as alternative login

It is possible to alternatively use your windows password for login. This can be especially useful if you are simultaneously active in a large number of projects and are forced to keep track of many different passwords. To enable the Windows login the following conditions needs to be satisfied:

The Aligned Elements user name needs to be identical to the Windows user name. The global project setting “Allow Windows Logon” needs to be activated.

The Aligned Elements user needs to define the windows domain in which the windows user is active. This is done in the User Management dialog.

6.2.5 Export Users

It is possible to export the user information to file. Click User Management -> Export -> Users

and select and output directory. A file with the name Users@<ProjectName>.urs is created

containing all the user information except the password about the users in the project. This file can later be imported in different project.

Note! Passwords, user certificates, certificate passwords (for electronic signatures) and Proxy Users (users for Trac and Jira) are not exported.

6.2.6 Export User Groups

It is possible to export the user groups to file. Click User Management -> Export -> User Group

and select an output directory. One file per user group with the naming convention

UserGroup@<ProjectName>@<UserGroupName>.urg is created containing the user group definition. These files can later be imported in different project.

6.2.7 Import Users

The initial password for a created imported user is set the user name (just like when you create a user) and has to be changed at first login.

If a user with the same user name already exists, you will be asked if that user shall be overwritten with the data in the file.

If a user group associated with the imported user does not exist in the target project, that user group association is deleted after import.

If a user group associated with the imported user exists in the target project, the user will automatically be associated with that user group.

6.2.8 Import User Groups

To import user groups, click User Management -> Import -> User Groups and select one or more valid .urg files.

If a user group with the same name already exists, you will be asked if that user group shall be overwritten with the data in the file.

If an imported user group contains User Rights associated with Document Object Types that does not exist in the target project, those User Rights will not be imported.

If an imported user group lacks User Rights associated with Document Object Types that exist in the target project but did not exist in the source project, those User Rights will be added with maximum permission.

In document Aligned Elements User Manual V (Page 127-131)

Related documents