---
title: "Exercise 4 - Permission Schemes"
canonical: "https://docs.getxporter.app/space/XPORTERCLOUD/559974/Exercise%204%20-%20Permission%20Schemes"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
## Introduction
This is the fourth set of exercises of Level 1 [(Basic Level)](https://docs.getxporter.app/space/XPORTERCLOUD/460196). The main goal of this exercise is to assist you in setting up and manage [Xporter Permission Schemes](https://docs.getxporter.app/space/XPORTERCLOUD/528718).
Permission Schemes allow administrators to define which *Projects*, *Issue Types*, *User Roles*, and *Groups* are permitted to use Xporter, as well as manage the [Templates](https://docs.getxporter.app/space/XPORTERCLOUD/431152) used on each of those available Issue Types.
## Initial Setup
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> [Navigate to Permission Schemes](https://docs.getxporter.app/space/XPORTERCLOUD/460808/Xporter+App+Administration) (Figure 1 - 1) on the Xporter administration section page of the Jira Administration.
>
> 
>
> The Permission Schemes screen (Figure 1) will be empty if you haven't configured any Permission Scheme yet.
>
> > Macro (rw-step)
>
> Once a Permission Scheme is configured, it will be displayed on that list (Figure 1 - 2).
>
> In Permissions Schemes (Figure 1), you can:
>
> - View existing Permission Schemes (Figure 1 - 2).
> - Add [new permission schemes](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Adding-New-Permissions-Schemes) by clicking the *Add* button (Figure 1 - 3). This action opens a modal (Figure 2).
> - [Edit existing permission schemes](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Editing-Permission-Schemes) by clicking the gear icon (Figure 1 - 4), and then select *Edit* (Figure 2 - 5). A modal will open (Figure 3).
> - [Define the permissions of the scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Defining-Permissions) by clicking the gear icon (Figure 1 - 4) and then *Permissions* (Figure 1 - 6). A new screen will appear (Figure 4).
> - [Select the projects that are associated with a Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Associating-Permission-Schemes-with-Projects) by clicking the gear icon (Figure 1 - 4) and then *Projects* (Figure 1 - 7). This opens a modal (Figure 5).
> - [Copy Permission Schemes](https://docs.getxporter.app/space/XPORTERCLOUD/559974/Exercise+4+-+Permission+Schemes#Copying-a-Permission-Scheme) by clicking the gear icon (Figure 1 - 4) and then *Copy* (Figure 1 - 8). A clone of the selected Permissions Scheme will be created and made instantaneously available in the Permission Schemes list (Figure 1).
> - [Delete Permission Schemes](https://docs.getxporter.app/space/XPORTERCLOUD/559974/Exercise+4+-+Permission+Schemes#Deleting-a-Permission-Scheme) by clicking the gear icon (Figure 1 - 4) and then *Delete* (Figure 1 - 9).
> - Set the selected permission scheme as default by clicking the gear icon (Figure 1 - 4) and then *Set as Default* (Figure 1 - 10). To remove this status, click the gear icon (Figure 1 - 4) and then *Remove as Default*.
> ℹ️ **Exercise Instructions**
> ℹ️
> ℹ️ To properly execute this exercise:
> ℹ️
> ℹ️ 1. Create a basic software development project on your Jira Cloud instance, and name it *Academy.*
> ℹ️ 2. Install at least two [templates](https://docs.getxporter.app/space/XPORTERCLOUD/431152).
> ℹ️ 3. Create a new Jira user named *Arthur* and associate it only with the *jira-software-users* group (which is done by default).
> ℹ️ 4. In the sidebar of *Jira Administration -> System*, under *Security*, access *Project roles* and add a Project Role named *King*.
> ℹ️ 5. Go to the project *Academy -> Project settings.* In the sidebar, access *Permissions* and edit permissions to add the role *King* to the permission *Administer Projects*.
> ℹ️ 6. Select *Add users to a role*, and in the dialog, add the user Arthur to the role *King*.
> ℹ️ 7. After completing these steps, create a *Bug* issue, a *Task* issue, and a *Story* issue for your project.
## Permission Scheme Configuration
### [Adding a New Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Adding-New-Permissions-Schemes)
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> In the Permission Schemes of the Xporter administration section page in the Jira Administration (Figure 1 - 1), click the *A**dd* button (Figure 1 - 3).
>
> > Macro (rw-step)
>
> Enter the *Name* (Figure 2 - 1; *Academy*) and *Description* (Figure 2 - 2) of your Permission Scheme. Then, click the *Create* button (Figure 2 - 3).
>
> 
>
> > Macro (rw-step)
>
> A success message will appear, indicating that the Permission Scheme was successfully added, and it will now be visible on the Permission Schemes list (Figure 3 - 1).
>
> 
>
> > ⚠️ If the Permission Scheme name is already in use, an error message will appear when you click the Create button (Figure 1 - 3) to inform you of the conflict.
### [Editing a Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Editing-Permission-Schemes)
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On your newly created Permission Scheme (Figure 4 - 1), click the gear icon (Figure 4 - 4) and then select *Edit* (Figure 4 - 5).
>
> 
>
> > Macro (rw-step)
>
> A modal will open (Figure 5) where you can change the *Name* (Figure 5 - 1; mandatory field) and *Description* (Figure 5 - 2; optional field). After making your changes, click the *Update* button (Figure 5 - 3) to apply them.
>
> 
### [Configuring the Permissions of a Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Defining-Permissions)
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On your newly created Permission Scheme (Figure 4 - 1), click the gear icon (Figure 4 - 4) and then select *Permissions* (Figure 4 - 6).
>
> > Macro (rw-step)
>
> The Permission Scheme configurations screen will open (Figure 6).
>
> 
>
> Here, you can:
>
> - Define the *Issue Types* (Figure 6 - 1) that are allowed to be exported. In this scenario, select *Bug*, *Story* and *Task*.
> - Define the* Roles* that are allowed to use Xporter (Figure 6 - 2). In this scenario, select *King*.
> - Define the *Groups* that are allowed to use Xporter (Figure 6 - 3). Although you can view all available groups here, in this scenario, do not assign any group.
> - Map issue types to corresponding templates so that specific templates are available for specific issue types (Figure 6 - 4 and 6 - 5).
>
> > ⚠️ Even though all templates will be available to be assigned on *Issue Types*, their *Scope* settings are still respected.
> > ⚠️
> > ⚠️ Therefore, if you assign a template with only an active scope to *Single Export*, you won't be able to Bulk Export with it.
>
> > Macro (rw-step)
>
> Click the *Confirm* button (Figure 6 - 6) to apply the changes.
### [Associating a Project with a Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Associating-Permission-Schemes-with-Projects)
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Return to the *Permission Schemes* screen (Figure 4).
>
> > Macro (rw-step)
>
> Click the gear icon (Figure 4 - 4) and then *Projects* (Figure 4 - 7). A modal will open (Figure 7).
>
> 
>
> > Macro (rw-step)
>
> Select only the *Academy* project.
>
> > Macro (rw-step)
>
> Click the *Confirm* button (Figure 6 - 6) to apply the changes. The project will now be listed in the Permission Schemes screen (Figure 4 - 2).
### Copying a Permission Scheme
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On the Permission Schemes screen (Figure 4), click the gear icon (Figure 4 - 4) and then choose *Copy* (Figure 4 - 8).
>
> > Macro (rw-step)
>
> Instantly, a new entry named *Academy (Copy)* will appear (Figure 8 - 1).
>
> 
>
> > ℹ️ Only the Name, *Description* and *Permissions* fields are copied. This copy will not contain any project.
### Deleting a Permission Scheme
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On the Permission Schemes screen (Figure 4), click the gear icon (Figure 4 - 4) and then select *Delete* (Figure 4 - 9).
>
> > Macro (rw-step)
>
> A modal will be displayed, asking if you're sure about deleting the Permission Scheme. Click the *Confirm* button to proceed with the deletion.
### Making a Permission Scheme Default
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On the Permission Schemes screen (Figure 4), click the gear icon (Figure 4 - 4) and then choose *Select as Default* (Figure 4 - 10).
>
> > Macro (rw-step)
>
> To remove this status, click the gear icon (Figure 4 - 4) and then select *Remove as Default*.
## Exercises
### 1 - Enabling Permission Schemes Configurations
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> With all the Permission Schemes setup complete, navigate to the [*Miscellaneous*](https://docs.getxporter.app/space/XPORTERCLOUD/462170/Miscellaneous)*,* located in the Xporter administration section page of the Jira Administration.
>
> > Macro (rw-step)
>
> Using the toggle switches, [enable (Figure 1 - 2; 3)](https://docs.getxporter.app/space/XPORTERCLOUD/462170/Miscellaneous):
>
> - *Xporter for Jira for all projects and all users* under *Global Permissions.*
> - *Xporter for Jira panel on Single Issue View. *With this option is disabled, only the *Projects*, *User Roles*, *Groups* and *Issue types* as well as associated templates configured on the Permission Schemes are allowed to use Xporter.
>
> Click the *[Save](https://docs.getxporter.app/space/XPORTERCLOUD/462170/Miscellaneous)*[ button (Figure 1 - 10)](https://docs.getxporter.app/space/XPORTERCLOUD/462170/Miscellaneous) to apply the changes.
>
> > Macro (rw-step)
>
> In a new browser window, logged in as *Arthur*, navigate to the *Story* issue type of the project *Academy***.** You will notice that the Xporter panel isn't displayed on the right sidebar.
>
> > Macro (rw-step)
>
> Click the *Xporter* button to export multiple issues and a modal will display an error message informing that you are unable to export the selected issues. This message explains why the user can't export that issue, stating: "the user has no permissions for using Xporter in the current Permission Scheme".
### 2 - Exporting Issues within a Permission Scheme
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> While still logged in as *Arthur*, navigate to the *Bug* issue type of the project *Academy*. Here, you will notice the Xporter panel is displayed on the issue side view. However, in the Template selector, the only available option will be the template you've set up in the Permission Scheme definition for that issue type. Using the *Xporter bulk* button, the same options will be listed.
>
> > Macro (rw-step)
>
> If you attempt to bulk export only the *Bug* and *Task* issues from the project *Academy*, you will still encounter an error message informing you that you are unable to export the selected issues.
>
> > Macro (rw-step)
>
> Click the *Check Details* button, and an error reporting pop-up will appear because the issue types don't have a common template assigned in the Permission Scheme definitions.
>
> > Macro (rw-step)
>
> Using a user account with Administration access, navigate to the Permission Schemes screen in the Xporter for Jira administration section of the Jira Administration.
>
> > Macro (rw-step)
>
> Click the gear icon next to your scheme, and then select *Permissions.*
>
> > Macro (rw-step)
>
> Select a common template for both the *Bug* and *Task* issue types.
### 3 - Exporting Issues with an Unauthorized User
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> With a user account having Administration access, go to the Permission Schemes in the Xporter for Jira administration section of the Jira Administration Apps page.
>
> > Macro (rw-step)
>
> Click the gear icon next to your scheme, and then select *Permissions.*
>
> > Macro (rw-step)
>
> From the *Groups* dropdown, select select *jira-administrators*.
>
> > Macro (rw-step)
>
> Remove the *King* from *Roles.*
>
> > Macro (rw-step)
>
> Now, return to the browser logged in as the user *Arthur* and attempt to bulk export the *Bug* and *Task* issues from the *Academy* project again. An error message will appear, indicating that you are unable to export the selected issues. The error reporting pop-over will display, with an entry stating that your user doesn't have permissions.
> ℹ️ **Learn More**
> ℹ️
> ℹ️ - [Permission Schemes (Xporter App Administration)](https://docs.getxporter.app/space/XPORTERCLOUD/559974/Exercise+4+-+How+to+use+Permission+Schemes)
> ℹ️ - [Permission Schemes (Project Administration)](https://docs.getxporter.app/space/XPORTERCLOUD/430612/Project+-+Permission+Schemes)
> ℹ️ **This configuration level (Level 1 - Basic Level) is now complete. You can now proceed to **[**Level 2 - Advanced Level**](https://docs.getxporter.app/space/XPORTERCLOUD/460172)**.**
> ℹ️
> ℹ️ If you like this exercise, [please write us and leave a comment](https://docs.getxporter.app/space/XPORTERCLOUD/460118/Support) or a 👍. Your feedback is very important to us.
> ℹ️
> ℹ️ Thank you in advance. Enjoy our product!
Support/Troubleshooting
If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://docs.getxporter.app/space/XPORTERCLOUD/18251779/In-App+Chat+Support).