Apps turn your sheets and workflows into a focused experience: a form, onboarding journey, customer portal, or review process. A form is a one-page app. Larger apps use the same editor, blocks, data bindings, and publication controls.
Start with the job the app should do#
- Open Apps in the workspace navigation. Start with a description, a template, or a blank page.
- Choose the source sheet and review the fields the app may read and write. Decide whether people should create a record, update assigned records, or review work.
- Start from Form, Application, Onboarding, Portal, or Review. Give the draft a name that describes its purpose.
- Use Pages to arrange the page tree, responsive canvas, and properties. Use Journey for the connected Flow, and Preview to test the experience with fictional data.
Compose a clear experience#
Combine sections, stacks, columns, and tabs with headings, Markdown, images, help text, inputs, progress, validation summaries, and useful empty or success states. Save reusable compositions to copy reviewed blocks into other drafts. Later changes to a composition do not rewrite an already published app.
Use conditional visibility to show questions when they matter. Hidden answers are cleared, and the server checks those conditions again at submission. Preview uses fictional records and simulated outcomes: it does not create records, send messages, execute integrations, or run the real journey.
Ask Ralti for a draft or improvement, then review and apply the proposal. The design operation uses selected field metadata and the current draft, not participant answers. AI cannot publish the app, invite people, widen its data bindings, or change its access policy.
Share the experience without sharing the workspace#
| Audience | Good fit | Access |
|---|---|---|
| Public | Intake and applications | Anonymous visitors create records on final submission; they cannot browse the sheet or update existing records. |
| Invited participants | Portals and ongoing work | A signed-in person accepts a single-use app invitation. The invitation does not make them a workspace member. |
| Audience groups | Teams of app participants | Managers assign a role and records to a group, with optional expiry. Each group grants only its explicit scope. |
Bindings select exact read and write fields, allowed actions, and record scope. Relationship choices respect the target binding. Public pickers expose only a publisher-approved choice list. Invited reviewers receive only permitted fields and assigned records; they cannot approve their own submission, and a rejection needs a reason.
Removing one group does not remove access granted independently by another group or personal invitation. Revocation and expiry apply to subsequent reads, writes, saved drafts, and workflow transitions. Group and invitation management remain private to workspace managers.
Connect pages with real work#
- Open Journey to use the existing Flow Studio. An App page is a step that waits for the participant.
- Connect page answers and the submitted record ID to later steps. Create/update steps must select an explicit app binding.
- Add an approval when a person should decide. Route a rejected review to a revision page that shows the review note, then back to approval.
- Use connected actions only with an available, permitted integration. Select the output properties that later steps may use.
- Inspect waiting or failed runs in the existing Flow operator view. Browser Back does not repeat or undo a committed action.
Publish a release you can trust#
- Review every page, binding, audience policy, and the exact published Flow version. Resolve setup issues.
- A workspace manager publishes the app. Editors can work on drafts without changing the live release.
- Share the hosted page, invite participants, or configure an approved HTTPS embed origin.
- Use release history to restore an earlier definition into a new validated release. Restoration preserves history and does not undo submitted records or completed actions.
New runs use the current release; active runs retain their compatible release. Publishing failure leaves the previous release in place. Pausing an app prevents entry and further actions without deleting its completed history.
Files, saved progress, and embedded apps#
File inputs use private storage. Uploads are checked, bound to the participant and input, and available only after validation; downloads recheck current access. Content checks are not an antivirus guarantee. Public visitors can explicitly save progress with a private return link. See Forms & public intake for expiry and return-link behavior.
Public and signed-in apps can embed on explicitly approved HTTPS origins. Signed-in embeds use a first-party sign-in popup and an in-memory app session, without depending on third-party cookies. If the popup cannot open, the hosted app is the fallback.
Improve the experience after launch#
Managers can inspect thirty-day submission, journey, page, release, denial, duplicate, and failure counts. These metrics exclude participant answers and provider results. Use the patterns to improve a draft, preview it, then publish a new release. Per-app pause and operator emergency controls may temporarily suspend capabilities while preserving saved work.