Merge access policies #1041
Merge access policies #1041
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
david-crespo
force-pushed
the
merge-policy
branch
from
6c5f3bc to
2612089
Compare
| const { data: orgPolicy } = useApiQuery('organizationPolicyView', { | ||
| orgName: projectParams.orgName, | ||
| }) |
There was a problem hiding this comment.
If a user doesn't have permissions for this, what would happen?
There was a problem hiding this comment.
Great question! That could happen if they lacked the read permission on the org (you can read the policy if you can read the resource), and they would not be able to see any permissions that are inherited from the org. The best we could do is not error and maybe say "there may be other people who are are getting access through the org, but you can't see the org so we can't tell you".
This is another argument against doing this client-side, possibly also an argument for tweaking the permissions model.
|
Closing for now. API needs discussion. |
This is about #1024, but it is equally likely to end up as fuel for me to ask the API to do this as it is to end up merged.