Branches

A branch splits the account by place or by team. Lists and new requests follow the branch you selected in the header. If the account has only one branch, you may not need this page every day.

List and switch

Under branches or account settings, add a branch with a name the team recognizes. Switch the active branch before you create a request or generate QR codes so you do not print another branch’s stickers.

The properties list and maintenance requests list show the current branch. If a request you know is missing, check the header branch before you recreate it. All branches appears for an account administrator, or for staff assigned to more than one branch — use it only when you need a wider scan.

On All branches, the properties card list, assets list, users list, service provider groups list, floor-plan list, and Working Calendar blackout list show a branch column (or card badge) and a branch filter. A property or asset shared with other branches shows the home name plus +N and a Shared mark. Filter by one branch to see that branch’s home records and the places shared with it. Staff assigned to only one branch do not see the column or filter — the header already scopes the list.

The customers list shows a customer when they are assigned to the header branch, or when their unit is visible there. The badge is the assignment. Assign users on the branch list is staff only — saving it does not change a customer’s assignment. A resident who scans a code is not asked for a branch.

Note: A resident who scans a code does not see your branch list. The code itself sets the place. Print that branch’s codes only on that branch’s doors.

The app refuses to delete a branch that still has properties, assets, requests, contracts, or other work. Leave it unused, or ask an administrator to re-file the work first. You can rename the Main branch — the Yes badge stays, and that is what marks it as Main. You cannot delete Main.

A new property follows its parent when it has one, otherwise the header branch. A new asset follows the property you attach it to. A new maintenance request follows the property or asset you opened it on. The create form shows which branch the record will be filed under. A new colleague is assigned to the branch you are viewing. QR and lobby codes still follow the header — switch first so you do not print another branch’s stickers.

Bulk import templates include an optional branch column. Leave it empty to use the header branch (or Main). Fill Jeddah on a row while the header is still Riyadh, and that row is filed under Jeddah. Unknown names reject that row. Updating an existing property or asset with a different branch in that column moves its home there and keeps extra shares. Reports follow the header branch, or the hub branch filter on All branches — Show and export keep that filter. Shared places count once by home.

To re-file a place that is already on the wrong branch, open the property and use Move to branch. The building, its child properties, assets, floor plans, and open requests move together. Completed and canceled requests stay unless you check the history option. The record keeps the same identity — QR codes and history stay on it. If a maintenance contract would then cover properties on two branches, the move is blocked until that contract is split. A subtree or asset move is also blocked if a child property, asset, or request already lives on a branch you are not assigned to.

You can also move a single asset, maintenance request, or maintenance contract from that record. An asset move takes its open requests and warns if the destination is not the property’s branch. A request move moves only that request and warns if the destination is not the place. A contract move files the contract row only and is blocked if the covered properties would sit on two branches. Staff assigned to only one branch do not see Move to branch.

A campus, headquarters, or plant that two teams both run can stay one record. On the property or asset profile, use Share with branch. Home stays the same; the extra branch can see the place. Sharing an asset alone does not put the property on the other branch’s property list; the asset still shows its property name. Reports that count properties or assets still count the home branch only. The same QR codes and history stay on that record. Do not clone the place. You cannot stop sharing the home branch, and the place must stay on at least one branch. To stop sharing one extra branch — or every extra branch — open Share with branch again and dismiss that chip. The home chip has no ×. The button stays even after every assigned branch already sees the place. Sharing a parent does not change children unless you check Also share child properties and assets. A new request on a shared place is filed under the header branch if that branch already sees the place; otherwise it is filed under home. Staff assigned to only one branch, or not assigned to home, do not see Share with branch.

Note: Deleting a branch is refused while it is the home of a property or asset. If the branch only had a share, that share is removed and the branch can be deleted once no other work remains.

What to read next

• Properties — a child follows its parent; a root building follows the header; share a campus from the profile; filter by branch on All branches.
• Assets — a new asset is filed under the property’s branch; you can share the machine from the profile; filter by branch on All branches.
• Account users and roles — the users list shows assigned branches on All branches.
• Service provider groups — pick a branch on the group; filter the list on All branches.
• Maintenance requests — a new request follows the property or asset; you can move one request from its profile.
• Maintenance contracts — move the contract row from the profile; split it first if it covers two branches.
• QR codes — print that branch’s codes only on that branch’s doors.
• Account settings — the branch list also lives under settings.
• Customers — the list shows a customer when their unit is visible; the badge is the assignment.
• Working Calendar — blackout list column and filter on All branches.
• Conversations — a new thread picks staff on the request’s branch; a joined thread stays visible.
• Reports — filter on All branches, or read the header-branch hint; shared places count once.

Ask about your next step