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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: