Overview
Partitions allow the Integriti system to be segregated into independent sites, each with its own set of global entities (Users, Permission Groups, Door Lists, Area Lists). This enables independent management of separate sites while still allowing — but not requiring — a global layer spanning all partitions. Partitions address deployment scenarios where treating all sites as a single global system is inefficient or undesirable.
Introduced: Integriti V19.0.
Deployment Scenarios
- Independent Unrelated Sites: Each site administered independently, preventing unintended changes across sites and reducing bandwidth/server load.
- Branch Office Scenarios: Most staff have site-specific access, with a small group of global users (security, management, cleaners) requiring access across all sites.
How Partitions Work
Global System (No Partitions)
Global Entities (Users, Permission Groups, Door Lists, Area Lists) are defined once and can reference entities in any controller. Integriti transforms this into controller-specific subsets automatically.
Partitioned System
Each partition creates a separate address space for Global Entities — they are scoped to their partition. This prevents interference between sites, including changes made via keypad or Integriti CS.
Hybrid System (Global + Partitioned)
Combines both approaches: individual sites managed independently within partitions, plus global entities that span all partitions. Example: branch office staff have partition-scoped access; corporate managers have global permission groups.
Prerequisites
- Integriti System Designer V19.0 or later with installer-level access.
- Partition License (996915) — partitions are a counted licensed feature.
- Controllers assigned to partitions still count toward Controller Connection licenses.
Step-by-Step
Creating a Partition
- In System Designer, right-click on a Site (or the Default Site) in the Navigation Tree.
- Select Add New > Add Partition.
- The Partition properties window opens — enter a Name and a unique Short Name (exactly 3 letters).
- Click Save.
Short Name: The partition’s 3-letter Short Name is prepended to the ID of all partitioned global entities. E.g.,
"U1"is the global User 1 (in all panels);"SR.U1"is a partitioned User in the “SR” partition, only in controllers with that partition.
Assigning Controllers to a Partition
- Right-click a controller in the Navigation Tree.
- Select the target Partition/Site to move the controller into.
Warning: This requires disconnecting and partially re-synchronising the controller. Moving a controller out of a partition removes all partitioned entities from that controller.
Working with Partitioned Entities
- Partitioned entities are created inside a partition. They cannot be moved out of their partition or to another partition.
- The Current Navigation Context (top of System Designer and GateKeeper) shows and allows changing the current partition.
- The “Current Site” selector automatically filters the system to the selected site or site and its sub-sites.
Duplicating Entities Across Partitions
- If an entity is accidentally created in the wrong partition, it must be deleted and recreated.
- To simplify: use the Duplicate option, and change the Partition of the duplicated entity before saving it.
Licensing
- Partitions are a counted licensed feature (just like Controller Connections).
- Partitions can be created before sufficient licenses exist, but controllers in unlicensed partitions will not connect.
- A controller inside a licensed partition still counts toward Controller Connection licenses.
Verification
- Create a test partition with a unique Short Name.
- Move a controller into the partition.
- Create a partitioned User — confirm the ID shows the Short Name prefix (e.g., “TST.U1”).
- Verify this user cannot be accessed or edited from outside the partition.
- Test hybrid mode: create a global user with permissions across all partitions.
Troubleshooting
| Problem | Resolution |
|---|---|
| Controllers won’t connect in partition | Verify sufficient Partition Licenses (996915). Check controller connection licenses. |
| Entity IDs showing wrong prefix | The Short Name is prepended automatically. Verify the partition’s 3-letter Short Name is correct. |
| Cannot move entity between partitions | Partitioned entities are locked to their partition. Delete and recreate using Duplicate before saving. |
| Unintended cross-site changes | Verify controllers are assigned to the correct partitions. Use Current Navigation Context to confirm active partition. |