API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-051 · Authentication & identity

Forge adds offline impersonation for JSM portal-only users

Forge apps can make asynchronous Jira and JSM calls on behalf of portal-only customer accounts through asUser(accountId) or an offline user token.

Atlassian ForgeJSMoffline impersonationportal users

Previous state

Background Forge calls could not use the new portal-only-user offline impersonation path.

Current state

Apps and remotes can use the bounded offline impersonation mechanisms after declaring scopes and redeploying.

Who needs to care

Forge and Forge Remote apps serving Jira Service Management portal-only customers.

What to do

Declare required scopes, redeploy, validate portal-only permissions and avoid treating the user as a licensed account.

What the source does not prove

Portal-only users remain limited to supported Jira/JSM APIs and declared scopes; this is not full licensed-user access.

Lifecycle history

Dated event sequence

  1. Capability announced

    Offline impersonation became available for portal-only JSM accounts.

Evidence ledger

First-party sources

  1. 01
    Atlassian Developer — Forge changelog

    Official platform changelog · 2026-07-27

    Open official source ↗