You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[DELETE EVERYTHING ABOVE THIS LINE BEFORE SUBMITTING YOUR ISSUE]
Describe your issue in as much detail as possible.
I have a few different types of users. I also have several separated geographic areas that shouldn't be interacting in any way. I.e. an "admin" user assigned to the "New York" region shouldn't be able to view anything out of the New York region, and they should get special access to some objects related to that region.
Setting an ACL, I would love to be able to grant Read/Write access for a user who is in both the admin Role and the New York Role. Currently to achieve this, if I have m types of users and n geographic regions, I need m X n roles. It would be extremely convenient to be able to just work with the basic roles instead of having to do a complex role set up.
Steps to reproduce
Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.
Have various combinations of users that fit categories, need to give access to users who fit multiple roles.
Expected Results
simple && role set up.
Actual Outcome
Complex role set up.
Environment Setup
Server
parse-server version (Be specific! Don't say 'latest'.) : ~2.3.2
Operating System: OSX
Hardware: MBP 2015
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): All
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
[-][Feature Request] Role1 AND Role2 ACL / CLP access[/-][+]Role1 AND Role2 ACL / CLP access[/+]stale commentedon Sep 18, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
parse-github-assistant commentedon Dec 6, 2021
The label
type:featurecannot be used in combination withtype:improvement.