Skip to content

Should _Role collection be accessible to the clients? #1284

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

Closed
drew-gross opened this issue Mar 30, 2016 · 5 comments
Closed

Should _Role collection be accessible to the clients? #1284

drew-gross opened this issue Mar 30, 2016 · 5 comments

Comments

@drew-gross
Copy link
Contributor

Currently the _Role collection is not accessible to clients at all. We could configure it to be locked down by default, but otherwise adhere to regular CLPs. This could allow people to, eg. have each user create roles for "friends of " and give permissions to that role. On the other hand, that can already be accomplished via relations, so it may not make that type of app any easier.

@flovilmart
Copy link
Contributor

We should aim to parity here, before adding new fancy things no?

@drew-gross
Copy link
Contributor Author

Parity is certainly an important goal, but it needn't be the only goal.

@FridaySG
Copy link

Although I'm a little confused by the issue at hand, I feel I should mention my application uses a process which involves role creation from the client SDK's and does exactly what @drew-gross described. A "friends-of" type role is created with R/W permissions set exclusively to one user, and friends are added within the users relation by that user. Being able to maintain that functionality would be nice.

@flovilmart
Copy link
Contributor

AFAIK, the roles were available by the clients, protected by their ACL's only no?

@drew-gross
Copy link
Contributor Author

I meant locked down my default CLPs rather than default ACLs, but if it's already open, thats fine.

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

3 participants