Individuals and businesses — public site, data, and workflows

Replace [account] with your team slug in every path below.

Public site

Your public site is what anonymous visitors see on the tenant host (subdomain or custom domain).

1. Edit content in Admin → Public Site at /home/[account]/admin/public-site.
2. Work iterates through draft → pending review → approved → published, depending on your role:
   • Editors save drafts and may submit for review.
   • Reviewers approve or reject (public_site.review).
   • Publishers (often owners) publish approved work (public_site.publish).
3. Validate changes with preview at /public-site-preview/[account] (and nested paths for inner pages).

Lead capture: Embedded public forms write to Admin → Public Site Leads at /home/[account]/admin/public-site/leads. Monitor for spam and export or process leads according to your policies.

Data entities

Structured business data is defined under Admin → Data entities at /home/[account]/admin/dataentities.

Practices:

• Start from the smallest set of entities you need for the first workflow; expand later.
• Name fields the way your team already speaks (“Purchase order number” not cryptic internal codes in user-visible labels).
• Align entities with forms so users are not asked twice for the same fact.

Forms

Author reusable definitions at Admin → Forms (/home/[account]/admin/forms). Attach them to:

• Workflow steps (data capture during a process).
• Public site blocks (lead generation, surveys).

When you change a form that active instances depend on, coordinate with process owners to avoid confusing in-flight work.

Workflows

Designing processes

Users with workflow admin access open Admin → Workflow admin at /home/[account]/workflow/admin to:

• Maintain versions with effective-from / effective-until dates.
• Add steps, gateways, and transitions.
• Bind each step to a form and optional data entity.
• Restrict view or capture permissions per step via roles.

Operating processes

Everyone with membership on the team can use Workflows at /home/[account]/operativeworkflow to start or continue instances.

Task inbox at /home/[account]/operativeworkflow/tasks aggregates assigned work items so users do not hunt through every workflow.

Navigation and sign-in experience

Optional tools include:

• Navigational Menu Editor — /home/[account]/admin/navigation-menu
• Team sign-in customization — /home/[account]/admin/team-sign-in

Use these to match your brand and simplify how employees reach Workflows and Dashboard.

For guided walkthroughs, see Tutorials (public site, entities, forms, workflows).