--- title: "Permission Schemes" canonical: "https://docs.getxporter.app/space/XPORTER/1409475/Permission%20Schemes" format: markdown --- > Macro (rw-ui-expands-macro) > > > Macro (rw-expand) > > > Macro (toc) ## Introduction Permission Schemes allow administrators to determine if the app capabilities will be available for the Issues of a Project. One Jira project must have at least one Permission Scheme, or not be associated at all (in which case, the app functionality will not be available for that project).  The Permissions Schemes screen displays a list of existing schemes (Figure 2 - 2) and, for each one, the projects that it is associated with.  ## Access > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > On your Jira Data Center instance, click the gear/*Administration* icon (Figure 1 - 1) and click *Manage apps* (Figure 1 - 2). > > ![Figure 1 - Administration](media://8c5a94d7-853d-4ba7-9990-4b7f5ce0cc47) > > > Macro (rw-step) > > The Xporter menu will open on the left side of the screen. There, click *Permission Schemes* (Figure 2 - 1). > > ![Figure 2 - Permission schemes](media://034ca953-149c-4372-9af8-89c272c0c515) ## Operations ### Adding a Permission Scheme > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the *Add* button (Figure 2 - 3). A modal will open (Figure 4). > > > Macro (rw-step) > > ![Figure 3 - Add permission scheme](media://24184eb2-9819-4a98-8758-9ab9b2d67de0) > > Here (Figure 3), you can add the Permission Scheme's name (Figure 3 - 1; mandatory field), a description (optional) and, once you're finished, click the *Create* button (Figure 3 - 3). > > > Macro (rw-step) > > The newly added Permission Scheme will now appear in the Permission Scheme's list (Figure 2 - 2). ### Editing a Permission Scheme > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Edit* button (Figure 2 - 6). A modal, very similar to the one shown in Figure 3, will open. > > > Macro (rw-step) > > The Edit modal allows you to edit the Permission Scheme name (mandatory field) and its description. Once you're finished, click the *Update* button. ### Deleting a Permission Scheme > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Delete* button (Figure 2 - 10). > > > Macro (rw-step) > > A modal will appear for you to confirm the removal of the Permission Schemes. ### Assigning Projects to a Permission Scheme > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Projects* button (Figure 2 - 8). A modal will open (Figure 4). > > ![Figure 4 - Assign projects](media://2ac92ae5-87b8-457c-a5cc-2f495f9d4bbf) > > > Macro (rw-step) > > Choose the projects you wish to have associated to the Permission Scheme by selecting the respective box (Figure 4 - 1). Once you're finished, click the *Assign* button (Figure 4 - 2). ### Copying Permission Schemes > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Copy* button (Figure 2 - 9). > > > Macro (rw-step) > > A copy of your select Permission Scheme will instantaneously appear below the copied scheme (it copies the Permission Scheme's name, description, and permissions). ### Setting a Permission Scheme as Default > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Set as Default* button (Figure 2 - 5). > > > ℹ️ When you have a default Permission Scheme defined, it means that Xporter will assign new projects that have been created to that scheme. This is really helpful when Xporter is disabled for all projects and users. > > > Macro (rw-step) > > You can repeat the process to remove that Permission Scheme as default. The only difference is that the button now will be called *Remove as Default*. ### Defining the Permissions of a Scheme > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Once on the Permission Schemes screen (Figure 2), click the gear button (Figure 2 - 4), and then the *Permissions* button (Figure 2 - 7). A new screen will appear (Figure 5). > > > Macro (rw-step) > > In the Permissions section (Figure 5 - 1), you can define: > > - Which Issue types are allowed to be exported (Figure 5 - 2). > - Define which Project roles are allowed to use Xporter for Jira (Figure 5 - 3). > - Define which User groups are allowed to use Xporter for Jira (Figure 5 - 4) > > ![Figure 5 - Definitions](media://fd74432b-9c7c-4be9-9a72-93f688f8c641) > > You can, at any time, remove an Issue type/Project role/User group by clicking the respective cross icon (Figure 5 - 5) and/or add a new one by clicking the respective *Assign* button (Figure 5 - 6). > > > Macro (rw-step) > > In the Global Template Mapping (Figure 5 - 7) and Mapping of Issue Types to Templates sections (Figure 5 - 8), you can assign Templates to Issue types: > > - Mapping of Issue Types to Templates - associate Templates to certain Issue types. For each issue type, only the associated Templates will be shown. > - Global Template Mapping - associate Templates to the Issue types defined in the upper section. All selected Issue types will have these common templates added to those that were chosen in the previous section. > > You can, at any time, remove a Template by clicking the respective cross icon (Figure 5 - 5) and/or add assign another one by clicking the respective *Assign Templates* button (Figure 5 - 6).
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/XPORTER/23102936).