Skip to main content
SuperEmber onboarding is a guided launch path built around real work. A page visit never completes a mission. The checklist advances only when SuperEmber can verify the outcome in the workspace. SuperEmber onboarding map

​
What you will understand

By the end, you should be able to answer four questions without guessing:
  1. Which AI identity should receive this work?
  2. Should the work stay conversational or become a workflow?
  3. Where will the result, approval, and durable knowledge appear?
  4. What will SuperEmber review automatically, and when must a human decide?

​
The seven outcomes

​
How the identities fit together

​
Start or resume

Open Help & onboarding in the dashboard sidebar. Choose the outcome that matters most now, then follow the highlighted action. Choosing an outcome changes the recommended order. It never marks work complete. You can pause onboarding and reopen it later without losing durable progress.

​
Use the guided walkthroughs

Opening a mission starts a short walkthrough on the real dashboard screen. SuperEmber dims the surrounding interface, highlights the control you need, and anchors the instruction beside it.
  • Use the highlighted control when the walkthrough asks for a click or field entry. The next step appears only after that interaction.
  • Skip step bypasses one unavailable or irrelevant control without marking the mission complete.
  • Close or Esc exits immediately. Choose Show me in the mission banner to replay the walkthrough.
  • Your checklist advances only after the real product outcome succeeds. Finishing or skipping a walkthrough never fakes completion.
Permission-gated and feature-gated controls may not appear for every member. In that case, the walkthrough explains that the control is unavailable and lets you continue safely. Persistent onboarding checklist

​
How progress is verified

  • Channel completes after a linked channel has a successful inbound turn with a non-empty reply.
  • Personal Agent completes after your active Personal Agent has useful configuration.
  • Team completes after the workspace has a team-bound surface or a collaborative team.
  • Fleet completes after the workspace has a specialist beyond protected system agents.
  • Delegation completes after a delegated agent task finishes successfully.
  • Workflow completes after a workflow run succeeds.
  • Emberbase completes after you add a meaningful company knowledge page.
Continue with Connect a channel.