What your site needs, who can do what, and the permissions the app asks for.
Your site
- Jira Service Management Cloud with a customer portal.
- A Jira admin to install the app from the Atlassian Marketplace and configure it.
- Customers who sign in to the portal. PortalPilot works out who someone is from their Atlassian account, so it is not shown to visitors who are not signed in.
Who can do what
| Person | Can |
|---|---|
| Jira admin | Open the PortalPilot admin page and change every setting. Manage global filters. Rename and delete global filters, and delete any user filter, in Filters management. On the portal, also sees App configuration in the PortalPilot sidebar. |
| Customer or agent on the portal | Open PortalPilot if Visibility allows it. Save and share filters if the Save and share rules allow it. Manage global filters if an admin has named them. |
Visibility applies to Jira admins too. There is no admin bypass: an admin who is not allowed by Visibility does not see PortalPilot on the portal either.
Permissions the app asks for
There is no permission to write to Jira.
- read:servicedesk-request: read requests, service desks and request types on the portal.
- read:jira-work: check whether the person is a Jira admin, and list fields for Fields configuration.
- read:organization:jira-service-management: read organisations.
- read:jira-user: read user names and groups for pickers, lists and visibility.
- storage:app: keep settings and saved filters in the app’s own Forge storage.
- report:personal-data: Atlassian’s personal data reporting. The app reports the account IDs it stores, and erases what it stores for accounts Atlassian reports as closed.
Related pages
Need help with PortalPilot? Contact us