What are the maximum role settings for an Integrated User in Jira Align?

Still need help?

The Atlassian Community is here for you.

Ask the community

Summary

Jira Align has two types of users: Full and Integrated. When a review of license usage is needed, it can be difficult to confirm which users are considered to be Integrated and which are considered to be Full users. This is because the requirement to be considered as an Integrated User is an association with a System Role that only provides access to areas of Jira Align that should be available to Integrated Users. 

This article provides details of all of the system role settings  (toggles) that can be enabled for an Integrated User and discusses how to check the current Full and Integrated license use. It is designed to add detail to the information available in the following community article Jira Align users: Full VS Integrated

(warning) As the community article was originally written some time ago, some of  the functionality (shown in the table in the community article) has been deprecated or is no longer considered valid for an Integrated User, therefore the role toggles provided in this Knowledge Base article should be used as the current maximum settings that are applicable to integrated user licenses.

Environment

Jira Align


Solution

For a user to qualify as an Integrated User, they should be associated to a system role that does not exceed the following settings (where any toggle not specifically mentioned in this list must be disabled):


Role Toggle Comment
ProgramOverall Toggle (enabled automatically when child toggles are enabled)
Program > Manage > Features Enable this toggle but disable all the sub-toggles shown on the right of the row
Program > Manage > Program Board
Team Overall Toggle (enabled automatically when child toggles are enabled)
Team > Team > Team Room
Team > Team > BacklogEnable this toggle but disable the sub-toggle "Rank Items in External Tools"
Team > Manage > StoriesAll the sub-toggles shown at the right of the row should be left enabled
Team > Manage > DefectsAll the sub-toggles shown at the right of the row should be left enabled
Team > Manage > Team ObjectivesEnable this toggle but disable all the sub-toggles shown on the right of the row
Team > Manage > TasksAll the sub-toggles shown at the right of the row should be left enabled
Team > Manage > Assign TasksAll the sub-toggles shown at the right of the row should be left enabled
Team > Manage > ImpedimentsAll the sub-toggles shown at the right of the row should be left enabled
Team > Manage > SprintsEnable this toggle but disable all the sub-toggles shown on the right of the row
Team > Manage > TeamsEnable this toggle but disable all the sub-toggles shown on the right of the row
Team > Track > Burndowns
Team > Track > Sprint Metrics (M1)
Team > Track > Sprint Coaching
ProductsOverall Toggle (enabled automatically when child toggles are enabled)
Products > Product > Features Enable this toggle but disable all the sub-toggles shown on the right of the row
Additional Options Overall Toggle (enabled automatically when child toggles are enabled)
Additional Options > PermissionsOverall Toggle (enabled automatically when child toggles are enabled)
Additional Options > Permissions > Add Agile Objects
Additional Options > Permissions > Allow access to cancel item
Additional Options > Permissions > Allow access to read recycle bin
Additional Options > Permissions > Allow access to restore/delete from recycle bin
Additional Options > Permissions > Delete Agile Objects
Additional Options > Permissions > Manage Agile Objects(Admin)

If setting up a system role to meet these requirements then, where Overall Toggle is stated in the comments, just enable the stated individual toggles underneath it, as this will automatically enable the overall toggle. If the overall toggle is directly enabled, then this enables everything underneath it, causing more work to disable the  unwanted toggles. If a mistake has been made causing everything to be enabled then disable the toggle again and start enabling the lower level toggles instead.

(info) The system role configured with the above toggles should be set in the Jira and/or ADO connectors

  • for the Jira Connector: Jira Align > Settings > Jira Settings > Jira Setup > (use dropdown to choose connector) > Default System role for new users (scroll to bottom of page to find this)
  • for the ADO Connector: Jira Align > Settings > Azure DevOps Settings > (connector details) > Default Jira Align system role for ADO users


How to check the current Full and Integrated licence use 

  1. In Jira Align identify the name of the system role used by Integration - if unsure check the connector settings mentioned above
  2. Go to Settings > Roles and check that the role has not had more toggles enabled than are provided in the above table - if the role does exceed the documented toggles then the Jira Align instance is probably operating with 100% of the  users considered to be Full and corrective action will be needed  
  3. Go to Settings > People and click More Actions > Export which will create a CSV file
  4. Open the exported CSV file in Microsoft Excel (or any other spreadsheet application)
  5. In the spreadsheet, filter to exclude exclude any deactivated users and any users with the @atlassian.com domain in their email addresses (neither of these are included in the count of either type of license)
  6. Filter the rows to match only users with the role identified in step #1.
  7. Count the results - This is the number of Integrated User licenses the instance is consuming.
  8. Clear the filter applied in step #6
  9. Filter the rows to users that match any roles except the role identified in step #1
  10. Count the results. - This is the number of Full User licenses the instance is consuming.






Last modified on Jul 9, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.