Inflow.aiDocs

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 product update — 9 November 2026. App Chat is now an implemented optional App Shell feature and may be configured after the app, its approved sources/actions and the user's ordinary access are prepared. Its source list narrows what the assistant may use; it does not grant access or replace normal user/task/record permissions. The preserved identity workflow below predates App Chat and does not include its setup; references to “separately planned” App Chat mean it is outside this tutorial's steps, not unavailable in the product. See the current App Chat lesson; this note does not certify a real user's access.

Prepare the People Operations people, groups and application access

Story and deliverables

Nadia builds Leave requests in workspace people-ops. Mohammad is an employee who asks for14–18December2026, five days. Sara is the manager who may handle the published decision task when she is actually eligible. This tutorial prepares their real identity and permission boundaries, then hands the resulting coordinates to the data/rules tutorial, App Shell tutorial and workflow tutorial.

Teaching value Actual environment value to retain
people-ops Returned workspace ID plus its stable key.
Mohammad / Sara Actual returned user IDs; names/usernames are not assumed IDs.
Employees / Managers Actual editable group IDs/keys and intended membership.
Leave requests Actual published App Shell ID/key and reviewable current resources.
leave-2026-014 Business request ID; it is not authentication or a case/task ID.
flowchart LR
    Person[Normal authenticated person] --> Membership[Directory group membership]
    Membership --> Contribution[Reviewed application contribution]
    Contribution --> Page[Published App Shell access]
    Page --> Domain[Current task / row / field / document checks]
    Landing[After-sign-in destination] --> Page

A builder may have authoring permissions that employees never need. Identity administration, workspace creation and application-access administration can belong to different legitimate operators; do not make one person a broad administrator merely to follow the tutorial. The application-user feature must already be admitted by its environment owner.

This is a source-backed teaching journey with synthetic data. It is not a built-in leave application or a completed import package. Perform any real mutations only in an admitted owned environment with normal authentication; this documentation program did not execute the product/provider workflow. Keep actual IDs/revisions/versions and private session material outside public examples.

Milestone1 — Create or select the correct development workspace

Scenario and inputs. Start with an authorized isolated development environment and a legitimate workspace creator. Nadia's creation authority and authoring admission are current; no production workspace, shared runtime or retained evidence is to be repurposed. The desired stable workspace key is people-ops, with display name People Operations.

Procedure. Inspect existing authorized workspaces before creating a duplicate. Create through Studio or POST /api/workspaces using this actual create body:

{"key":"people-ops","name":"People Operations","description":"Synthetic leave-request application"}

Retain the returned workspace id, key, environmentState and status. Read it back by the actual coordinate. Inspect its creator membership and default general business function. Establish a private fixture note mapping this returned ID to the teaching name; later API examples use the returned value, not a guessed ID.

Expected result. The workspace is created in the native DEV/ACTIVE lifecycle with the current atomic creation/seed behavior. It contains no leave record model, process, employees or application yet. The fixture note lets later tutorial readers consistently select the same legitimate workspace without treating a path header as authority.

Failure and recovery. A duplicate-key, creation-admission or state refusal is resolved at that boundary. Do not switch to root headers, use a Production workspace with a convenient name or claim the fixture exists because a JSON example parsed. Preserve the original state and choose another admitted disposable workspace only when its owner permits it.

Sources. WorkspaceController.java:109, SecuredWorkspaceService.java:80.

Milestone2 — Provision the employee and manager with actual directory IDs

Scenario and inputs. The identity administrator, who may be a different person from Nadia, has current user-management authority and an approved test-mail/welcome setup. Mohammad and Sara are synthetic learner identities. Their ordinary account type is Basic; neither needs platform administrative roles to request leave or handle a legitimately assigned task.

Procedure. Read the current profile schema and use the user wizard for the intended editable fields. Create Sara and Mohammad through the supported account lifecycle, retaining the returned IDs and safe account state. Set Mohammad's manager reference with Sara's selected actual ID where the profile is intended to express that relationship. Treat generated passwords/set-password links privately and complete normal sign-in through the admitted setup. Do not copy server-owned provider metadata or a full response into an upsert request.

Expected result. The fixture now has two real current accounts with deployment-local IDs. A display name, employee number or Text field such as employeeId=mohammad is not automatically a canonical User reference. Later workflow employee/managerUser variables must use the native user selection/binding contract, while the data model's business identifiers keep their own meaning.

Failure and recovery. If an account already exists, inspect the intended identity rather than overwriting or duplicating it. Resolve invalid/duplicate email, locked/inactive state or welcome failure with the legitimate identity owner. Never grant administrator type, fabricate an external claim or expose a one-time secret to make the rest of the tutorial proceed.

Sources. AdminIdentityController.java:365, AdminUserUpsertRequest.java:1.

Milestone3 — Create ordinary groups and review membership separately from permissions

Scenario and inputs. The group administrator can create an editable non-privileged group and knows the actual account IDs from the previous milestone. The Employees and Managers groups are separate teaching scopes; a name containing “manager” does not confer an administrative permission or native task assignment.

Procedure. Create the Employees group through the native group form or POST /api/admin/identity/groups with the actual request shape:

{"key":"leave-employees","name":"Leave employees","description":"Synthetic employee app users","parentGroupId":null,"active":true,"openMembership":false,"attributes":{}}

Create the Managers group with its own key/name. Add the actual selected person through POST /api/admin/identity/groups/<group-id-or-key>/members using {"userId":"<actual-user-id>"}. Read current members/effective members through the permitted surface and retain both group IDs/keys and their intended people.

Expected result. The directory has explicit ordinary membership. It has not yet granted workspace Editor, application resources, identity administration or task candidacy. Parent/group inheritance remains part of effective membership, so inspect the actual hierarchy before drawing conclusions from a single direct-members row.

Failure and recovery. If a predefined, protected or application-owned group cannot be edited, use the correct admitted ordinary group or its actual owner workflow. Do not delete a protected group, use a force-delete flag or broaden open membership to conceal a fixture error. Retain which membership changed and who legitimately made that change.

Sources. AdminGroupController.java:95, AdminGroupController.java:133, AdminGroupRequest.java:1.

Milestone4 — Give builders their authoring scope without turning employees into builders

Scenario and inputs. Nadia needs to author the leave assets; Mohammad and Sara need only their legitimate published application/runtime scope. The selected workspace's current grant panel and actual security-object catalog are available to the authorized workspace administrator. Group IDs from the directory are not a substitute for selecting a native grant target.

Procedure. Inspect current workspace/function/object grants and their provenance. Organize the intended assets under a business function such as leave_management through the native function surface. Assign Nadia only the legitimate builder scope needed for the authored work, keeping user/group/identity administration separately governed. For any explicit grant edit retain the actual expectedRevision (-1 only for a genuinely new direct entry) and actual native object type/ID. Use Check access for the intended builder and a forbidden sibling object before claiming the configuration is complete.

Expected result. Authoring scope and published application use are separate recorded decisions. A particular object/function grant does not eliminate row/field, task participant, document or provider policy. Existing independent sources and explicit scoped overrides remain visible in effective-access explanation; removing one entry is not equivalent to denying every path.

Failure and recovery. A stale revision requires reloading/review, not setting every write to -1. An unavailable capability cannot be treated as a denial or an allow. Do not give employee groups a broad workspace Editor/Admin role merely because an app control is absent; resolve the actual application dependency or business eligibility instead.

Sources. WorkspaceSecurityController.java:154, WorkspaceSecurityController.java:221, WorkspaceFunctionController.java:1.

Milestone5 — Build the application and retain its real runtime dependencies

Scenario and inputs. The people/groups/workspace fixture exists. Nadia now follows the connected data, interface and workflow tutorials to create the synthetic leave model/rule/App Shell and human-decision process. The current environment must admit those actual capabilities; this milestone does not pretend that creating directory groups generated the application automatically.

Procedure. Complete data and rules, then App Shell/interface milestones1–7 to publish the employee and manager forms. Follow vacation workflow milestones1–4 for authoring/publication/Debug, then return to App Shell/interface milestones8–9 to wire the real published start and native task host. Stop before ordinary-user runtime checks: return here for milestone6 to review the resulting application scope first. After that, execute workflow milestones5–8 and finish shell milestone10 plus identity milestone7. These are deliberate returns, not whole-tutorial prerequisites. Retain actual model/schema/physical publication coordinates, rule versions, screen/shell IDs and process/task contracts. Use native User values for employee/manager assignment rather than trusting business Text identifiers. Inspect the application's reviewable resources/actions; resolve dynamic or unavailable dependencies through their owning publication/configuration flow.

Expected result. The application has explicit authored/published artifacts and supported links between them. Record creation and case start remain distinct unless the builder configured the supported business action. App Shell bound pages follow their own latest-published semantics; task forms, rules and other referenced objects retain their specific native version contracts. One generic “everything is pinned” claim is insufficient.

Failure and recovery. Do not add the separately planned floating App Chat as an implemented step or grant broad permissions to compensate for an unreviewable dependency. If a required provider, template or execution path is not admitted, keep that milestone incomplete and select the supported current path with its owner. A valid source fragment is not a completed imported application.

Sources. screen.schema.json:1, ApplicationRuntimeAccessController.java:1, task-persistence.md:1.

Milestone6 — Review and apply employee and manager application contributions

Scenario and inputs. The published Leave requests App Shell and its supported resources are available. The authorized application administrator has selected the actual workspace, shell and Employees group IDs. Optional landing and Studio policies are separate choices with their own authority and revisions, so start without changing them unless the tutorial's operating plan explicitly requires those changes.

Procedure. Read the native management groups/applications/options/current contribution. For a new source, preview the complete request shape below using the same actual workspace ID in the path and body:

{"workspaceId":"<actual-workspace-id>","shellId":"<actual-published-shell-id>","groupId":"<actual-employees-group-id>","action":"GRANT","contributionId":null,"expectedRevision":0,"destination":null,"studio":null,"journey":"APPLICATION_ACCESS"}

Review returned additions/removals/retained sources and expiry. Apply /application-runtime-access/applies with its returned planId, requestDigest as expectedDigest, one original retained idempotencyKey and confirmed=true. Independently repeat the intended manager review for Managers instead of assuming a group label conveys extra actions.

Expected result. Each contribution is a reviewed native resource/action/role source. It does not override task assignee/candidate, own/worked/shared case, row/field, document or AI-disclosure restrictions. Landing and Studio policy are unchanged by null optional inputs; a group's complete configuration is distinct from an individual person's current business eligibility.

Failure and recovery. Known stale/expired plans require Review again; an uncertain apply reply first requires reconciliation of the original operation/current source. Do not create a second intent, fabricate an accepted receipt, type an unreviewed dependency or turn the whole workspace into an allowlist. Preserve the exact native result and ask its accountable owner to resolve a blocked review.

Sources. ApplicationRuntimeAccessController.java:35, ApplicationRuntimeManagementService.java:27, ApplicationRuntimeManagementService.java:41.

Milestone7 — Exercise the ordinary-user matrix and interpret failures honestly

Scenario and inputs. After identity milestone6 has configured access and workflow milestones5–8 have produced the actual case/task, return here. The configuration has been saved, but no normal-user runtime acceptance is established by an administrator preview. An independently admitted exercise uses Mohammad's and Sara's own normal sessions plus an ungranted sibling application/object/workspace. Any live operations remain subject to the environment's test data and execution authority.

Procedure. Check that Mohammad can reach only his admitted application path and intended request actions; check Sara's eligible decision task and its actual participants. Include forbidden authoring controls, an ungranted sibling, a denied row/field/document and a revoked/stale scope case appropriate to the actual fixture. Unauthorized controls/requests stay absent; direct inaccessible links use the neutral unavailable state. Keep a policy outage distinguishable from a known denial and read the actual native receipt after a consequential action.

Expected result. A correctly qualified matrix establishes only its exact actor/build/fixture and affected domain boundary. It must show both intended access and preserved exclusions. Sara seeing a shell does not prove she can decide every task, and a human-readable record does not authorize provider disclosure or an embedding index.

Failure and recovery. If a positive case fails, diagnose current contribution, actor state, publication/version and native eligibility without broadening all roles. If a negative case unexpectedly succeeds, preserve the evidence and investigate the owning authorization boundary; do not hide the result with a screenshot or a count-only report. This documentation program records source expectations, with actual product/runtime execution NOT_RUN.

Sources. authorization-visibility-policy.md:1, WorkspaceSecurityController.java:221, application-user-access.md:1, task-persistence.md:1.

Try “document generation”, “integrations” or “first form”.