Your changes reach members only when you publish. This page covers publishing, the badges that show where a plugin stands, the **Versions** page, and switching a plugin off or deleting it.
## Publish
The button at the top of a plugin reads **Publish** until its first version, then **Publish changes**.
1. Choose **Publish** or **Publish changes**.
2. Confirm. Members' agents get the new version on their next request.
There's nothing to upload or install: publishing is all it takes to update everyone who receives the plugin. See <mention-page url="https://app.notion.com/p/41b4815eed4f8141b20af00c49c519cd">Owners and receivers</mention-page>.
Before you can publish, the plugin needs:
- a description, set in **Configure**;
- at least one skill or connector;
- instructions and a description for every custom skill.
While something is missing, the button is dimmed and a **Before you publish** note says what to add. It's also dimmed while changes are saving, and once everything is published.
<callout icon="💡" color="blue_bg">
	**Approval may apply.** Where your organisation or the plugin's team requires approval, **Publish** becomes **Request approval**, and an approver publishes the plugin. Organisation Admins see **Approve and publish** instead, which publishes at once and records the version as self-approved. See <mention-page url="https://app.notion.com/p/41b4815eed4f819b94baf97c828d62ce">Approval</mention-page>.
</callout>
## What a version is
Each publish creates the plugin's next version, numbered from 1. A version is a fixed snapshot of the plugin's skills, preferences, files and connectors, and it never changes. The newest version is live: it's the one members' agents get.
A version records which managed skills it holds, not their release. Members' agents get managed skills from your organisation's managed skills release, so Tilt's updates reach them without a new publish. See <mention-page url="https://app.notion.com/p/41b4815eed4f81ed8b58cfe210582143">Managed skills releases</mention-page>.
## Status badges
A badge beside the plugin's name, and in **Plugins**, shows where it stands with members.
<table header-row="true">
<tr>
<td>Badge</td>
<td>What it means</td>
</tr>
<tr>
<td>**Not published**</td>
<td>The plugin has no version yet, so members get nothing.</td>
</tr>
<tr>
<td>**Version N**</td>
<td>Members get version N, and nothing has changed since.</td>
</tr>
<tr>
<td>**Unpublished changes**</td>
<td>You've saved changes that members don't have yet.</td>
</tr>
<tr>
<td>**Disabled**</td>
<td>**Enabled** is off in **Configure**, so members get nothing.</td>
</tr>
</table>
## The Versions page
A plugin's **Versions** page lists every version, newest first, with when it was published, who published it, how many skills and connectors it holds, and how often Base served its skills and files.
- **Live** marks the latest version, the one members' agents get.
- **Approved** or **Self-approved**, beside who published it, marks a version an approval published.
## Restore a version
Restoring brings back an earlier version's content as unpublished changes. Members keep the live version until you publish.
1. On **Versions**, open the version's actions menu and choose **Restore this version**.
2. Confirm.
3. Publish when you're ready to share it.
If the plugin's current content isn't in any version, restoring discards it, and the confirmation says so. Restoring the live version's content simply discards your unpublished changes.
## Switch a plugin off
**Enabled**, in the plugin's **Configure**, pauses access without deleting anything.
- Turn it off and members' agents stop getting the plugin's skills from their next request. Its skills, preferences and versions stay.
- It takes effect without publishing, and publishing leaves the plugin switched off.
- Turn it back on and members get the latest published version again, not your unpublished changes.
Base can't recall instructions an agent has already loaded or files it has already fetched. To be sure a member works without the plugin, have them start a new chat.
## Delete a plugin
<callout icon="⛔" color="red_bg">
	**Deleting a plugin can't be undone.** It removes the plugin and all its versions from your organisation, and members' agents can no longer use its skills.
</callout>
1. In the plugin's **Configure**, under **Delete plugin**, choose **Delete plugin**.
2. Confirm.
Switching a plugin off or deleting it needs permission to publish for the plugin's owner. Deleting is refused while an approval request for the plugin is waiting.
## Troubleshooting
- **"A request to publish this plugin is waiting for approval. Approve, decline or withdraw it first."** You tried to delete or move a plugin with a waiting request. Decide or withdraw the request in <mention-page url="https://app.notion.com/p/41b4815eed4f819b94baf97c828d62ce">Approval</mention-page>, then try again.
- **"… is not in your organisation's managed skills release."** Remove the skill, or have an Admin choose a release that has it. See <mention-page url="https://app.notion.com/p/41b4815eed4f81ed8b58cfe210582143">Managed skills releases</mention-page>.
- **"This plugin changed in another session."** Someone else saved the plugin meanwhile. Choose **Reload the plugin**, then publish.
- **"Publishing this plugin needs approval. Request approval instead."** Approval was switched on after the page opened. Reload the page and choose **Request approval**.
## Related
- <mention-page url="https://app.notion.com/p/41b4815eed4f813ea7a0cf9654f1867d">Edit skills</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f819b94baf97c828d62ce">Approval</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f8141b20af00c49c519cd">Owners and receivers</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f81ed8b58cfe210582143">Managed skills releases</mention-page>