Case Access Control: Team Derived vs Role Based

Case access can be limited in one of two ways - through Team Derived Access or through Role Based Access. Read through the information below for a summary of the pros and cons of each type of access or watch the video for a brief overview.

Note:

Regardless of the chosen access control method, team members will be able to see all cases that exist for their team; access control limits their ability to open and view details of the case without additional access being granted on an individual case basis. Users that are granted the "All Cases" system permission will be able to view all cases; those who are given Coordinator access to a specific model type will be able to view all cases for that model type only

Team Derived Access

Behavioral Case Manager uses team derived access to limit case visibility and access to members of the team with primary ownership of the case. Guest Users or Teams can be added to an individual case with either Read/Write or Read Only permission levels. Read/Write users can create, update, and manage cases, while Read Only users can view case information for awareness and collaboration purposes but cannot create cases or make any edits.

Role Based Access Control

Role Based Access allows District Administrative Users to create custom role types such as counselor, admin, or team member and designate per-model permissions (Read/Write, Read-only or No access) by assigning the role to the user. This allows for more granular access control as well as consistency between buildings. If a user is not assigned a role, they will default to No Access for all model types.

For example, counselors can be given read/write access to a Progress Monitoring model, while other team members are set to "no access" to help keep those notes confidential; or SROs can be set to "no access" for suicide risk assessments, and read-only for behavioral threat assessments.