Roles and Permissions

What are Roles and Permissions?

Within an organization, roles are created for various job functions. The permissions to perform certain operations are assigned to specific roles. Members or staff (or other system users) are assigned particular roles, and through those role assignments acquire the permissions needed to perform particular system functions. Since users are not assigned permissions directly, but only acquire them through their role (or roles), management of individual user rights becomes a matter of simply assigning appropriate roles to the user’s account; this simplifies common operations, such as adding a user, or changing a user’s department.

OPS-COM allows System Owners and Administrators the ability to set up roles that will restrict access to information and features in OPS-COM. 

In computer systems security, role-based access control (RBAC) or role-based security is an approach to restricting system access to authorized users. It is an approach to implement mandatory access control (MAC) or discretionary access control (DAC). Role-based access control is a policy-neutral access-control mechanism defined around roles and privileges. The components of RBAC such as role-permissions, user-role and role-role relationships make it simple to perform user assignments.

Setting up Roles and Permission in OPS-COM

OPS-COM allows System Owners and Administrators the ability to set up roles and permissions that will restrict access to information and features in OPS-COM. For example, you may wish to create a role for a Patrol Officer. You will set the permissions for this role and assign users the role of Patrol Officer when you would like to grant them permissions that match that job.

You may also decide to give a user access to OPS-COM but only give them permission to see or do one specific job. For example, if you only wanted the person to be able to validate parking but not have access to anything else.


Please see below for a quick video presentation on the set up of roles and permissions in OPS-COM. Alternately, you can follow along with OperationsCommander’s public training wiki here:

Before you begin it’s a good idea to sit down and plan out what roles you will need for your organization and what you want the person in each position to be able to see or do in the system.

It is important to note that Admin Users can not be deleted as they may be associated with past transactions. However, they can and should be made inactive in the case where someone leaves the organization.