3
$CURRENT_USER on Steroids
Source: directus/directus#25942 · opened by @gavalierm
Summary This feature describe how to enhance $CURRENT_USER in filters and role politics. Basic Example Ability to set permision by something like this: $CURRENT_USER.nested_field.is_something === true Motivation The whole permissions is based on one thing: The Current logged user. And we have just ID and just only on "right" side of Equasion at the moment. So Collection it self (or nested value in collection) needs to have somwhere the "user" asi field. This is very limited option to have complex permision based on just ID of $CURRENT_USER. (or i m missing something?) Detailed Design The idea is: Imolement $CURRENT_USER as logical block, which can be used on left side, or just on separated filter rule block. Maybe is just possible to merge actual collection.fields list with "directus_users.[current_user].fields" list to both? So selection dropdown will be with AND logic between collection fileds and current_user …
No pledges yet. Be the first to back this.
Comments
Similar requests
Default Value for Many-to-One Dropdown using $CURRENT_USER
12 votes · 0 comments
Multi-tenancy using the same database
52 votes · 0 comments
Add support for "dynamic value" in permissions/filters/presets
173 votes · 0 comments
Computed fields and/or View tables
3 votes · 0 comments
Defaultvalue on "Many to Many" fields.
5 votes · 0 comments
No comments yet.