Platform Agents: Create an Agent with the Wizard

Create a platform agent in six saved steps: basics and employee number, role charter, external account checks, onboarding prompt and restatement review, equipment and exam settings, then enable.

New platform agents are created with a six-step wizard (Platform Agents → New Agent). Each step saves on the server as you go, so you can stop halfway and pick up later: the agent card on the list shows the onboarding progress, and Continue wizard takes you back to the step you left. Nothing is live until the last step — the record starts as a draft and only becomes a working agent when you enable it in step 6. You need the agents.edit permission in ops.

Step 1: Basics — the employee number is issued here#

Fill in the name, work email, job title, department and avatar, then Save & continue. Saving creates the draft record and issues the employee number in the same action. Names must be unique — the system uses the name to line up the record; identity follows the number, not the name, and the number never changes once issued. If the number does not appear, the step is not done: save again to retry the issuance.

Step 2: Role charter#

Pick the scenario (the kind of job). The driver type, the role in one line and the role permissions prefill from the scenario registry — adjust them to the person. Then assign the role/topics, write the job duties (what the agent does and does not do), who they report to, and the email signature. Save writes the role permissions as this step’s full set — they replace, never merge with, earlier values. Changing the scenario, duties, reports-to or signature later re-opens step 4: the agent must restate against the new charter.

Step 3: External accounts — checked, not done, here#

• Muse account created: a second person checks it (the person who created the file cannot check their own work on this item) and notes who created the account and when. Never write any credential here.
• Work email created: two stages. Mark it created once the mailbox exists; it counts as fully verified only when the agent sends the verification email from that mailbox and you confirm receipt (you can close it here or in step 4 — fill in the mail’s subject as received).
• Email password handed to the agent: also second-person checked. The password must be delivered through the vault secure card into the agent’s own vault — saved only on your side does not count. State the handover fact in one line; never type the password itself anywhere on this page.
• Login account bound: if the agent signs in with a platform account, the binding itself is done in the account system; this step only confirms the fact once the account shows as bound.

Step 4: Onboarding prompt and restatement gate#

The system generates the onboarding prompt from the charter (scenarios with their own template use it; otherwise the generic template is used and the page says so). Copy it, send it to the agent through your usual channel, and mark it sent. The agent studies it and restates, in their own words, their identity, duties, boundaries and red lines — paste the full restatement back here. Then check it against the checklist for the scenario, point by point: pass it only when every point is confirmed and the step-3 verification email has been received. Rejecting requires a note saying what is missing; rejected restatements stay on record and a new one can be pasted.

Step 5: Equipment and exam settings#

Work through the equipment list for the scenario and tick each item as you hand it over, adding a reference name (the tenant name, the key’s name — never a value). Then review the exam configuration and the probation configuration: the fields and defaults come from the scenario registry, values are validated on save. This step only delivers and configures — exams are started, graded and judged elsewhere, not in the wizard.

Step 6: Review and enable#

The summary shows all six steps with who finished each and when. When you click Enable, the server re-checks all five steps against the current data — if anything no longer lines up (for example a field changed after its step was saved), enabling stops and names the step to fix, with a shortcut to it. On success the agent is enabled into exam preparation. Enabled is not the same as confirmed in post: the later gates (exam, probation, confirmation) proceed in the onboarding flow, and permissions still open gate by gate from the lowest tier.

Drafts: resume, abandon, delete#

• Resume: the list card shows the progress and a Continue wizard button; the detail page has an Onboarding progress section with the same shortcut.
• Abandon: a draft you no longer need is abandoned from inside the wizard, with a reason that stays on record. The draft is kept as a stopped record, not erased.
• Delete: wizard drafts and any agent with an issued employee number cannot be physically deleted — use abandon, or pause/archive for enabled agents.