Granular Case Security Discussion 

Wlad opened the meeting by discussing a request from SA15 regarding the ability to hide individual high-profile cases from most users within an office while allowing access to only a small group of authorized personnel. 

Current Challenge 

Current security is primarily based on Case Type, allowing groups of users to access designated categories of cases. However, agencies are requesting the ability to: 

Examples discussed included: 

Concerns with User-Level Security 

Wlad explained that while restricting access appears straightforward, it introduces significant operational risks: 

Questions raised included: 

Rather than implementing a quick solution, Wlad requested additional requirements gathering from participating agencies. 

Existing Circuit Practices 

Users shared they already limits visibility for certain investigative case types, but these are generally pre-filing investigations rather than active criminal cases with: 

This highlighted the distinction between restricting investigative matters and restricting active filed cases. 

Discussion of Possible Solutions 

Several ideas were discussed: 

Wlad cautioned that adding another layer of security outside existing Case Type security could create maintenance and reporting challenges. 

Rather than deciding immediately, the group agreed additional real-world scenarios should be collected before designing a solution. 

STAC 3 Usability Enhancements 

Wlad reviewed several improvements currently under development for STAC 3. 

Case Selection Behavior 

Beginning with the upcoming release: 

This change addresses user complaints regarding accidental opening of Case Cards during navigation. 

Faster Data Entry 

The team acknowledged that users who primarily work with codes experience unnecessary delays caused by current dropdown behavior. 

Future improvements will focus on: 

These changes are planned for a future release rather than the current version. 

 Magnifying Glass Search Improvements 

Although the magnifying glass search allows searching by: 

experienced users find the extra interaction slows workflow. 

Additional improvements and shortcuts are being designed to streamline this process while preserving usability for newer users. 

Document Merge Workflow Improvements 

A significant discussion centered around document templates containing numerous checkboxes and selections. 

Current Problem 

Documents requiring many selections force users to: 

 Proposed Future Solution 

Rather than editing documents after merging, Wlad proposed creating a structured data-entry process where users would: 

Potential benefits include: 

The concept remains under development, and feedback from agencies will continue to shape the design. 

Request Module Completion Workflow 

The group discussed questions arising after implementation of recent Request module changes. 

Completion vs Status 

Rafael clarified an important distinction: 

Changing a Request Status does not complete the request. 

Instead: 

Simply assigning a status such as: 

does not close the request unless the completion process is used. 

 Results vs Comments 

Rafael explained that: 

Comments 

Results 

This distinction helps maintain consistent tracking throughout the request lifecycle. 

 Editing Completed Requests 

Several agencies reported situations where: 

Once completed, requests cannot currently be edited. 

Participants agreed this creates operational challenges. 

 Proposed Reopen Feature 

 Suggested the preferred solution would be an Undo Completion or Reopen Request function. 

This feature would: 

The group agreed this would better address accidental completion than allowing unrestricted editing of completed requests. 

Q&A  

Q: Can STAC currently hide an individual case from everyone except selected users? 

A: Not currently. The existing security model is primarily based on Case Type. The team is evaluating more granular security options but is gathering requirements before implementing a solution. 

Q: Why is granular case security complicated? 

A: Restricting visibility to only a few users creates risks such as missed deadlines, unavailable staff, reporting issues, and cases effectively disappearing from normal office workflows. 

Q: Will clicking a case automatically open the Case Card? 

A: No. An upcoming release changes this behavior so clicking selects the case, while the Case Card opens only by clicking its icon. (RC-6)

Q: Are improvements planned for faster data entry? 

A: Yes. Future releases will focus on reducing delays for users who primarily enter codes and rely heavily on keyboard navigation. (RC-7)

Q: Why are document templates with many checkboxes difficult in STAC 3? 

A: Users must manually select numerous options after merging documents. The team is exploring structured input methods that capture selections before merging to simplify the process. 

Q: Does changing a Request Status complete the request? 

A: No. A request is only considered completed when the Complete Request process is used. Simply changing the status does not close the request internally. 

Q: What is the difference between Comments and Results in a Request? 

A: Comments are intended for initial request information, while Results are intended to document follow-up actions and outcomes throughout the request process. 

Q: Can completed requests currently be edited? 

A: No. Once completed, requests cannot be modified. The team discussed adding a permission based Reopen/Undo Completion feature to address accidental completion.