Publish a Classic AppFormerly Interfaces
Each page of a NocoDB classic app has two versions: the draft that you edit in the builder, and the published version that all other users see. You can redesign pages, test changes and preview freely. The people who use the classic app are not affected. Draft availability can change with your plan.
Publish changes
- In the builder topbar, click Publish. The button is enabled when there are unpublished changes. Classic apps with pending changes also show an "unpublished changes" badge in the sidebar.
- Review the publish dialog. It shows the pages that the publish will update.
- Optionally, mark pages as keep as draft. These pages are not part of this publish. The rest of the classic app publishes without them.
- Confirm the publish.

The publish dialog also lists your other classic apps that have unpublished changes. Select the ones to publish at the same time.
When a page of a classic app that you selected points at a deleted page or field, the dialog lists the page under Broken references, with a count of the broken buttons, bookmarks, record links and deleted fields. Users of the classic app do not see those elements. The publish still goes through, so fix the page and publish again.

After a publish, NocoDB counts the page links that will not open for your users: links to a page that was deleted, that is not published, or that belongs to another project. The message names the number of broken links. The publish still goes through, so fix the links and publish again.
What viewers see
| Who | What they see |
|---|---|
| Classic app users | Always the latest published version of each page. |
| Builders | The draft, while in the builder. Before you publish, use Preview and Preview as to check the draft as any role or user. See Classic app builder. |
Users cannot see a page that was never published. The page shows after its first publish.
Last updated on