Yes. System administrators can temporarily change the permissions of a user's profile or add an investigator to a particular case file within the system. This allows detectives of various units to work together on a difficult case without changing their role's permissions permanently or gaining access to irrelevant department files.

Public upload links are configured as anonymous, one-way ingestion portals. The citizen uploading the media is classified by the system as an external contributor. This role grants permission to upload files and enter basic contact info, but provides zero visibility into your agency's case files or directories.

In this case, the security system will automatically deny access and send out an access denied message.

No. When a prosecutor shares discovery materials, defense recipients access the files directly within the iCF workspace. They navigate the standard iCF layout, but permissions are strictly limited to viewing and downloading only the specific files approved for disclosure. By keeping defense activity inside the core platform, every action is automatically logged to the case’s primary audit trail. Depending on agency authorization and sharing configurations, this access can be set to view-only or download-enabled, ensuring external users never gain credentials or entry to your primary agency vault.

Industry best practices recommend reviewing user access permissions regularly and whenever personnel roles change. Conducting routine audits, along with immediate updates when staff are promoted, transferred, or leave the agency, ensures users maintain only the access required for their current responsibilities and keeps your security policies up to date.

No. RBAC rules run instantaneously in the software's background database layer during the login and folder navigation phases. It checks user permissions quickly without impacting file download speeds or media playback performance for personnel in the field.