Company Branches / Operational Units

A company rarely works from a single place. You have a head office, a couple of shops or showrooms, a warehouse point, maybe a service point. Company Branches (also called operational units) give you one tidy, shared list of those places — instead of everyone typing the branch into a free-text field and spelling it differently every time.

Once branches exist, you can tag your business records to a branch: a lead, a project, an invoice. Then a branch manager can see just their own leads, and you can filter any list down to one location.

When should I use this?

Turn this on if your company operates from more than one location and you want to:

keep a clean, reusable list of those locations (no more typos in a text field);
know which branch a lead, project or invoice belongs to;
let each branch manager work with their own branch's records;
filter leads, invoices, estimates, proposals and projects by branch.

You do not need multi-company switched on — Branches work on a single-company install too. (Multi-company is for running separate companies; Branches are locations inside one company.)

Open it

Branches live under the Companies console. Go to Setup → Companies (/admin/tsync_tenants) and click the Branches button on that page. From there you also reach Branch access and Branch mapping.

A staff member doesn't need to be a full administrator to manage branches — you can grant just the Company branches rights so a branch manager reaches this page and nothing else.

Start gently: the four modes

Branches have an activation mode you choose in the settings panel on the Branches console. It's your on/off ramp, so nothing changes on your daily screens until you're ready:

Off (the default) — the branch list exists, but it has no effect anywhere. Build your list in peace.
Shadow — a safe trial: you can build the list and map old values, still with no change to your day-to-day screens.
Hybrid — branch selectors, filters and badges start appearing on leads, projects and documents.
Canonical — fully enforced: a branch becomes required wherever you've configured it.

The same settings panel lets you choose where a branch should be required (leads, projects, financial or warehouse documents, HR), what to suggest as the default branch, and an access-enforcement setting — from none up to restricting each staff member to their own branches. That access restriction only takes effect in Hybrid or Canonical mode (in Off/Shadow nobody is ever locked out).

Recommended rollout: start in Off, build your branch list, switch to Shadow to map any old text values, then move to Hybrid when you want the selectors and filters to appear. Reach for Canonical only once everyone is used to picking a branch.

The Branches console

On Branches you manage the list itself:

Add a branch — click New branch, choose the company it belongs to, give it a name and (optionally) a short code, type and manager. The code must be unique within its company. A branch always belongs to one company.
Edit a branch — open it to change its name, code, type or manager at any time.
Default branch — the first branch you create for a company becomes its default. Use the star button to move the default to another branch. A company always has exactly one default branch.
Deactivate / archive — a branch you no longer use can be deactivated (it stops appearing in lists) or archived (hidden away). You can re-activate it later — nothing is lost.
Delete a branch — a branch created by mistake can be removed for good with the Delete button, but only once it is archived and only if it is not the company's default. TSync asks for confirmation, removes the staff-access grants that pointed at it, and writes the deletion to the audit log. If you only want to stop using a branch, archive it — deleting is for genuine mistakes, not for retiring a branch that has history.

Who can work in each branch

Open Branch access (the button on the Branches page) to decide which staff may work in which branch:

Pick a branch, then grant access to a staff member and choose their level: view, operate, manage, branch manager or branch admin. Remove a grant at any time.
Important rule: a staff member with no branch grants anywhere can use every branch. This is on purpose — nothing breaks while you set things up. As soon as you grant someone specific branches, they are limited to those, and other branches stop appearing for them (once enforcement is on in the settings panel).
Branch access sits under company access: a person needs access to the company before a branch inside it makes sense.

Branches on leads

Once the layer is in Hybrid (or Canonical), each lead can be tied to a branch:

Open a lead — a Branch block shows its current branch (or a reminder if a branch is required) with a dropdown to set the branch. You only see branches of the active company that you're allowed to use.
New leads can get a branch automatically: if your default-branch behaviour is use the company default branch, a brand-new lead with no branch is filled in with the company's default branch.
On the leads list a Branch column and badge show each lead's branch, and a Branch filter lets you narrow the list — handy for a branch manager who only wants their own leads.

Branches on projects, invoices, estimates and proposals

The branch also reaches your projects and commercial documents:

Open a project — a Branch bar at the top lets you set the project's branch (and a new project takes the company's default branch automatically).
Invoices, estimates and proposals inherit their branch from the project they belong to. A document raised under a project is automatically tagged with that project's branch (or the company default if it isn't linked to a project) — you don't have to set it by hand.
The invoices, estimates, proposals and projects lists each gain a Branch filter, so you can narrow any of them to a single branch.
Contracts, expenses and credit notes carry a branch too: a contract takes the company default branch, an expense inherits the branch of its linked project, and each of these lists also gets a Branch filter.
The Branch activity report (in the Reports console) counts leads, projects, invoices, estimates, proposals, contracts, expenses and credit notes per branch — a quick per-branch scoreboard.

Branches on warehouses

A warehouse can be assigned to a branch on its edit form (a Company branch field appears once the layer is on). Because all stock, movements and warehouse documents hang off the warehouse, assigning the warehouse a branch scopes its whole stock to that branch — staff who are restricted to certain branches then see only those warehouses (plus any left Unassigned, which stay global and visible to everyone). A warehouse can only take a branch of its own company, so the assignment can't leak stock across companies.

Branches on treasury places

A treasury place — a bank account, cash register or card you hold money in — can also be assigned to a branch on its edit form (Finance & Bank → Treasury places; the Company branch field appears once the layer is on). Because every balance and movement of a place hangs off the place itself, tagging the place with a branch scopes its whole cash flow to that branch — staff restricted to certain branches then see only those places (plus any left Unassigned, which stay global and visible to everyone). When the layer is on, a new place is pre-filled with the company's default branch, and a place can only take a branch of its own company.

Moving off an old "branch" text field

Did you keep the branch in a free-text custom field before (for example Filiala)? You don't have to re-type anything. Open Branches → Branch mapping:

It finds those branch-like custom fields and lists every distinct value with how many records use it.
For each value, map it to an existing branch or create a branch straight from it. The leads that used that text value are then filled in with the real branch automatically. Values you don't want can be ignored.

The BX lead view (the alternative lead screen) also gets the native Branch selector, so you set the branch from the same clean list no matter which lead screen you use.

Tip: there's no rush. Leave Branches Off until you actually work from more than one location, then move through Shadow → Hybrid at your own pace.