This article explains how Filter setup permissions work across different user roles, and what each role can (and cannot) do.
Filter Sets allow you to save groups of filters for quick reuse. Depending on your role, you may be able to create personal defaults or manage organisation-wide defaults.
User Roles Overview
Filter permissions are based on three roles:
Admin
Contributor
Viewer
Each role has different levels of control over organisation-wide and personal Filter Sets.
🛠 Admin Permissions
Admins have full control over Filter Sets across the organisation.
Admins can:
Create, edit, and delete organisation-wide Filter Sets
Set default Filter Sets for organisation-wide use
Override or update existing organisation Filter Sets
Create and manage their own personal Filter Sets
This ensures Admins can maintain consistency across teams while adapting default views as reporting needs evolve.
✏️ Contributor Permissions
Contributors can personalise their experience but cannot modify organisation-wide defaults.
Contributors can:
View and use organisation-wide Filter Sets
Create and save their own personal Filter Sets
Set their own personal default Filter Set
Contributors cannot:
Edit organisation-wide Filter Sets
Override or delete organisation-wide defaults
This allows Contributors to tailor workflows without affecting shared team configurations.
👀 Viewer Permissions
Viewers have the most limited Filter permissions.
Viewers can:
Use organisation-wide default Filter Sets
Save their own versions of Filter Sets for personal use
Viewers cannot:
Edit organisation-wide Filter Sets
Set organisation-wide defaults
Override existing shared Filter Sets
This ensures consistency while still allowing individual flexibility.
Summary Table
Role | Use Org Filters | Edit Org Filters | Set Org Defaults | Save Personal Filters | Set Personal Default |
Admin | ✅ | ✅ | ✅ | ✅ | ✅ |
Contributor | ✅ | ❌ | ❌ | ✅ | ✅ |
Viewer | ✅ | ❌ | ❌ | ✅ | ❌ |
If you’re unsure which role you have, contact your organisation’s Admin.