1
Fine-Grained Field-Level Permissions (Read/Update Subset Without Full Read Access)
Source: directus/directus#25822 · opened by @jm27
Summary Currently, Directus requires granting read access to all fields in a collection for a role to view and select individual items. This makes it impossible to restrict users to read + edit only specific fields without exposing all other fields. This feature request proposes allowing read and update access at the field level independently, so roles can be limited to only the fields they should see or modify. Basic Example For example, a posts collection with these fields: content slug hil_content hil_seo_title hil_seo_description Desired role: hil_user Read-only access: hil_content, hil_seo_title, hil_seo_description Update access: hil_content, hil_seo_title, hil_seo_description No access: content, slug Expected behavior: hil_user can open and edit only the hil_* fields for posts without being forced to read all other fields. Motivation Why: Current design forces roles to have read access to all fields to see records, even if they should only wo…
No pledges yet. Be the first to back this.
Comments
Similar requests
Code-first configuration of schema, roles and permissions
274 votes · 0 comments
Cannot use Access Control name in Flow Permissions; must use UUID
1 vote · 0 comments
Snapshot, diff, and apply for roles and permissions
19 votes · 0 comments
How hide collections' lists' visibility when they are required for a user inside an extension?
1 vote · 0 comments
Policy UX Enhancements for collection permissions management
2 votes · 0 comments
No comments yet.