Why Strategic Role & Permission Planning Matters
User roles and permissions define what information users can see and what actions they can perform within CommandCentral Aware. This granular control is essential for several reasons:
Data Security: Your primary goal is to protect sensitive operational data. Permissions ensure that only authorized personnel have access to specific information, such as sensitive unit locations.
Operational Integrity: By restricting actions to authorized roles, you prevent unintended changes or misuse of system functionalities. For example, crime analysts might view cameras, but would not be able to control them.
Enhanced Focus & Efficiency: Tailoring the user experience means each role sees only the relevant information and tools for their duties, reducing clutter and improving efficiency.
Empowering Day-One Users: Properly configured permissions, especially when combined with capabilities like automation rules, can make the system intuitive even for new users, guiding them to critical information without requiring deep expertise.
Key Advice for Planning User Roles & Permissions
Embrace the Principle of Least Privilege: Grant users only the minimum permissions necessary to perform their specific job functions. Avoid giving broad access unless absolutely required.
Define Clear Roles Based on Job Functions: Consider the different types of users who will interact with CommandCentral Aware (e.g., dispatchers, command staff, analysts, field supervisors).
For each role, list out exactly what information they need to see and what actions they need to perform. For instance, a dispatcher might need to see all unit locations, while a specific command role might need access to sensitive unit groups (like SWAT or undercover).
Consider Access to Administrative Functions
Beyond day-to-day operations, remember that certain administrative tasks, like bringing in custom map layers or creating new users, require specific permissions.
Ensure that only trusted administrators have these access rights.
Plan Ahead & Seek Support
Strategic planning before implementation is crucial. Think through all potential scenarios and user needs.
Do not hesitate to contact our Customer Success team if you need assistance in getting your permissions structured correctly.
Why Use Single Sign-On for CommandCentral Aware?
Single Sign-On makes logging in easier by allowing users to access CommandCentral Aware with the same credentials they already use for their organization’s sign-on process. This means users won’t have to remember yet another username and password to access the system.
Talk with your Motorola Solutions representative to see if Single Sign-on is available for you.
NOTE: If your agency has additional CommandCentral solutions, you may consider having a dedicated group specific to CommandCentral Aware user roles and permissions. Alternatively, you may provision CommandCentral Aware user permissions based on existing roles within CommandCentral Admin.
For more CommandCentral Aware knowledge, visit the CommandCentral Aware Manual.
