Pulse

Branches in Pulse - Managing Multiple Locations From One HQ Account

How the Pulse Branches feature works: what a branch is, how to create one, how HQ staff access branch data, how cross-branch inventory visibility works, how to route tickets between locations, and what the group dashboard shows.

Pulse · 16 Jun 2026

▶ Playlist

Posts in this playlist

6 parts
  1. 1Understanding Branches in PulseWhat a branch is in Pulse, how it differs from your HQ organisation, what plan is required, and the branch lifecycle from creation to active to suspended.
  2. 2How to Create and Manage a Branch in PulseHow HQ admins create a branch, what happens during setup, how to configure branch settings, and how to invite staff into a branch.
  3. 3Accessing and Switching Between Branches in PulseHow HQ admins and staff switch into branch workspaces, what a branch session means, how to return to HQ context, and what branch users see versus what HQ sees.
  4. 4Cross-Branch Inventory in PulseHow HQ gets visibility into stock levels across all branches using catalogue SKUs, how to link branch items to the group catalogue, and how to read the combined inventory view.
  5. 5Cross-Branch Tickets in PulseHow to send a ticket to another branch or to HQ, how the receiving branch handles it, how to track outgoing tickets, and when to use cross-branch routing.
  6. 6The Branch Group Dashboard in PulseWhat HQ admins can see in the group dashboard: per-branch revenue snapshots, project health, staff activity, stock alerts, overdue invoices, and top performers across all locations.

Branches in Pulse let you operate multiple physical locations, offices, or business units under one master account. Each branch runs independently with its own projects, clients, inventory, and staff — while HQ retains visibility across all of them from a single group dashboard.

What this playlist covers

This playlist explains what a branch is and how it differs from your main HQ organisation, how to create and configure a branch, how staff access works across HQ and branches, how the cross-branch inventory view gives HQ visibility into stock across locations, how cross-branch ticket routing works between branches and HQ, and what the group dashboard shows at the HQ level.

Branches are independent organisations

Each branch is a fully self-contained workspace. Branch staff log in and see only their own location's data. HQ staff can switch into any branch to manage it, then return to HQ context at any time. The two sides are separate but connected through the group layer.

Who should read this

Read this playlist if you manage more than one physical location or business unit, are setting up a franchise model, need to route support tickets between locations, or want to understand what HQ can see across its branches without logging into each one separately.

Frequently asked questions

Can a branch create its own sub-branches?

No. Branching is one level deep. A branch cannot have its own branches. Only an HQ organisation can create and manage branches.

Do branches need their own Pulse subscription?

Yes. Each branch is billed at a flat monthly rate per branch. Payment is managed through the HQ account.