A global interface moves beyond early access
Atlassian moved Forge's global:ui module from its Early Access Program to Preview on November 2. The module gives an app a dedicated entry in the Atlassian app switcher and a configurable layout with a header, side navigation and main content area.
The update adds sidebar components, custom search-result routing and compatibility with site, cross-context and unit-level installations. Atlassian's component reference says the module currently works only with UI Kit using native rendering, so developers using other interface approaches do not have an equivalent global module in this release.
Preview supports production use without GA stability terms
Atlassian describes Forge Preview features as operationally supported for production apps and available to all Forge users. Preview still requires opt-in, and a breaking change carries a minimum one-month deprecation period. General Availability features receive a six-month minimum under the same lifecycle policy.
That makes the release more usable than an early-access experiment, but it is not a GA commitment. Teams adopting global:ui should isolate the integration, track component changes and budget for a shorter response window if Atlassian changes the Preview contract.
User tokens expand to eligible unlicensed accounts
In a separate Forge platform update, Atlassian enabled online and offline user-token calls for eligible unlicensed users in Forge functions and Forge Remote, including supported Jira Service Management portal access. Existing app scopes, product permissions and API-specific controls still apply, and the change does not permit anonymous-user access.
Atlassian did not state exact announcement times, feature-specific pricing or geographic restrictions for either update. CGH has not deployed global:ui, tested an unlicensed-user flow or verified behavior in a customer tenant. Administrators should test the actual account type and API path before treating the broader token support as universal access.