Blocking app access for specific spaces
Blocking JEMHC app access by Atlassian Data Security Policies
Atlassian Data Security Policies allow administrators to control which Marketplace and custom apps can access content in specific Jira spaces (previously called "projects").
If a policy is configured to restrict app access, JEMHC may be blocked from reading or processing content in one or more spaces. When this happens, JEMHC continues to work as usual for unrestricted spaces, but its behaviour for restricted spaces is limited or fails entirely.
For an overview of Atlassian Data Security Policies, see the Atlassian documentation
https://support.atlassian.com/security-and-access-policies/docs/what-is-a-data-security-policy/
https://support.atlassian.com/security-and-access-policies/docs/block-app-access/
Features impacted when access is blocked
Impacted feature | Details |
|---|---|
JEMHC cannot create an issue | Lack of permissions |
JEMHC cannot create comments in specific issue | Lack of permissions |
Update notifications couldn’t be sent | When issue created / updated / deleted in blocked space, notifications couldn’t be sent (because Jira stops sending the webhook events for any changes in this space) |
JEMHC app start web page cannot be launched from blocked space’s Jira pages | When JEMHC app is run from blocked space’s Jira pages, it calls the app link with URL parameter If app is run from unrestricted project’s Jira page, or parameter  |