Getting Startedlifecycle

Setup Checklist

How does a new organization know what is configured and what is still missing?

Each organization carries a setup checklist recorded per module and per step — setup progress is data, not a wiki page. Until setup is complete, sign-in routes users toward setup rather than into a half-configured workspace.

How it works

Setup state lives in the platform itself. For each organization, the steps of each module’s setup are recorded individually, so what has been configured — and what has not — is a queryable record shared by everyone involved in the implementation rather than a document someone maintains on the side.

The platform acts on that state. After sign-in, an organization with incomplete setup is routed toward setup instead of the normal workspace, and two gates sit early in the path regardless: the organization’s disclaimer must be accepted, with each acceptance recorded in an audit log, and the working languages are registered so every later screen appears in them.

The steps themselves are completed in real configuration screens, some of which carry first-run wizard variants — the organization chart, for example, can be built step by step in wizard mode. Once people are added, position-keyed onboarding tasks generated in HCM carry the same structured-start idea down to each new employee.

What the record holds at once

Held constantSetup Checklist 4 states, at the same time

  • Per-module steps, recorded per organization

    Setup progress is stored step by step for each module the organization licenses.

  • Routing while incomplete

    Sign-in checks setup state and routes unfinished organizations toward setup rather than daily screens.

  • Disclaimer and language gates

    Acceptance is recorded per user, and languages are registered before the rest of setup proceeds.

  • Wizard-mode setup screens

    First-run variants of configuration screens, such as the org chart, support step-by-step initial builds.

See setup checklist running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.