Define workspace users

Tab: Workspace > Users. Visible to Site Administrators and Workspace Administrators only.

Workspace users are selected from site users, and are able to view only items in the workspace they are assigned to.

View users' current login status in the Logged In column.

What would you like to do?

Add a site user to the current workspace.

In the filter box, enter all or part of a user name (Full Name) to filter the list of users.

Unassign the selected users from the current workspace.

Assigns the selected users to specific roles.

To assign multiple users to the same roles, select the users and click Assign to Roles. The selected role is applied to all selected users.

Tip: A solid blue square in the selection box indicates that some users are assigned to that role. Click the checkbox to assign that role to all of the selected users.

Each user can have one or more of the following roles:

Role Description
Workspace Administrator

Has read and write access to all application pages and functions, as well as the Workspace configuration area.

Team Member

Has read and write access to all application pages and functions, with the following exceptions:

  • Workspace administrators can set permissions to prevent team members from deleting items created by others.

    When the Allow Team Members to delete backlog items created by others option is cleared, team members can only delete themes, features, and backlog items that they author. By default, this option is selected, and team members can delete any items.

    Regardless of configuration, Team Members can modify tasks and acceptance tests, regardless of who the author is.

    For details, see Permissions configuration.

  • Team members have read-only access to the Author field. This field can be modified only by Workspace Administrators.

  • Team members have read-only access to public favorites on grid pages. Team members can not create, update, or delete these items.

  • By default, team members have read-only access to public Dashboard favorites and to the public Dashboard gallery. Team members can not create, update, or delete these items.

    Workspace administrators can set permissions to allow Team Members to create public dashboard favorites and widgets. For details, see Permissions configuration.

Team members can also make only the following configuration changes:

  • Modify team work hours per day and working days in sprint for their team, from the bucket in the Release Backlog only.
  • Modify ALI configurations.
Viewer

Has read access only for all backlog items, grid pages, and the Sprint Closure page. Can also watch backlog items to receive notifications about status updates.

Additionally:

  • Has read and write access to private favorites on grid pages.
  • Can create private buckets on the Defect Management page.
  • Has read access on the Dashboard, and read and write access for private Dashboard items and favorites.
Integration Administrator

Has read and write access to the Integrations configuration area to configure NextGen Synchronizer.
ALI Dev Bridge

Use this role for the user whose identity will be used by ALI Dev Bridge to connect to Agile Manager.

Note: You cannot log in to Agile Manager with a user that is assigned to this role only.

Restrict the applications the selected users have access to. Users will be able to view only items associated with the applications to which they have access.

To allow users access to items that have no application value, select the (not set) value. Clearing this value sets the Application field as required for any new items those users create.

Note: Access settings take effect the next time the user logs in.

Assign the selected users to a workspace team, if workspace teams are already configured on the Workspace > Teams configuration tab.

Workspace teams function across releases. If you want to assign the user to a feature team, you must do so within the context of the relevant release.

For details, see Configure teams and releases.

Map the selected user to a specific code committer. This enables Agile Manager to associate code changes with a specific Agile Manager user.

User mapping also enables you to filter change impact reports and change longs by Agile Manager teams.

SCM users are mapped one at a time.