Planned Group Assignment Permission Behavior #429
Closed
jacobsen9026
announced in
Announcements
Replies: 2 comments
-
This change has taken effect as of v0.9.4.2024.07.23.0231 |
Beta Was this translation helpful? Give feedback.
0 replies
-
FYI the logic diagram incorrectly shows a need for assignment permission to add a group as a member, this is not the case and behavior is identical to adding user members, only read permissions are required. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As of version 0.9.3, Blazam's permission requirements for assigning users and groups to groups is not consistent. Access differs based on whether assigning from the member, or the parent group. This was caused by an incorrectly designed foundation that ignored these two different assignment approaches.
Therefore, the plan is to migrate all assignment authority to the groups. Assign permissions will no longer be available to User type in Access Levels. Adding the Assign/Unassign action to Groups will allow assigning any users or group the delegate has read access to.
Logic Diagram
This change is planned for the next update, ETA unknown.
Beta Was this translation helpful? Give feedback.
All reactions