Close<\/strong>.<\/li>\n<\/ol>\n\n\n\nOnce you\u2019ve done that, you will need to specify which user groups in Jira should have access to the issue panel, and other features. If you don\u2019t see the group picker field being populated with options, you will need to manually enter the name of the group (this is usually something like site-administrators<\/strong>, or service-desk-users<\/strong>)<\/p>\n\n\n\nTo trigger actions in JumpCloud, navigate to an issue and click on the Open Multiplier<\/strong> link in the sidebar.<\/p>\n\n\n\n <\/figure>\n\n\n\nEnabling self-service access requests for JumpCloud apps<\/strong><\/h2>\n\n\n\nThe Self Service access request integration, allows employees to request access to applications in JumpCloud from the JSM portal, and optionally routes the request to their manager or application owner for approval in Jira.<\/p>\n\n\n\n
Once the manager approves the request, JumpCloud assigns the user to the group, which automatically provisions the application, eliminating the need for IT to manage individual requests manually, and at the same time, end users get what they need quickly and easily.<\/p>\n\n\n\n
This guide will walk you through the steps needed to set up Multiplier\u2019s self-service access request workflow feature after you\u2019ve connected your JumpCloud account, illustrated in the steps above. <\/p>\n\n\n\n
To request access in Multiplier<\/strong><\/h3>\n\n\n\nIn the Multiplier application, select the software for which you are requesting access:<\/p>\n\n\n\n <\/figure>\n\n\n\n\nTurn on the enable application catalog setting in Multiplier\u2019s configuration. This can be accessed through the Apps > Manage<\/strong> your apps in the Jira nav.<\/li>\n<\/ol>\n\n\n\n <\/figure>\n\n\n\n\nTo display a list of apps in the JSM portal, you will need to associate the app catalog with a Request Type. If you do not want to use an existing request type, then go to Project Settings > Request types<\/strong> and click Add new request type<\/strong>.<\/li>\n\n\n\nTo provision apps immediately after they\u2019re requested, keep the required approval setting disabled. Otherwise, switching it on will display the default approval behavior when apps are requested, which can be further customized for each individual app.<\/li>\n\n\n\n If enabling approvals, you\u2019ll need to map the workflow status that a request transitions to once approval has been granted. This is how Multiplier determines whether approval has taken place so it can go ahead and carry out provisioning.<\/li>\n\n\n\n Select the issue’s field for populating approvers (typically the Approvers field). <\/li>\n\n\n\n Select the default approver – this can either be the application owner, the requestor\u2019s manager, or a Jira user of your choice.<\/li>\n\n\n\n Lastly, select the status Multiplier should transition the issue to once the app has been provisioned. If provisioning fails for some reason, this step will not be carried out.<\/li>\n<\/ol>\n\n\n\nTo populate the App Catalog<\/strong><\/h3>\n\n\n\nMultiplier will automatically discover apps once connected to your JumpCloud instance. You can view this list by clicking on Apps > Multiplier<\/strong> in the Jira top nav.<\/p>\n\n\n\nBy default, all apps appear with an \u2018Unassigned<\/strong>\u2019 status. To sanction apps that end users are able to request, change their status to \u2018Approved<\/strong>\u2019.<\/p>\n\n\n\nApps with multiple identity groups mapped to them can be configured with different entitlements to let users select the type of access they want. These access levels can then be mapped to different identity groups.<\/p>\n\n\n\n <\/figure>\n\n\n\n