Documentation

Handover

Give the customer a handover note of at most two pages, the exported settings bundle and workflow documents, and remove or reduce outside access.

At handover, the customer takes over the setup. The customer gets three things: the handover note, the exported settings, and an organization without outside access that it did not choose to keep.

The handover note

The note is at most two pages. It tells the person who maintains the setup what is set, why, how to change it, and what to watch. It does not repeat the docs: it links to them.

Use this template.

  1. About this setup. The customer, the organization in CoRoid, the date, and the implementers. Where the discovery document and the exported files are kept.
  2. What is set. For each area of Configure that you changed: the setting, in one line. Leave out the areas that use the defaults, and say that they do.
  3. Why. For each setting, the rule of the discovery document that it meets. A setting without a reason is a setting nobody dares to change.
  4. How to change it. For each setting, where it is and who may change it. Name the files in the repositories too: AGENTS.md, REVIEW.md, the review-rules folder and the skills.
  5. What to watch. The figures from the pilot, what a good value is, and what to do when a value goes wrong. Include who answers Needs you.
  6. Open items. The requests sent to CoRoid, and the exceptions in the go-live checklist, each with a date.

Export the settings and the workflows

  • The settings bundle. Export it in Settings → Data & legal → Export settings. The bundle records how the organization is set up. Secrets are only placeholders in it, so it holds no key or token. See Export and import settings.
  • Each workflow. Open the workflow, then choose More actions → Export. The file holds the workflow's steps and paths, its rules tables, its test situations and the names of the tools it needs. It holds no secret and no case.

Give the files to the customer, together with the note. The customer keeps them in its own systems, for example in a repository. Keep no copy yourself. The files are the record of what you delivered.

Remove or reduce outside access

Follow the access rules for consultants.

  1. Each consultant revokes the access tokens they made, under Settings → Connections → CoRoid MCP server → Access tokens.
  2. The customer removes each consultant in Settings → Members, or gives a lower role that the customer chooses to keep.
  3. Check Settings → Identity and access → Active sessions for sessions of people who left.
  4. Check that no connection uses a consultant's personal token. Replace any that does with a connection of the customer.

Done when

  • The customer has the note and the exported files.
  • Each consultant's access is removed, or reduced on purpose.
  • The person who maintains the setup has read the note.