System and permissions
How to define branches and clinics
Setting up branches and clinics for clinics running several locations, and the role of the branch prefix.
Where to find it
System SettingsBranches
The branch is the structure that separates operations for clinics running more than one location. The branch selector on calendars, the branch filter on lists and the branch field on supplier records all read this one record.
A clinic is a unit defined beneath a branch; one branch can hold several clinics.
Step by step
- Branch: enter a Name and a Prefix.
- Clinic: enter a Name and the Branch it belongs to.
- Once branches exist, attach users to the right one — the calendar opens on the user's own branch.
Tips and common mistakes
- Tip The branch prefix is how you tell at a glance which location a record belongs to. Keep it short and consistent ("IST", "ANK"); changing it later makes historical records harder to read.
- Careful Define a branch even if you run one location. Records left without one fall into no filter at all the day you open a second site.
Frequently asked questions
What is the difference between a branch and a user group?
A branch separates locations; a user group separates teams. They are independent: one branch can hold two language teams, and one team can work across two branches.
How do I attach a user to a branch?
On the user record. A user with a branch gets a calendar that opens on it by default.
Is defining a clinic mandatory?
If your operation does not need the distinction, one clinic is enough — the branch structure carries the rest.