Commercial transition
Previous stateModules could be assumed to run for broader user types without the new explicit manifest declaration.
→New stateDefault access remains licensed authenticated users; supported unlicensed user types require an unlicensedAccess declaration in manifest.yml.
Who is affected
Forge developers and Marketplace vendors serving anonymous, unlicensed or JSM customer users.
Action required
Declare only supported user types, test each access context and preserve licensed-user behaviour.
Evidence boundary
The rule is bounded to modules that support unlicensed access and does not create universal anonymous entitlement for every Forge module.
Timeline
- Policy or product change documented
Atlassian requires apps using jira:uiModifications to declare supported anonymous, unlicensed or Jira Service Management customer user types through unlicensedAccess.
- Effective milestone
Default access remains licensed authenticated users; supported unlicensed user types require an unlicensedAccess declaration in manifest.yml.
Official sources
- Adopting Forge from Connect changelogAtlassian Developer · 2026-07-07 · Official commercial or product documentation