Handover

An implementation ends with documents the client signs and a trail they can rely on. superglue produces both from the work already done, so handover is a matter of exporting and sharing rather than writing things up.

Deliver the documents

The reports produced during the engagement are artifacts under Brain → Artifacts:

• The discovery and readiness report
• The agreed mapping, with decisions and exceptions
• The validation and reconciliation results
• The cutover plan and post-go-live sync overview

Each artifact downloads as PDF or an editable Word document with your organization’s branding, or as interactive HTML. Spreadsheet artifacts download as Excel workbooks. Ask the agent to combine the engagement’s findings into one closing report when the client wants a single document.

To share with the client directly, use Share on the artifact and create a link. A link shows the artifact’s current saved version. If the artifact is a questionnaire or sign-off form, the client fills it in through the link, and you receive an email when they submit.

i

Ask the agent for a sign-off form. It builds a form with the reconciliation summary and an acceptance section. The client’s confirmation lands in the project with a timestamp.

Deliver the audit trail

Every run of every tool is recorded with its trigger, the user or schedule that started it, the credential used, the input, each step’s result and the final output. The Runs page filters by tool, status, time and system, and the search covers inputs, outputs and errors.

For the closing pack, export the relevant runs or ask the agent to summarize the migration runs into an artifact: what was loaded, when, in how many batches, with which reconciliation result. Admins can enable Store Run Results under Settings → Runs to keep full inputs and outputs for the retention period the client requires.

The Activity view under Control Panel adds who created, changed and shared each resource, which completes the trail for compliance reviews.

Control who sees what

On Team and Enterprise plans, your organization can include the client’s own staff. Use access rules to give them exactly what they need:

• Viewer access to the sync tools lets the client’s finance team run them and see results, without changing them.
• Viewer access to the systems lets those tools run, while credentials remain the client’s own or a specifically shared service account.
• A custom role per client keeps engagements separated when several clients share one organization.

Credentials are never shared automatically. Sharing a tool grants the system access it needs, but a recipient uses their own credential or one you share deliberately. See Role-based access control.

Leave the client self-sufficient

If the client will operate the syncs themselves, hand over three things:

1. Notifications routed to their channel, so failures reach them first.
2. The Investigate flow on the Runs page, so their team can ask the agent to explain and repair a failure.
3. The playbook or written instructions for the recurring tasks, such as month-end reconciliation, attached to the project.

For clients who want AI assistants in their own tools, an MCP server can expose selected superglue tools to Claude, Copilot-style clients or Langdock with the client’s own logins. See Creating an MCP server.

Close the project

Archive the project when the engagement ends. Sessions and tasks are hidden, while artifacts, tools and run history stay available. Disable schedules that are no longer needed rather than deleting them, so the history stays complete.