Consultant — public site, data, and workflows

Use this checklist when you are configuring a client workspace you are allowed to manage. All URLs use the client team slug in place of [account].

Public site

The tenant public site is the client’s outward-facing presence (often on a subdomain or custom domain managed by the platform).

1. Edit pages and branding under Admin → Public Site at /home/[account]/admin/public-site.
2. Saves create draft revisions. Use Submit for review when the client’s process requires approval.
3. A user with review permission (public_site.review) approves or rejects pending revisions.
4. A user with publish permission (public_site.publish, commonly an owner) publishes an approved revision so visitors see it.
5. Use preview (/public-site-preview/[account] and nested paths) to see draft or unpublished approved content as visitors would, outside the main app chrome.

Leads: Public forms post to the platform; review them under Admin → Public Site Leads at /home/[account]/admin/public-site/leads.

Data entities

Data entities define structured records (fields, types, relationships) that back operational data and can be referenced from forms and workflow steps.

• Open Admin → Data entities at /home/[account]/admin/dataentities.
• Model entities to match the client’s nouns (for example Expense, Vendor, Project).
• Keep names and field labels aligned with how the client’s staff already talk about their work—this reduces training time.

Coordinate with Forms and Workflow admin so entities and forms stay consistent.

Forms

Dynamic forms are authored under Admin → Forms at /home/[account]/admin/forms.

• Reuse form schemas across workflow steps and public site embeds where possible.
• Version significant changes so in-flight workflow instances remain understandable.

Workflows

Design and administration

Admin → Workflow admin at /home/[account]/workflow/admin is where definers:

• Create workflow definitions with versions and effective dates.
• Map steps to forms and optionally to data entities.
• Assign step permissions (who may view or complete a step) using system roles or account custom roles.

Running work

Workflows (operative) at /home/[account]/operativeworkflow lets end users:

• See active workflows they may start.
• Start a new instance and complete steps in order (including gateways and approvals as modeled).

Task inbox at /home/[account]/operativeworkflow/tasks lists tasks assigned to the current user across workflows.

Navigation and team sign-in branding

If the deployment uses a navigational menu editor or team sign-in customization, configure them under:

• /home/[account]/admin/navigation-menu
• /home/[account]/admin/team-sign-in

These affect how the client’s users move through the product and how team login pages look.

Handoff tip

Before you leave a client project, ensure at least one owner can publish the public site and edit workflows without you—so operations do not depend on consultant access alone.

Step-by-step guides: Tutorials.