The branch in JJ Skill Builder acts as a flexible path that directs how skill checks, user roles, and access rules are applied in the platform. Understanding what branch does in JJ Skill Builder helps teams keep permissions aligned with real business units and reduces accidental configuration errors.
By tying settings to a branch, the system can reflect store locations, service centers, or regional offices without changing core skill logic. This structure supports clear ownership, focused reporting, and smoother day to day operations for admins and analysts.
| Branch Type | Typical Use | Visibility Scope | Permission Impact |
|---|---|---|---|
| Organizational Root | Top level hierarchy | All child branches | Global policies applied downward |
| Store Front | Retail locations | Single store staff | Location specific rules |
| Support Region | Geographic support | Regional teams | Region based access |
| Project Squad | Temporary initiatives | skill checks and views scoped to the project
Routing Logic Inside JJ Skill Builder
How Branch Determines Skill Evaluation
Each skill evaluation follows rules that first look at the active branch context. These rules decide which policies, score weights, and data filters apply when users interact with assessments. The branch value is read from the user profile or from the runtime context at evaluation time, keeping behavior consistent across devices and sessions.
Data Segmentation and Branch Mapping
Branch controls which records, incidents, and performance events are visible inside analytics dashboards. When a branch filter is active, only data tagged with that branch or its children appears in charts and reports. This design supports multi tenant setups, where each location or department operates with strict data separation while sharing a common skill framework.
Configuring Branch in Practice
Defining Branch Hierarchies
Administrators set up branch records in the configuration area, linking each entry to codes like regions, cost centers, or site identifiers. Parent branches group child branches, and those children inherit settings unless overridden. Clear naming and stable IDs make it easier to maintain mappings as the organization grows.
Linking Skills and Branch Rules
Skill builders can attach branch conditions to specific skills, deciding who can perform checks, approve tasks, or escalate issues. Conditions may include minimum roles, required certifications, and branch membership, so the same skill behaves differently under different branches. These conditions are evaluated at runtime, reducing manual approvals and human error.
Branch Driven Access Control
Restricting Views by Branch
View permissions are filtered based on branch assignment, ensuring that staff only see the data relevant to their operational area. A branch filter applied at the profile level automatically limits list pages, detail views, and export options. This aligns with compliance expectations and prevents accidental exposure of sensitive metrics.
Managing Edit Rights Across Branches
Edit rights are granted when a user role matches the branch context and the associated skill conditions are satisfied. Admins can define exceptions for supervisors or power users, allowing temporary cross branch actions when justified. Audit logs track every change, preserving transparency and supporting regular reviews.
Best Practices for Branch Management
- Use stable branch codes that align with HR or finance identifiers to simplify mapping and audits.
- Document the purpose of each branch, including parent child relationships, in a central knowledge base.
- Test skill conditions in a development environment before promoting branch changes to production.
- Schedule regular reviews of branch membership to ensure permissions stay aligned with team structures.
- Leverage inheritance at the parent branch level to avoid duplicating rules across many child entries.
FAQ
Reader questions
Can I assign more than one branch to a single user profile?
Yes, you can map multiple branch codes to a profile, and the platform uses the active context to decide which branch rules apply during skill checks.
How does changing a branch hierarchy affect existing skill evaluations?
Updating parent child relationships or moving users between branches can change which policies and filters apply, so admins should test major moves in a sandbox environment first.
What happens if a skill has branch conditions that no longer match the user context?
The skill appears in read only mode or is hidden from the user, depending on how the rule set is configured in the builder interface.
Do branch filters impact historical performance data in reports?
Reports respect active branch filters, which means historical views can be segmented by branch over time if the branch code was recorded with each event.