Onboarding: prepare the team and complete your personal path

Team onboarding is preparation for working together. It is separate from initial account registration and from confirming participation in a project.

1. 1
   Open Onboarding setup

   Choose the team and project. A manager can prepare a team standard before there is a project; personal paths become available when the team is connected to project work.

2. 2
   Choose a template

   Use the standard or an available team template. Where permitted, use New template to create reusable guidance rather than rewriting it for every project.

3. 3
   Explain the working context

   Add the team’s purpose, communication rules, reporting expectations, resources and access instructions.

• Responsibility and expected outcomes: what the person owns and which work products they deliver.
• Decision boundaries: what they can decide independently and what needs approval.
• First-week outcomes and required launch actions: the first practical steps.
• Handoffs: who supplies an input, who receives it, whether they review or approve, and what proves the handoff is complete.
• Tools and resources: where the person works and which references or access they need.

1. 1
   Review the setup

   Check the team, project, personal responsibilities, workflow and access information.

2. 2
   Use Save and prepare paths

   Save the standard and prepare the project-specific onboarding for the participants.

3. 3
   Review Overview, Team paths and Project context

   Inspect readiness and risks, people’s progress, the scope and working rhythm. Use Questions to answer or resolve uncertainties.

4. 4
   Refresh when the project changes

   Use the refresh control to update onboarding from current project data, and review any resulting changes.

1. 1
   Open your assigned path

   Check the project and your role. Use the chapter list or Previous / Next to move through the material.

2. 2
   Read the relevant context

   Review the company and project, your role, collaboration, working rules, tools and knowledge. Process projects can include process-specific context.

3. 3
   Use I understand

   Confirm a chapter once you have reviewed its manual steps. Your progress is saved and contributes to the shared readiness view.

4. 4
   Use Ask when something is unclear

   Ask within the chapter instead of guessing. Return to Questions for replies and clarification.

Readiness combines participant progress with project checks such as participation, access and available project context. Automatic checks follow their source records and are not completed by pressing I understand.

A participant completes their own path. They do not confirm the whole team or set the project schedule. The manager resolves missing project setup and responds to questions within their permissions.

A process-linked template can explain the process purpose, inputs, outputs, roles, KPIs, controls and starter work. It belongs to the relevant process and team, not to every company project. Review the process context alongside the personal responsibilities.

• Check that the correct team is linked to the project and that you have access.
• The team owner or authorized manager must prepare the launch before personal paths become available.
• If Retry onboarding appears, retry loading; missing data is not the same as a completed path.
• Completing a personal chapter does not replace accepting a project invitation or getting access to a required tool.