Security

Last updated: 23 October 2026

How we protect customers who use Portal Fields – Show Assignee and SLA to Customers.

Architecture

• Runs on Atlassian Forge. All code runs in Atlassian's sandboxed, Atlassian-hosted runtime. There are no AMZMILLA servers, databases or third-party services.
• No data egress. The app declares no external network permissions; data never leaves Atlassian.
• Minimal, read-only scopes: read:jira-work, read:jira-user, read:servicedesk-request, read:organization:jira-service-management and storage:app. The app cannot change or delete your Jira data.

Access control

• Before returning any request, the app checks that the signed-in customer is allowed to see it: they raised it, are a request participant, or it is shared with their organization. Any other request is never shown or exported.
• Only project administrators can open and change the app's settings; the check is enforced on the server side.
• Administrators decide which fields are visible to customers and can turn exports off per project.

Data protection

• Data in transit and at rest is protected by Atlassian's platform encryption (TLS in transit; encrypted Forge storage at rest).
• The app stores only project configuration and no personal data (see the privacy policy).
• Export files are created in the user's browser. Cell values are escaped to prevent spreadsheet formula (CSV) injection.
• The app does not store credentials, API tokens or secrets.

Development and vulnerability management

• Every release is tested, including automated tests and permission tests that confirm customers cannot see requests they are not entitled to.
• Dependencies are kept to a minimum and are reviewed and updated regularly.
• We take part in the Atlassian Marketplace security programs and fix vulnerabilities within the timelines of the Atlassian Marketplace Security Bug Fix Policy.

Reporting a vulnerability