User groups are collections of users who work together or need access to the same students. They allow you to organize your staff into teams and control which students each team can access.
Key Benefits
Need-to-know access: Ensure users only see information relevant to their role
Simplified management: Add or remove multiple users at once
Team collaboration: Assign incidents and actions to entire groups
Audit clarity: Track which teams accessed specific records
Compliance: Demonstrate appropriate access controls for inspections
Organize staff by the year groups they support.Examples: Year 7 Pastoral Team, Year 10 Team, Sixth Form TeamAccess: Each group accesses only their year’s students
Key Stages
Organize staff by key stage for smaller primary schools or cross-year responsibilities.Examples: KS1 Team, KS2 Team, KS3 TeamAccess: Each group accesses students in their key stage
Safeguarding Team
DSLs and DDSLs who need school-wide access.Example: Safeguarding TeamAccess: All students across the school
Specialist Teams
Staff with specific responsibilities across year groups.Examples: SEN Team, Attendance Team, Wellbeing Team, Behaviour TeamAccess: All students (or specific student groups based on need)
Leadership Teams
Senior leaders who need oversight.Examples: Senior Leadership Team, Pastoral Leadership TeamAccess: All students for reporting and oversight
External Partners
External agencies or temporary staff with limited access.Examples: Social Workers, Educational Psychologists, GovernorsAccess: Specific students only (typically with Viewer role)
Clear names make access controls easier to understand and audit.
Align with your school's structure
User groups should reflect how your school is organized:
Year groups for secondary schools
Key stages for primary schools
Houses or divisions if that’s how you assign pastoral responsibility
Don’t create user groups that don’t match real teams.
Keep user groups focused
Each user group should have a clear purpose:
✅ “Year 8 Pastoral Team” - clear, specific
❌ “Year 8 and Some Year 9 and SEN” - confusing, hard to manage
If access needs are complex, create multiple user groups and add users to several groups.
Review memberships termly
At the start of each term:
Remove users who have left or changed roles
Add new staff to appropriate groups
Review whether student group links are still appropriate
Check for users in the wrong groups
This keeps access controls accurate and compliant.
Document access decisions
Keep a record of why specific user groups have specific access. This helps during inspections and demonstrates accountability.Example: “External Partners group has access to specific students only (linked manually as needed). Used for social workers and educational psychologists. Access reviewed monthly.”
Use 'All Students' access sparingly
Only these groups should typically have “All Students” access:
Safeguarding Team
Senior Leadership Team
Attendance Team (if they need to see everyone)
Most pastoral staff should be limited to their year group or key stage.
Combine with student groups effectively
User groups are most powerful when combined with student groups:
Create student groups for different cohorts (years, houses, vulnerability levels)
Link user groups to appropriate student groups
Use auto-update rules on student groups so access stays current
You can create sophisticated access patterns by combining multiple user groups and student groups:
Example: Multi-Layered Access
Scenario: A staff member is:
Year 9 Form Tutor
SEN Coordinator for KS3
Part of Safeguarding Team
Setup:
User is in 3 user groups:
“Year 9 Pastoral Team” (linked to “Year 9 Students”)
“SEN Team” (linked to “SEN Support - KS3”)
“Safeguarding Team” (linked to “All Students”)
Result: User has combined access from all three groups. They can see:
All Year 9 students (via group 1)
SEN students in Years 7-9 (via group 2)
Any other student school-wide (via group 3)
The highest level of access (Safeguarding Team → All Students) effectively grants full access, but the granular group memberships document their specific responsibilities.
Ask: “Should all these people still have this access?”
2
Review student group links
Check which student groups each user group can access:
Click the Student Access tab for each user group
Verify the links are still appropriate
Remove links that are no longer needed
3
Check for orphaned users
Look for users who aren’t in any user groups:
Go to Settings → Users
Filter by “Not in any group”
Either add them to appropriate groups or investigate why they have no groups
4
Document the review
Keep a record of your audit:
Date of review
Changes made
Issues identified
Actions taken
This demonstrates due diligence during inspections.
Signal provides an Access Audit Report that shows all users, their roles, user groups, and which students they can access. Run this report termly and save it for compliance records.Go to Reports → Compliance → Access Audit Report.