inflowDocsLearning path

Publishing content for Home

Availability at a glance

This guide separates an available App Shell publishing journey from Home features that lack an end-user or publisher page. Current Studio source has Home routes for Applications and Tasks (including My requests); it has no Business Starts, view-publisher, or Social page. Backend source does include a default-off Social API, but that is not a Home screen or a qualified workflow. The SCRUM-4924 material below describes candidate designs and source work, not controls you can use in a running workspace. Do not try candidate routes or API examples against a live environment.

What you want to publish Current status Where to go
An App Shell page that users can open from Home Applications Available through the existing Interface Designer publishing flow, subject to the app's access grants Use Interface Designer and the App Chat guide if chat is part of the app
A Business Start action listed in Home Proposed candidate; no Home publisher screen is available Use the currently supported process/start entry point in your application; ask the product owner about Home availability
A curated Home business view or a shared saved view Proposed candidate; no Home view publisher screen is available Use the application's existing record screens and access controls
Home Social feeds and moderation No current Home Social screen in Studio. Conditional backend routes exist in source but default off and not release-qualified. Use the approved communication and moderation process for your workspace

Publication is an additional visibility restriction. It never grants an ordinary user access to an application, record, task, document or process.

Planned candidate: Business Start actions

Not available to configure in the current Home UI. The following describes intended behavior only; it is not a procedure for an administrator to execute.

The proposed journey gives an authorized Home publisher a workspace-scoped page for reviewing current publication heads and allowed audiences. The design requires a server-checked publisher grant; Studio configuration permission alone is not sufficient. A denied user and an unavailable service must have distinct outcomes.

The proposed design checks each publication against its exact canonical lifecycle contract. A changed contract should be shown as stale, and a service outage must not present an unverified head as current. These behaviors have not been qualified as a user workflow.

The candidate proposes stable keys, display labels, a current published lifecycle, an already-allowed audience, and explicit confirmation for publish, replacement and retirement. Revision conflicts and uncertain responses need deliberate review. No publish, replace or retire control described here is available in current Home.

The candidate contract pins an immutable published lifecycle and canonical input contract. If delivered, audience metadata would control discovery only; each end user would still need current process-start authority. Publication would not start a process by itself.

Status: source/design candidate only. Required tests, reviews, ordinary-user workflow, native 2K video and delivery/playback receipts have not qualified this journey. This guide is not rollout or runtime approval.

Applications and Ask [App]

Publish an App Shell with the existing Interface Designer controls and review its published pages. Home Applications uses the canonical latest-published App Shell entry. It does not use the authoring catalog, a Home-specific version picker, or stored title copies to revive a revoked application. Assign access through the existing approved grant process separately.

Enable the existing Published App Shell Chat only for the intended app. Add actual permitted source options and supported canonical actions in App Chat settings, save and publish. User draft sharing remains unchecked by default and applies to one send only; see the App Chat manual for its selector, scope, exclusions and privacy limits. Require explicit user confirmation for business effects. Opening Home is not a global Ask Inflow session.

Planned candidate: curated business views

Not available to configure in the current Home UI. The definitions and examples below describe a proposed product contract, not an administrator workflow.

The proposed registry would reference an actual published screen and DATA_GRID or RECORD_VIEW node, exact screen/source versions, publication identity and saved inputs. A definition would include a stable Home key, label, audience, field/query capabilities, declared relations and supported canonical actions. It would not accept arbitrary SQL, a browser-supplied source identity or an executable script.

The candidate source contract sketches draft, publish and retirement operations with operation keys and expected revisions. These example routes are not a supported administrator API. A new Home revision would require deliberate re-review rather than silently repairing an old link.

The candidate relation contract pins target identity, revision, attestation and field mapping, with bounded traversal and no per-row remote lookup. It has not been qualified as an end-user capability.

The candidate calculated-column design would allow only current-row dependencies that are separately published and readable in the current source session. A calculated display column would not grant query, relation, identity, action or form-input authority. The implementation and runtime path remain unqualified.

The published-query adapter remains an integration dependency. Any eventual implementation must exclude draft fallbacks, preserve source publication pins and honor the ordinary reader's actual source policy. Do not treat a developer catalog or a global permission heuristic as a substitute.

Planned candidate: saved views and explicit sharing

Not available as a Home saved-view publisher or sharing screen in the current Home UI.

The proposed contract binds saved queries to an owner, account incarnation, workspace and exact Home publication revision. New views would be private. Explicit sharing would require current publisher permission for that view and would never grant source-data access. Recipients would need current audience and source authorization. These controls are not currently offered by Home.

In the candidate contract, personal queries contain no grant; each field, operator, search and sort is revalidated before use. Invalid saved queries would not fall back to a broader query. Search and private filter values must stay out of global browser URLs and telemetry. Audience metadata is never evidence of source permission.

Status: source/design candidate; not qualified and not available as a Home user journey. Do not treat sharing as a source-data grant or copy private query values into a workspace URL. The proposed removal action would affect a saved preference, never business records.

Planned candidate: Social audiences and moderation (no current Home Social page)

Home does not have a current Social route. This design is not a live or qualified user journey.

The candidate design limits authors to currently admitted audiences and separates moderator authority from authorship and workspace membership. A moderation decision requires a reason, revision check, retained history and audit. Source-aware audience and attachment restrictions must apply to moderators too.

The report queue, post review and hide/restore/resolve/dismiss UI remain unqualified. Configuration, native admission and positive/negative workflow evidence are outstanding. An API class alone does not establish operational readiness.

App Shell publishing: current journey

  1. Open the intended app in Interface Designer and verify the pages and data/actions it is meant to expose.
  2. Save and publish the App Shell using the existing review and publishing controls.
  3. Assign access through the existing approved grant process. Publication does not grant reader access.
  4. Sign in as an ordinary user with the intended access and open the app through Home Applications.
  5. If using App Chat, verify its app-level settings and eligible sources/actions separately. Ask [App] is not enabled by opening Home; require the user to review and confirm every proposed business effect.

The source and a documented path do not prove that a specific environment has the app, grant, model or source configured. Confirm those in the target workspace before training users.

Home Training example: draft material only

The Home Training example is import material, not an installed workspace or verified fixture. Review it in an owned draft before using it. Confirm an ordinary user's published-app access and qualify provider/index/model access separately before enabling its Ask [App] experience. A JSON file does not prove that the app is installed or ready in your environment.

See operations before changing rollout flags or schema, and maintainer guidance for source boundaries and validation.

Inflow documentation · Published 19 November 2026

Screenshot captions retain their recorded build and capture context.

Type to search articles and their contents.