01 / Getting started

Choose a useful first workflow

Begin with a specific outcome: reviewing time, organizing customer follow-ups or handling an internal request. Name the person responsible for the workflow and the people who prepare, review and act on its records.

Agree what a successful pilot should demonstrate. Use the real steps your team needs, including rejected requests, corrections and changes of owner.

02 / Getting started

Set up the organization

Create your organization and confirm its headquarters country. Set up locations, units, positions and reporting relationships as needed, then invite the people involved in the pilot.

  • Keep organization and employee information accurate before other products rely on it.
  • Give each member the product access and permissions their work requires.
  • Check the requester, employee, manager and administrator views that apply to your workflow.

03 / Getting started

Bring in records deliberately

Check the import options and required fields in the product you are adopting. Review the source records, remove duplicates and use the product's validation and preview steps where available.

Each product has its own import format, so check it before you move records from another platform. Start with a manageable set of records and confirm the result before you continue.

04 / Getting started

Verify the handoff before expanding

Run the workflow with the people who will use it. Check ownership, permissions, review decisions and the records visible at each step.

Check outside delivery on its own. An email, a signature invitation or a payment-related action needs its own setup, and you confirm delivery from its outcome.

These principles support a self-service rollout. Migration services, implementation timetables and staffed onboarding are agreed separately.