Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Help] Intended use case of "access list" field type #676

Closed
gryphonmyers opened this issue Feb 20, 2018 · 1 comment
Closed

[Help] Intended use case of "access list" field type #676

gryphonmyers opened this issue Feb 20, 2018 · 1 comment

Comments

@gryphonmyers
Copy link

I recently noticed the "access list" field type, and was hoping you might explain how it's supposed to work. For a moment, I was very excited because I thought you had added a way to provide per-entry overrides of collection-level permissions. I attempted a basic test though and it didn't seem to do what I was hoping.

@aheinze
Copy link
Member

aheinze commented Feb 20, 2018

Hi Gryphon,

the access list is just a field type to select groups and users. what you're doing with the data, is then up to you.

BUT...

I think what you're looking for are the "programmatic" access rules you can do in the collections settings:

image

so what I'm doing here is extending any read query going against the post collection. in that special case I check whether we have a logged in user and if yes I extend the query by adding my additional query condition.

So, if a user isn't in the admin group he'll always only get items he created.

This way you can build your very own access scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants