Versioning & Collaboration
Every prompt in Prompt Studio maintains a complete version history. This enables safe experimentation, easy rollback, and team collaboration.
How Versioning Works
When you create a prompt, it starts at version 1. Every subsequent save creates a new version automatically. The prompt document always contains the current (latest) version's content, while all previous versions are stored in a separate version history.
Version Fields
Each version records:
| Field | Description |
|---|---|
versionNumber | Sequential version number (1, 2, 3, ...) |
content | The prompt content at this version |
variables | Variable definitions at this version |
changeNote | Optional description of what changed |
createdBy | User who made the change |
createdAt | Timestamp of the change |
Viewing Versions
On a prompt's detail page, click the Versions tab to see the complete history. Each version shows the version number, change note, author, and date. Click View to expand and see the full content of any version.
Restoring a Version
To restore a previous version:
- Open the Versions tab
- Find the version you want to restore
- Click Restore
- Confirm the action
Restoring does not delete newer versions. Instead, it creates a new version with the restored content. For example, if you restore version 2 while on version 5, the result is version 6 with the content from version 2.
Sharing & Visibility
Visibility Modes
| Mode | Who Can See | Who Can Edit |
|---|---|---|
| Private | Owner + shared users | Owner only |
| Public | All users in the organization | Owner only |
Sharing with Users
- Open the prompt detail page
- Go to the Sharing tab
- Search for users by name or email
- Click Share to grant read access
- Click the remove button to revoke access
Multi-Tenant Behavior
In multi-tenant deployments:
- Users can only share with members of the same organization
- Public prompts are visible only within the organization
- Organization admins can see all prompts in their organization
In single-tenant deployments:
- Users can share with any user on the platform
- Public prompts are visible to all users
Best Practices
- Write descriptive change notes when editing prompts — your team will thank you
- Use tags consistently across your organization for easy discovery
- Start prompts as private, then share or make public once tested
- Duplicate before experimenting to preserve the working version
- Use variables for values that change between environments or use cases