Define site users

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

Site users include all users in the site, in all workspaces. View users' current login status in the Logged In column.

What would you like to do?

Create a new user and include the user in the site. The new user is added to the SaaS Customer Portal.

Note: You can only add a user whose email address shares the same domain as the portal admin user, or is listed in your list of trusted domains. Trusted domains are defined in the SaaS Customer Portal, and can be modified there. To modify trusted domains, contact Customer Support.

Select existing users from the SaaS Customer Portal to include in the site.

Filter users by entering all or part of a Full Name or Login Name in the column headers.

Note: The list of users includes only users that do not already exist in Agile Manager.

Remove the selected users from the site.

Activate users to enable them to log in to the site.

Users you add or include in the site are automatically activated, provided there are available licenses.

You may want to note the users' last login date in the Last Login column. If you are juggling licenses between users, you can use this data to identify users who have not used Agile Manager recently. Deactivate these users to make room for other new users.

Note:  

  • If you do not see the Last Login column, use the column selector to add it to the grid.
  • You cannot activate users if all licenses are already in use. Either purchase new licenses, or deactivate other users to make licenses available.

The widget in the top right corner of this page, displays information about current licenses available on your system, as well as past and future licenses.

Note:  

  • If you have multiple sets of licenses pending expiration or waiting to be added, the widget displays only the closest sets.
  • Recently expired licenses are only listed if they expired within the last week.

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.

Note: When assigning roles to multiple users, you must select users that are assigned to the same workspace. If the users are assigned to multiple workspaces, first select the workspace where you want to make the change.

Each user can have one of the following roles:

Role Description
Site Administrator

Has read and write access to Site configuration pages, the Workspace > Users configuration page, and the Integrations > API configuration page.
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 cannot 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 cannot 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 > Synchronizer configuration page to configure NextGen Synchronizer.
Integration Bridge

Manages communication between Agile Manager and the NextGen Synchronizer Integration Bridge.

Note:  
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.

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.

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

If you decide not to use multiple workspaces, all users are automatically assigned to the Default workspace.

Tip: If you have many workspaces, enter a search string to filter the workspaces displayed.