What are the optional Project tabs?

Last modified: June 23rd, 2026

On this page

Every Project in CloudCannon has three optional tabs in its top-level navigation: Publishing, Pull Requests, and Branches. These tabs are turned off by default. Your developer can enable any combination of them from the Details section under Project Settings.

The Publishing tab#

The Publishing tab shows a graph of how the Sites in your Project publish to each other. Each Card in the graph represents a Site; each arrow shows the Publish Branch relationship. A Site without a connected Publish Branch appears as a Card with no outgoing arrow.

A screenshot of the Publishing tab in a Project showing a graph of Sites and the publish flow arrows between them.

This tab illustrates where content moves to after you publish it, whether you have a single Site publishing to your Main Branch, a tiered setup where draft Sites publish to a staging Site and the staging Site publishes to production, or several branched Sites layered onto a release Site.

Clicking a Card opens that Site in CloudCannon. Clicking the Context Menu icon on the top right of a Card opens a menu with up to three actions:

  • Live site preview — opens the Site's Testing Domain in a new browser tab.
  • Branch site — opens the Create a Site page so you can start a new branched Site from this Site. This action only appears when Allow all branching is turned on for your Project.
  • Begin publish — opens the Publishing page for this Site, where you can review and publish changes. This action only appears when the Site has a connected Publish Branch.

For more information, please read our documentation on what publishing is and what Publishing Methods are.

The Pull Requests tab#

The Pull Requests tab is available on our Team or Enterprise plan.

Want to chat about whether this feature is right for you? Our support team is always happy to hear from you.

The Pull Requests tab lists open and draft Pull Requests in the Git Repository connected to your Project, alongside any Sites connected to each.

To see the Pull Requests tab, a Team Member needs the project:pull-requests:read permission on the Project. Team Members without the permission will not see the tab even when it is turned on. If you cannot see the Pull Requests tab in a Project where it should be visible, ask your administrator to check your permissions.

A screenshot of the Pull Requests tab in a Project listing open and draft Pull Requests, with the Sites connected to each one.

Each Pull Request appears as its own Card, showing its title, number, state icon, head branch, base branch, author, and the time it was last updated. Draft Pull Requests are marked with a Draft tag. Each Card has two buttons:

  • Open on [Git Provider] — opens the Pull Request in your Git Provider in a new browser tab.
  • Create a Site — opens the Create a Site page so you can connect the Pull Request's head branch as a new Site in your Project.

If a Site is already connected to the Pull Request's head branch, it appears inside the Pull Request Card, showing its name, Testing Domain, and build and sync status.

Pull Requests from outside contributors

The Pull Requests tab groups Pull Requests opened by contributors outside your Git Provider organization into a separate Pull Requests from outside contributors section. This makes outside contributions stand apart from internal Pull Requests in the list, so your team can recognize them at a glance and review them with appropriate care.

If you have Deploy Previews enabled for your Project, CloudCannon can automatically create Sites whenever someone opens a Pull Request in the connected Git Repository. However, CloudCannon does not automatically create Sites for Pull Requests from outside contributors. For more information, please read our documentation on using Deploy Previews to trigger Site creation and deletion.

The Branches tab#

The Branches tab lists every branch in the Git Repository connected to your Project, grouped into four sections: your Main Branch, Connected Branches (branches that have a Site connected), Orphaned Branches (branches that have a Site connected but no longer exist in the Git Repository), and Other Branches (branches without a connected Site).

A screenshot of the Branches tab in a Project listing the branches in the connected Git Repository, grouped by Main Branch, Connected Branches, Orphaned Branches, and Other Branches.

This tab gives you a single place to see what is in your Project's Git Repository alongside what your team has built in CloudCannon.

Each branch appears as its own Card, showing the branch name and the time it was last updated. If a Pull Request is open against the branch, the Card also shows a link to that Pull Request on your Git Provider. Each Card has two buttons:

  • Open on [Git Provider] — opens the branch in your Git Provider in a new browser tab.
  • Create a Site — opens the Create a Site page so you can connect this branch as a new Site in your Project.

If the branch already has Sites connected to it, those Sites appear inside the branch Card, each showing its name, Testing Domain, and build and sync status.

The Orphaned Branches section lists branches that Sites in your Project are connected to but which no longer exist in the Git Repository — for example, if someone deleted or renamed the branch in your Git Provider. Reconnect each Site in this section to an existing branch, or delete the Site.

Related Resources

Open in a new tab