Configure Access Control
Set up roles, permissions, and approval chains for your agency
How to Configure Access Control
This guide shows agency administrators how to set up access control in IronCase. You will learn to create roles, assign permissions, and configure approval chains.
You need administrator privileges to configure access control. If you do not have admin access, contact your department IT or IronCase administrator.
Before You Start
Gather this information before configuring access control:
- Your department's organizational structure
- Who needs access to what types of cases
- Your approval hierarchy (who approves what)
- Any special access requirements (task forces, specialized units)
Understanding Roles and Permissions
IronCase uses a role-based access control system.
| Concept | Description |
|---|---|
| Permission | A single action a user can or cannot perform |
| Role | A collection of permissions assigned together |
| User | A person who logs into the system |
| Assignment | Connecting a user to one or more roles |
Users can have multiple roles. Permissions from all roles combine.
Step 1: Access the Admin Panel
- Click your name in the top right corner
- Click Admin Settings
- Click Access Control in the left menu
You see three tabs: Roles, Users, and Approval Chains.
Step 2: Review Default Roles
IronCase includes default roles. Review them before creating custom roles.
- Click the Roles tab
- Click each role name to see its permissions
Default Role Summary
| Role | Purpose |
|---|---|
| First Officer | Initial response, scene documentation |
| Detective | Full investigation, evidence management |
| Supervisor | Team oversight, approvals, case assignment |
| Administrator | System configuration, user management |
| Read Only | View cases without editing |
Most departments use these default roles without modification.
Step 3: Create a Custom Role
If default roles do not fit your needs, create a custom role.
- Click the Roles tab
- Click New Role
- Enter a role name (example: "Crime Scene Tech")
- Enter a description explaining who should have this role
- Click Create
The role is created with no permissions. Add permissions next.
Step 4: Assign Permissions to a Role
Add permissions to define what the role can do.
- Click the role name to open it
- Click Edit Permissions
- Permissions are grouped by category. Check the ones this role needs:
Case Permissions
| Permission | What It Allows |
|---|---|
cases:view_assigned | View cases assigned to this user |
cases:view_team | View all cases on user's team |
cases:view_all | View all cases in the system |
cases:create | Create new cases |
cases:edit | Edit case details |
cases:close | Submit case for closure |
cases:assign | Assign cases to others |
Evidence Permissions
| Permission | What It Allows |
|---|---|
evidence:add | Add evidence items |
evidence:edit | Edit evidence details |
evidence:transfer | Transfer evidence custody |
evidence:submit_lab | Submit evidence to lab |
evidence:view_chain | View chain of custody |
People Permissions
| Permission | What It Allows |
|---|---|
people:add | Add persons to cases |
people:edit | Edit person information |
people:view_pii | View sensitive PII (SSN, DOB) |
people:view_sealed | View sealed records |
Checklist Permissions
| Permission | What It Allows |
|---|---|
checklist:view_own | View checklist items for own role |
checklist:view_all | View all checklist items |
checklist:complete | Mark items complete |
checklist:reopen | Reopen completed items |
AI Permissions
| Permission | What It Allows |
|---|---|
ai:query | Ask AI questions |
ai:summarize | Request AI summaries |
ai:draft_warrant | Request warrant drafts |
ai:analyze_evidence | Request evidence analysis |
Approval Permissions
| Permission | What It Allows |
|---|---|
approve:low | Approve low-risk actions |
approve:medium | Approve medium-risk actions |
approve:high | Approve high-risk actions |
approve:critical | Approve critical-risk actions |
- Click Save Permissions
Step 5: Set Up Approval Chains
Approval chains define who approves what type of action.
- Click the Approval Chains tab
- Click Edit Chain next to the chain you want to modify
Default Approval Chains
| Chain | What It Covers | Default Approver |
|---|---|---|
| Low Risk | Notes, summaries | Self (requester) |
| Medium Risk | Interview docs, lab requests | Detective or above |
| High Risk | Warrant drafts, digital requests | Supervisor |
| Critical Risk | Arrest recommendations, closures | Supervisor |
Modify an Approval Chain
- Click Edit Chain on the chain to modify
- Select who can approve:
- Self — The requester approves their own action
- Role — Anyone with a specific role can approve
- Specific User — Only named users can approve
- Supervisor — The requester's direct supervisor
- Optionally add a secondary approver for two-person review
- Click Save Chain
Step 6: Assign Roles to Users
Connect users to their roles.
- Click the Users tab
- Find the user you want to modify
- Click Edit Roles
- Check the roles this user should have
- Click Save
Assigning Multiple Roles
Users can have multiple roles. Common combinations:
| User Type | Roles |
|---|---|
| Patrol officer | First Officer |
| Detective | Detective |
| Sergeant | Detective + Supervisor |
| Crime scene tech | First Officer + custom CSI role |
| Admin staff | Read Only |
Step 7: Create User Groups (Optional)
For large departments, create groups to manage users more easily.
- Click the Users tab
- Click Manage Groups
- Click New Group
- Enter group name (example: "Homicide Unit")
- Add users to the group
- Assign roles to the group
All users in the group receive the group's roles automatically.
Best Practices for Role Hierarchy
Start Simple
Begin with default roles. Add custom roles only when needed.
Use Least Privilege
Give users only the permissions they need. Add permissions as requirements become clear.
Document Custom Roles
Write clear descriptions for custom roles explaining:
- Who should have this role
- What it allows
- Why it exists
Review Quarterly
Review access control settings every quarter:
- Remove users who have left
- Update roles for promotions
- Check that permissions match current needs
Separate Duties
For sensitive operations, require two people:
- One person requests
- Another person approves
This prevents single points of failure.
Troubleshooting Common Issues
User Cannot Access a Case
- Check that the user has
cases:view_assignedpermission - Verify the case is assigned to them
- Check for team-level access with
cases:view_team
Approval Not Reaching the Right Person
- Review the approval chain configuration
- Check that the approver has the required
approve:*permission - Verify supervisor relationships are configured correctly
User Has Too Much Access
- Review all roles assigned to the user
- Check group memberships that might add roles
- Remove unnecessary roles
Custom Role Not Working
- Verify all required permissions are checked
- Save the role after making changes
- Have the user log out and back in
Related
- Permission Types Reference — Full list of all permissions
- Role Permissions Reference — Default role capabilities
- Approval Levels Reference — What actions require approval
- Handle Approvals — How to review and approve actions