Sandbox user permission testing

Choose “Test as this user” on a sandbox user detail page to use development Apps with that user's roles and access scopes. Return to the developer account from the persistent banner. This feature is unavailable in production tenants.
Configure users, roles, and access through the existing screens. Test users must be active with a verified email. Saves and deletes affect sandbox data, and browser tabs for the same sandbox switch together.

Current-state event recovery

Recognize Inbox receipts belonging to registered reconcile consumers during recovery contract checks. Interrupted current-state synchronization no longer appears as a missing replay contract or blocks recovery for that reason. Missing consumer definitions still block recovery. No SDK update or database migration is required.
Successful current-state reconciliation also settles paused receipts left by earlier failures. Failed reconciliation, invalid confirmations, and generation changes roll back acknowledgements; receipts arriving after reconciliation starts remain pending.

App Catalog and Data Center distinguish development execution from installation status. Import tasks retain their development context after selection, and event recovery explains that records include earlier executions. No SDK update or data migration is required.

Compare registered apps and review submissions in tables, with app names, submission times, and links to app-specific history. Version submission is labeled separately from deployment.
Resource reference pages use app catalog translations, keep long resource lists scrollable, and collapse technical definitions. Empty app settings explain when a setting declaration and a new development run are needed.