Users

This topic describes how to manage users in shared spaces and workspaces.

User architecture

Users can be created in a workspace or shared space. In both cases, the user is a space-level entity. At creation, a user must be assigned a role in at least one workspace.

Users cannot be unassigned from a workspace by any administrator. The shared space or workspace administrator can only deactivate users but not remove them. This ensures historical data integrity and auditability.

Users can be deactivated at the shared space or workspace level. A user deactivated at the shared space level is deactivated in all its workspaces. For details, see Deactivate users.

Back to top

Review users

This section describes accessing the Users grid, viewing a history of user attributes, and configuring the user details box.

To access the Users grid:

  1. Open the global menu and select AdministrationGeneral Settings.

  2. Select a shared space or workspace.

  3. Select the Users tab.

Tip: You can filter the list of users by role, workspace, and other fields, by clicking the Filter button .

To view a view history of user attributes:

  1. In the Users grid, select a user.

  2. In the user's details view, select the History tab.

Configure the user details box

When you hove over a user's avatar, a popup opens displaying essential user information, such as their contact details and team.

You can configure the information displayed in the details box or disable the box from displaying.

To configure the user details box, use the USER_DETAILS_BOX_OPTIONS and USER_DETAILS_BOX_ENABLED parameters. For details, see Configuration parameters.

Back to top

Add users

Users can be added to workspaces both in the shared space settings and in the workspace settings.

To add users:

  1. Open the global menu and select AdministrationGeneral Settings.

  2. Select a workspace or shared space .

  1. Select the Users tab.

    Click the + Add user button.

  2. Enter the user's information.

    • If you specify a Login name, the user enters this name to log in. If no login name is specified, the email address is used.

    • Login names and emails must be unique across all workspaces and spaces.

  3. Assign a License type from the list of available license types. For details, see Assign licenses.

  4. Assign roles to the to the user.

    In the shared space settings, for each role that you add, select the workspaces in which the user is assigned that role.

    For details, see Roles and permissions.

  5. Click Add.

  6. To modify an existing user's details, open a user in the Users grid and edit the details.

    You can edit your own user details in the same way. To change your own Login name, ask another admin to change it for you.

Back to top

Assign licenses

The user's license type determines which functionality is available to the user.

You can assign a license type when creating a new user, or change license type assignments in the Users grid.

To update license type assignments:

  1. In the Users tab, select one or more users, and click Assign license.

  2. Select a license type from the list of your available licenses. For details, see Licenses.

    Do not choose the Core or Developer license type.

    If the number of available named licenses of the selected license type is fewer than the number of users that you selected, none of the selected users will be assigned the license type. Select users up to the number of available named licenses.

Note: Specify which license is assigned to users created from the workspace or from API calls, in cases where the license is not provided in the API call.

Enter the default license type in the DEFAULT_LICENSE_TYPE_FOR_ASSIGNMENT parameter. For details, see Configuration parameters.

Back to top

Deactivate users

Deactivating a user removes them from the user selection list. Items that are already assigned to a user remain assigned to the user after they are deactivated. The deactivated user has a (deactivated) label appended to their user name.

Users can be deactivated at the space or workspace level. While a user is active on at least one workspace, they can still log in and they still consume a license.

Users can be reactivated at the same level at which they were deactivated:

  • If a user was deactivated in a workspace, he can reactivated only in the workspace settings.

  • If a user was deactivated at the shared space level, he can be reactivated in the shared space settings.

System emails are not sent to deactivated users.

If you reactivate a user, all existing settings for the user are restored.

The Deactivated column in the grid shows which users have been deactivated.

Icon Details
Deactivated icon

The user is deactivated at the current level.

The user can be reactivated from the current space or workspace.

Deactivated at site level icon

The user is deactivated at a higher level (shared space or site).

The user can be reactivated from the shared space or site.

To deactivate a user:

  1. Open the global menu and select AdministrationGeneral Settings.

  2. Select a workspace or shared space .

  3. In the Users tab, select one or more users, and click Deactivate.

    To reactivate a user, click Activate.

  4. Click Yes to confirm.

Back to top

Map users to SCM users

For analysis of SCM commits, identify which users perform the commits and map each user to their SCM user. This enables you to analyze the commit information with tools such as widgets and filters.

If you set up an integration with a CI server that works with a source control management (SCM) system, changes committed to the SCM system are tracked. For details, see Track commits to your SCM system.

If the email address defined for a user is identical to the one defined for an SCM user, the users are mapped automatically when changes they commit are discovered.

Make sure that your SCM system is configured to share commit authors with your CI server. For example, in the Jenkins GIT plugin, set the option User commit author in changelog.

Otherwise, map the users manually.

Users can also map themselves to unmapped SCM users listed in the Commits tab. This does not require admin permissions. For details, see Track committed changes in the Commits tab.

To map a user to an SCM user:

  1. Open the global menu and select AdministrationGeneral Settings.
  2. Select a shared space .

  3. In the Users tab, click in the SCM users cell of a user.

  4. Do one of the following:

    • Select from the list of SCM users known from previous commits.

    • Click Add New to add an SCM user. Provide the SCM user's username and email address for identification.

Back to top

See also: