1
Ability to Hide Visual Editor Extension for Specific Roles
Source: directus/directus#25912 · opened by @SerhiiMazurBeetroot
Summary Add the ability to hide or disable the Visual Editor extension in the Directus Admin based on user roles. This would allow administrators to control access more precisely, improving security and reducing unnecessary UI clutter for users who do not require this tool. Basic Example If a user role is set to not have access to the Visual Editor, the extension should be hidden from their interface. Motivation Currently, all roles that can access the Admin app see the Visual Editor extension. In many projects, this is not desirable: Editors may need access to create and manage content visually. Contributors or view-only roles should not see or use it. The lack of role-based control leads to: Potential security risks if roles gain unintended editing capabilities. Cluttered UI for users who only need limited functionality. Reduced flexibility in managing permissions across large or diverse teams. The expected outcome is a cleaner, more secure, and role-approp…
No pledges yet. Be the first to back this.
Comments
Similar requests
Code-first configuration of schema, roles and permissions
274 votes · 0 comments
Automatic Language Selection in Translations interface for Visual Editor
5 votes · 0 comments
API Testing UI (Swagger-like) with Role-Based Simulation
5 votes · 0 comments
Better control by roles
1 vote · 0 comments
How hide collections' lists' visibility when they are required for a user inside an extension?
1 vote · 0 comments
No comments yet.