Skip to content

Grant/Revoke rules #5360

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

Open
s8sato opened this issue Mar 16, 2025 · 0 comments
Open

Grant/Revoke rules #5360

s8sato opened this issue Mar 16, 2025 · 0 comments
Labels
question Further information is requested research

Comments

@s8sato
Copy link
Contributor

s8sato commented Mar 16, 2025

In the current default permission system, Grant and Revoke instructions follow a single rule: users can only grant or revoke permissions they already possess.

While granting is straightforward, revoking introduces a subtle issue:
A user can lose a permission if they grant it to others and then have it revoked by one of those recipients.

Possible Solution

One potential approach is to consider the hierarchical structure of the permission set.
For example, revocation could be allowed only if the revoker’s aggregate permission set is greater than that of the target account.
This approach could be implemented with the support of #5355, which enables permission aggregation.

Next Steps

Further research is required to refine the Grant/Revoke system design.

@s8sato s8sato added this to the 2.0.0-rc.2.0 milestone Mar 16, 2025
@s8sato s8sato added the question Further information is requested label Mar 16, 2025
@s8sato s8sato removed this from the 2.0.0-rc.x milestone Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested research
Projects
None yet
Development

No branches or pull requests

1 participant