---
title: "Project - Permission Schemes"
canonical: "https://docs.getxporter.app/space/XPORTERCLOUD/430612/Project%20-%20Permission%20Schemes"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
## Introduction
[Xporter](https://marketplace.atlassian.com/apps/891368/xporter-export-issues-from-jira?tab=overview&hosting=cloud) allows Jira Project administrators to create and manage Permission Schemes at the Project level.
All features related to [Permission Schemes](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes) management on [Xporter App Administration](https://docs.getxporter.app/space/XPORTERCLOUD/460808) are included at this level of configuration. However, users cannot associate projects with the scheme, and it's not possible to set a scheme as default.
> ℹ️ From now on, Project administrators can add, edit, and delete Permission Schemes at the Project level. Consequently, Xporter needs to associate the schemes defined at both the Project and Admin levels, resulting in a new scheme with roles and groups grouped by issue type.
## Accessing Permission Schemes
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Navigate to your Jira Cloud instance and select a project (Figure 1 - 1).
>
> 
>
> > Macro (rw-step)
>
> A menu will open on the left side of the screen. There, click the *Project settings* option (Figure 2 - 1).
>
> 
>
> > Macro (rw-step)
>
> Another menu will open, on the left side of the screen. There, enter *Apps* (Figure 3 - 1) and then *Xporter* (Figure 3 - 2).
>
> 
>
> > Macro (rw-step)
>
> In this screen (Figure 4), you can create/edit [Templates](https://docs.getxporter.app/space/XPORTERCLOUD/430710/Project+-+Templates) (Figure 4 - 1), Permission Schemes (Figure 4 - 2), and [Scheduled Reports](https://docs.getxporter.app/space/XPORTERCLOUD/41222146/Project+-+Scheduled+Reports) (Figure 4 - 3).
>
> 
## Managing Permission Schemes
### No Permission Schemes Defined
If you don't have a Permission Scheme created yet, your screen will look like Figure 4.
Here, you can:
- Click the *Create* button (Figure 4 - 4) to create a new Permission Scheme. Then, follow the instructions [on this page](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Adding-New-Permissions-Schemes).
- Click the *Learn more* button (Figure 4 - 5) to go to the [Xporter Templates documentation](https://docs.getxporter.app/space/XPORTERCLOUD/431152/Templates).
- Use the toggle (Figure 4 - 6) to disable/enable global Permission Schemes in the project.
### Permission Schemes Defined
If you have Permission Schemes already defined, your screen will look like Figure 5.
Here, you can:
- View the list of the Permission Schemes defined and their details (Figure 5 - 1).
- Click the gear icon (Figure 5 - 2) to edit (name and description), copy, and/or delete an existing Permission Scheme. If you select *Permissons*, a modal will open (Figure 6) for you to define the permissions of a Permission Scheme. This screen is similar to [the one used in the Xporter App Administration](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes) with some differences:
- Only issue types and roles available for the selected project can be defined.
- For each issue type selected, the user can define [project ](https://docs.getxporter.app/space/XPORTERCLOUD/430710/Project+-+Templates)Permission Schemes or global Permission Schemes (when the *Enable Global Permission Schemes *toggle is enabled; Figure 5 - 1).
- Click the *Add* button (Figure 5 - 3) to [add a new Permission Scheme](https://docs.getxporter.app/space/XPORTERCLOUD/528718/Permission+Schemes#Adding-New-Permissions-Schemes).
- Use the toggle (Figure 5 - 4) to disable/enable global Permission Schemes in the project.
#### Editing a Permission Scheme
To edit an existing permission scheme, click the gear icon (Figure 5 - 2) and then select *Permissions*.
Here, you can edit the Permission Scheme's:
- Issue types (Figure 6 - 1).
- Roles (Figure 6 - 2).
- Groups (Figure 6 - 3).
You can also edit the mapping of the issue types to templates (Figure 6 - 4).
Once you're done, click the *Confirm* button (Figure 6 - 5) to save the changes.
## Permission Schemes - Examples
### "Developers" (created by a a project administrator)
#### Result
User can export tasks and bugs if the Permission Scheme respects one of these conditions:
- Has the *adminstrator* role (Figure 7 - 1).
- Belongs to the *atlassian-addon-admin* group (Figure 7 - 2).
> ℹ️ In this scenario (Figure 8), it's only possible to export in a single issue because the issue types defined (Figure 7 - 3) don't have a common template (Figure 7 - 4).
### Multiple Permission Schemes
Schemes created by a JIRA administrator merge with those created by project administrators.
Users with different roles and group affiliations can export specific issue types, based on the merged schemes.
In Figure 8, you can see a scheme and the result of merging it with the one above (Figure 7).
#### "Administrators" (created by a JIRA administrator)
##### Result
- Users who have *Administrator* and *Developers* roles (Figure 8 - 2) and or belong to *atlassian-addons-admin* and *confluence-users* groups (Figure 8 - 3) can export issues of type *bug*, *task* or *story *(Figure 8 - 1).
- Users who have the *administrators* role (Figure 8 - 2) can only export tasks or bugs (Figure 8 - 1).
- Users that belong to both groups (Figure 8 - 3) can export *tasks*, *bugs*, or *stories *(Figure 8 - 1)*.*
> ℹ️ In this scenario, exporting multiple issues of different types is restricted due to the lack of common templates.
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).