The File Permissions page gives administrators a consolidated view of access controls across all files. Use it to audit, adjust, and enforce your organization's data access policies.
Understanding the File Permissions page
Navigate to File Permissions in the Document Library sidebar. This page lists every file alongside its permission assignments. It is designed for administrators who need to review access patterns across the entire library rather than file by file.
How permissions work
Every file has an owner -- the user who uploaded it. The owner always has full control. Beyond ownership, access is granted in two ways:
Direct share -- A specific user is granted Read, Edit, or Delete permission on the file.
Role-based share -- A role is granted permission, and every user with that role inherits it.
Both types can coexist on the same file. If a user has access through both a direct share and a role, the highest permission level applies.
Permission codes
Butterflai uses three granular permission levels:
Read -- View and download only.
Edit -- View, download, rename, and update the file description.
Delete -- Full control, including permanent removal.
These are cumulative. Edit includes Read. Delete includes Edit and Read.
Managing permissions for multiple files
Use the File Permissions page to select multiple files and adjust their permissions in bulk. This is particularly useful when onboarding new team members or restructuring role assignments.
Permissions and user roles
File permissions and platform roles are related but distinct. A user's platform role (e.g., Admin, Manager, Viewer) determines what they can do in the application. File permissions determine which specific files they can access. An Admin with broad platform permissions still cannot see a file unless they are the owner, have a direct share, or hold a role that has been granted access.