Optional technical reference. This material is for developers, integration specialists and platform administrators. For the consultant lesson, read the practical guide.
Preserved from source baseline
d4587c7c0e073e58c2d430342f65ac55dd701bf4; source/static examples retain their stated scope. They are not new runtime verification or required consultant setup steps.
Current status (2026-11-11). This guide preserves its historical Spec 118 body. Before enabling the feature in a target deployment, review the retained Spec 118 readiness history and verify that deployment's current qualification. This note is not a readiness claim.
Application users, landing pages and Studio access
Practical guide and worked examples
Three independent decisions
Application administration answers three different questions: what published application may this group use, where should its members land after sign-in, and may they open Studio. A landing page is navigation, not access. Blocking Studio is a policy choice, not a prerequisite for an application grant. Task participant, own/worked/shared case, record-row/field and document rules continue to apply after application admission.
Prepare an active editable Employees group, an active Mohammad account in that group, a published Leave requests App Shell and the current canonical feature setting. In a separate manager group, Sara can receive the appropriate reviewed scope. The application's published resources/actions must be reviewable: unresolved dynamic dependencies are not fixed by a broad workspace permission.
The administrative API lives under /api/workspaces/{workspaceId}/application-runtime-access. Read groups, applications, current contributions and options before constructing a review. It uses the path and body workspace consistently; IDs are actual selected catalog coordinates. A new contribution has action=GRANT, contributionId=null, expectedRevision=0; editing/removing an existing source retains its actual contribution ID and positive current revision. Optional destination and Studio changes have their own revision and authority requirements.
| Phase | Actual values | Reader action |
|---|---|---|
| Options/current state | Selected group/shell, saved contribution and optional policies | Inspect only sections the administrator may read/edit. |
| Preview | Request, returned planId, requestDigest, expiresAt, revisions and delta |
Review additions, removals and retained sources. |
| Apply | planId, expectedDigest, original idempotencyKey, confirmed |
Apply exactly the reviewed change. |
| Readback | Current contribution/effective access | Reconcile the original operation and test intended/sibling access. |
An administrator preview is not normal-user runtime proof. Examples below describe actual source contracts, while any deployment qualification and feature enablement remain separately accountable.
The examples below use synthetic teaching data. They are grounded in the cited source contracts; this documentation change did not execute these operations against a running Inflow deployment. Use normal authenticated sessions and the actual returned identifiers, revisions and versions from an authorized environment.
Example ROOT-APP-01 — Review and apply Employees access to Leave requests
Scenario and inputs. Nadia has the application's required access-administration authority, the feature is admitted in this environment, and the Employees group plus Leave requests App Shell have been selected from authorized catalogs. Mohammad is an active group member. The workspace, shell and group IDs below must be replaced with those actual returned coordinates; no access is created merely by opening a landing URL.
Procedure. Read current contributions and options for the selected group/shell. For a new application contribution, preview this complete request shape:
{"workspaceId":"<workspace-id>","shellId":"<published-shell-id>","groupId":"<employees-group-id>","action":"GRANT","contributionId":null,"expectedRevision":0,"destination":null,"studio":null,"journey":"APPLICATION_ACCESS"}
Send it to POST /api/workspaces/<workspace-id>/application-runtime-access/previews. Review the returned delta and impact. Apply via /applies with the returned planId, its requestDigest as expectedDigest, one retained original idempotencyKey and confirmed=true. Read back the saved contribution and effective access.
Expected result. The reviewed source contributes only its admitted runtime resource/action/role scope. Optional navigation and Studio policy remain unchanged because their inputs were null. Mohammad still needs current task/record/document eligibility. A normal Mohammad session should be used for separate runtime acceptance, including an ungranted sibling application and forbidden authoring controls.
Failure and recovery. A blocked review reports a source-specific dependency reason; correct the authored publication/configuration rather than granting broad workspace or identity permissions. Stale or expired reviews must be rebuilt from current state. An ambiguous apply response must be reconciled with the same original operation, not retried with a fresh idempotency key.
Sources. ApplicationRuntimeAccessController.java:35, ApplicationRuntimeManagementService.java:27, ApplicationRuntimeManagementService.java:41.
Example ROOT-APP-02 — Recover from a stale or expired application review
Scenario and inputs. Nadia previewed an Employees grant, then another authorized administrator changed its contribution or the App Shell's reviewed resource scope. The original preview records its plan, digest, source revisions and expiry. Nadia has not established that the apply was accepted. She needs to identify the actual state before deciding whether there is still a change to make.
Procedure. Keep the original review intent and any apply correlation in the task record. Read the current contribution and use the authorized options/effective-access surfaces. If the application reports APPLICATION_ACCESS_STALE or APPLICATION_ACCESS_EXPIRED, choose Review again and inspect a newly built delta before confirming it. If the earlier network reply was uncertain, investigate the same original operation and current saved source first; do not manufacture a second source merely because the browser did not receive a success response.
Expected result. A known stale/expired refusal does not authorize the old plan. The API maps those review-state failures to409 with safe messages telling the administrator to review again. A policy outage is503, not a stale revision or a denial. The new review presents current additions, retained sources and removals for a deliberate decision.
Failure and recovery. An unknown result remains unknown until reconciled. Repeating the old key with a different digest or sending a new key can produce a conflict or a duplicate-intent problem rather than repairing it. Preserve the original evidence, involve the accountable access owner when needed and keep broad workspace/secret grants out of the recovery path.
Sources. ApplicationRuntimeAccessController.java:50, ApplicationRuntimeManagementService.java:55, ApplicationRuntimeManagementService.java:41.
Example ROOT-APP-03 — Remove one contribution without removing another valid source
Scenario and inputs. Mohammad belongs to both Employees and Benefits. Each group has independently reviewed authority to one or more applications. Nadia needs to remove only the Employees contribution to Leave requests. She has read the current contribution ID and positive revision, and the review will show which sources are retained. Removing every user grant would exceed this intended change.
Procedure. Read /application-runtime-access?groupId=<employees-group-id> in the selected workspace. Select the exact contribution to revoke, preserving its contributionId and expectedRevision. Build a REVOKE preview through the same management boundary and review removed versus retained resources/actions and optional policy effects. Apply the confirmed plan with its own original retained key. Read both the Employees source and the user's effective access afterward; inspect the independently configured Benefits source separately.
Expected result. Only the reviewed contribution is removed. Mohammad may legitimately retain some access through Benefits, another group, a manual source or another application. A remaining allowed object therefore is not automatically evidence that revoke failed. The effective explanation must identify the surviving source within the administrator's read authority.
Failure and recovery. If the contribution changed, do not replace its revision with zero: zero describes a new grant, not removal of an existing source. Re-review the current state. Do not remove other groups or manually delete persisted contribution rows to force an expected screenshot; resolve the exact remaining source with its authorized owner.
Sources. ApplicationRuntimeManagementService.java:11, ApplicationRuntimeManagementService.java:27, ApplicationRuntimeAccessController.java:31.
Example ROOT-APP-04 — Diagnose app-only sign-in and a missing landing
Scenario and inputs. Mohammad can authenticate, but he should use the published Leave requests application rather than Studio. Nadia separately controls the admitted application contribution, an eligible after-sign-in destination and the group's Studio policy. A direct or inherited group policy can affect the result; a user-specific bypass or a second application switcher should not be assumed.
Procedure. Confirm application access first. In the authorized group Experience or workspace After sign-in surface, choose an eligible published page and priority using the current destination revision. Change Block Studio only when separately authorized and after preserving protected recovery administrators. Sign in as the actual ordinary user for runtime qualification. For source-based diagnosis, the authenticated self endpoint GET /api/application-entry returns redirectPath, reason, choices and canOpenWorkspaces; choice fields are path, applicationTitle and pageTitle.
Expected result. An eligible explicit application link takes its native precedence; otherwise the saved group destinations and conflict rules choose the route. No eligible app-only destination leads to the access-filtered fallback/help/sign-out behavior, not an automatic administration grant. A landing link never grants access to its target, and unrelated application links still enforce their own scope.
Failure and recovery. POLICY_UNAVAILABLE and503 indicate unavailable policy evidence, not an empty authorized application list or a reason to disable the access policy. Correct the group mapping or application review within its legitimate scope. Never block the last protected recovery administrator, expose forbidden Studio controls or impersonate another user to make the destination appear reachable.
Sources. ApplicationEntryController.java:22, ApplicationRuntimeManagementService.java:14, ApplicationRuntimeManagementService.java:24.
Spec118 implementation guide. The feature is OFF by code default; each deployment has its own canonical configured value and qualification status. This document explains the approved administration journey; it does not certify that the complete runtime, physical database, browser or CI acceptance has passed. Consult the current implementation record before enablement.
Give an HR group access
- Create an active Basic user and add that user to the intended active, editable group. Existing direct and ancestor group membership determines inheritance; permissions are not copied into the user at creation.
- From application Access choose the group and published App Shell, then Use application. Alternatively, select Application user in the group's capability packs and choose the application scope. Both journeys use the same reviewed contribution state.
- Review the explicit resources, actions and roles, additions, retained sources and restrictions. Resolve unavailable or dynamic dependencies through the existing publication/configuration workflow; do not add broad workspace, authoring, identity-management or secret permissions to bypass a runtime gap.
- Optionally include a landing page and Studio policy change when the administrator has their separate required authority. Neither option grants application access by itself.
- Choose Review access, inspect the changes and apply that reviewed change. If it is stale or expired, choose Review again. An uncertain save result requires checking the same reviewed operation rather than creating a second grant.
- Open the user's effective-access view and Check access, then verify an eligible action using that user's actual account. Also check an ungranted sibling application, another workspace and a forbidden authoring action. Administrator preview is not proof that the user can perform the action.
“Full runtime access” preserves existing task candidate/assignee, own/worked/shared case, row, field, object, credential and explicit-denial restrictions. Human application grants do not become service identities, connector secrets or administration privileges. Specialist builder/author packs remain separate. Published rules that consume a document or image still require current access to that document and any applicable sharing contract. Document controls in pages and task forms are reviewed as follows: a file or image upload with a fixed Documents folder lists that folder (and its current documents) as view-only access — uploading still requires the user's own write access to that folder; read-only file lists and read-only document, folder or cabinet references add no access and each open is checked against the user's own document access; an editable document picker or an upload folder written as an expression cannot be reviewed and blocks the review with its reason code. A folder in another workspace also blocks the review. Application access does not override the workspace’s external image-processing policy.
Understand capability packs and revocation
Pack absent/partial/complete state is derived from actual configured actions and scope. Selecting Application user requires an application selection; a pack name alone is insufficient. A complete group configuration is distinct from a particular member's current business eligibility. Individual keys and managed keys must agree with the saved contribution and its source.
A group or user may have access to several App Shells. Removing the HR contribution removes that contribution's authority while preserving independent Benefits, manual and other valid group/application sources. Review the retained-source explanation before confirming removal. A predefined group is not made editable by this feature.
Users always open the latest published App Shell. Publication evidence records what was reviewed, not an end-user release selection. Unchanged permission scope remains usable; new resources/actions/roles require review. An unauthorized lifecycle/rule button stays absent until the updated scope is reviewed; after applying that review, the same published application exposes the admitted action. Users do not open an old release to bypass the review. Existing pinned task-form contracts retain their own version semantics.
Configure sign-in and inheritance
Use group Experience, workspace Settings → After sign-in, or the optional grant-review fields to edit the same saved group mapping. Workspace editors need workspace-scoped destination authority; group-wide discovery and Studio policy editing have separate requirements. Each group selects at most one landing across its accessible applications.
After required authentication/consent, an authorized explicit application link takes precedence; otherwise the highest-priority eligible group destination wins. Equal-priority distinct destinations use the exceptional resolution chooser. With no mapping, Workspaces remains the default when Studio is permitted. App-only users without an eligible destination receive the access-filtered fallback, help and sign-out.
Other granted applications open through direct URLs or designer-authored published links/buttons. There is no automatic global app switcher. A link and a landing mapping never grant destination access.
Block Studio access is optional and defaults off. An active direct or ancestor group block wins ordinary allows. Application access, home selection and Studio policy remain independent. Protected recovery administrators cannot be blocked; unsafe last-recovery-administrator changes must refuse. Ordinary users have no per-user bypass. Changes take effect by the next protected request in existing sessions, including supported API/MCP clients; authorized published runtime and account-security operations remain available.
Diagnose safely and operate the rollout
Effective-user and Check access views explain inherited sources, application review status, Studio policy and destination conflicts within the administrator's read authority. Unauthorized controls are absent; unauthorized deep links show neutral “not available.” An authorized action blocked by state explains that state. Studio uses LTR; published interfaces and their components support their configured LTR/RTL direction.
Keep audit records append-only. Record actor, scope, source, old/new identifiers and revisions, outcome and correlation; never credentials, token values or private record contents. Do not reset histories or reinterpret old manual/global grants as new scoped contributions.
Enablement requires the exact candidate's complete security, real-boundary, performance, accessibility, full-suite, independent-review and CI gates. Migration readiness is specific to the target database; verify its actual schema and ordered migrations in the current implementation record. Source review alone is not migration or rollout approval. A rollback must continue enforcing saved grants, blocks and revocations. Disabling new editing surfaces is not permission to run older code that ignores saved policy; any required compatibility migration needs explicit authorization and audited evidence.
The legacy workspace-level Manage Application Access plugin remains a distinct profile-reconciliation workflow. Its historical “application” terminology refers to a workspace, not this App Shell runtime contribution.
Canonical feature configuration (spec503)
Set inflow.application-user-access.enabled in the canonical file and restart the API through its qualified rollout. API/MCP saving reports configured versus startup-effective state; it supplies no app grant, wrapper/policy version, group destination or publication. See Feature switches and migration for exact keys, defaults, scope, direct-edit locking, migration and rollback.