Roleplay CAD Permissions & Role Management

Managing who can access what in a multi-department roleplay CAD system is one of the most critical — and often most overlooked — aspects of community administration. Without proper permissions, sensitive records end up visible to the wrong people, junior members can modify data they shouldn't touch, and the careful organizational structure you've built becomes meaningless. CDE CAD provides a comprehensive permission system that gives administrators precise control over every action, every module, and every piece of data in the system.

Understanding Role-Based Access Control

CDE CAD uses a role-based access control (RBAC) model, which means permissions are assigned to roles rather than individual users. When a user is assigned a role, they inherit all permissions associated with that role. This approach scales efficiently — instead of configuring permissions for each of your 200 members individually, you define permissions once per role and assign members to the appropriate roles.

Roles in CDE CAD are hierarchical within each department. A Sergeant role inherits all permissions of the Officer role below it, plus any additional permissions you define at the Sergeant level. This cascading model means you only need to configure the incremental permissions at each rank level, not the complete permission set. A Lieutenant gets everything a Sergeant has, plus supervisor-specific capabilities. A Captain gets everything a Lieutenant has, plus administrative functions.

Cross-department roles are also supported for members who serve in multiple capacities. A community administrator might need access across all departments, while a member who plays both a police officer and an EMS paramedic can hold roles in both departments simultaneously. CDE CAD resolves overlapping permissions by applying the most permissive setting, so users are never accidentally locked out of features they should have access to.

Granular Permission Controls

Module-Level Access

Control visibility and access to entire CAD modules including dispatch, records, warrants, reports, and administrative panels per role.

Action-Level Permissions

Fine-grained control over create, read, update, and delete operations within each module for precise access management.

Hierarchical Inheritance

Higher ranks automatically inherit lower rank permissions, reducing configuration overhead and ensuring consistent access chains.

Per-User Overrides

Grant or revoke specific permissions for individual users when role-based assignments don't cover edge cases in your organization.

Department-Level Permissions

Beyond role-based permissions, CDE CAD supports department-level access restrictions that create information barriers between agencies. A police department officer cannot access internal fire department records, and an EMS supervisor cannot view police internal affairs files. This departmental isolation is essential for communities that take organizational realism seriously and want to prevent metagaming across departments.

Department permissions also control which departments can see each other's units on the dispatch board and live map. In most communities, all departments see all units for coordination purposes. But some communities prefer operational isolation where each department manages its own operations independently, only sharing information through formal inter-agency communication channels. CDE CAD supports both models and everything in between.

Shared records — like civilian profiles and vehicle registrations — are accessible across departments by default, since any officer should be able to run a name or plate regardless of their agency. However, the ability to modify these shared records can be restricted to specific departments or roles, preventing unauthorized edits.

Discord Role Synchronization

For communities that manage their membership through Discord, CDE CAD's role synchronization feature eliminates the need for double administration. Map your Discord roles to CAD roles, and the system automatically keeps them in sync. When someone is promoted in Discord, their CAD permissions update immediately. When someone leaves your Discord server, their CAD access is revoked automatically.

The sync is bidirectional and configurable. You can set Discord as the authority (changes in Discord push to CAD) or CAD as the authority (changes in CAD push to Discord), or use a hybrid model where certain roles are managed in Discord and others in CAD. The mapping supports one-to-one and many-to-one relationships, so multiple Discord roles can map to a single CAD role or vice versa.

Best Practices for Permission Setup

Setting up permissions effectively requires planning. Start by mapping out your organizational structure — every department, every rank, and every specialized role. Then identify which CAD modules and actions each role needs access to. Apply the principle of least privilege: give each role only the permissions it absolutely needs, and nothing more. It's always easier to grant additional access later than to revoke access after sensitive data has been exposed.

Test your permission configuration thoroughly before going live. Create test accounts at each role level and verify that they can access everything they should — and nothing they shouldn't. Pay special attention to edge cases like members with roles in multiple departments, newly created accounts before role assignment, and the transition period when members are promoted or transferred between departments.

"Proper permission management is the difference between a professional community and chaos. CDE CAD gives us the tools to enforce our chain of command digitally, which reinforces it in roleplay."

Secure Your CAD Operations

Take control of who can access what with CDE CAD's comprehensive permission and role management system.