Separation between agencies
Membership in one agency should not expose another agency’s records. Our design calls for checking both agency ownership and user permissions whenever case information is accessed.
SECURITY AT KAMODO CANVASS
Protecting agency information.
Your agency needs control over who can access operational records and a way to review important activity. Those needs guide our security design as Kamodo Canvass develops.
AGENCY ACCESS
Access by authorization
Agency records should be available only to authorized personnel. Our access model calls for verified agency membership and role-based permissions, so a successful sign-in alone does not grant access to operational information.
Permissions by responsibility
- 01
Administrator
Control who belongs to the agency and which permissions they receive.
- 02
Supervisor
Oversee case activity with permissions tied to supervisory responsibilities.
- 03
Officer
Access permitted cases and contribute field information within assigned permissions.
Access is based on agency membership and permissions, rather than an officer’s assigned geographic zone.
INFORMATION & ACCOUNTABILITY
Separate records. Accountable activity.
A record of important actions
Leadership needs to know who changed a record and when. Our audit design calls for a protected history of case creation, assignment changes, and membership updates to support internal review.
BEFORE DEPLOYMENT
Security review before adoption
Bring your agency’s security and procurement requirements to the evaluation. Review available controls, access policies, and data-handling requirements with your IT and security team before entering sensitive operational information.
This page describes the principles guiding development. It is not an attestation of implemented controls or a claim of CJIS compliance or other security certification.
Discuss your security requirements