Publish, version, and roll back

Your edits accumulate on a draft until you decide to publish. This keeps work-in-progress away from users until it’s ready.

Draft then publish

1. Edit freely, across instructions, model, knowledge, tools, and settings. It all gathers on one draft.

2. When ready, select Publish to commit the draft as a new version. Users now get the new version.

Versions and rollback

Every publish creates an immutable version, so you have a full history. If a change causes trouble, roll back to a previous version, restored as a new version, so the history stays intact. You can compare versions to see what changed.

Approval and emergency stop

• Your organisation may require approval before a publish goes live, you submit, a reviewer approves or rejects with a reason.
• If something goes wrong in production, an administrator can use the kill switch to disable an assistant (or the whole platform) immediately.

Note

Which of these apply depends on your organisation’s governance settings and subscription tier. Your administrator configures them.

Organising what you’ve built

Group assistants into collections for discovery, publish them to teams, and, where your organisation distributes assistants centrally, manage updates through modules.