Our "Add User Permission" and "Add a Delegated Admin" screens are very similar. The new design in Figma consolidates these two screens into one. The Figma design currently allows multiple roles to be selected in a single form, but our backend can only handle one role assignment per submission at the moment.
Ideally, a new UI design should be finalized before implementation begins. However, we can start implementing it based on these general concepts. The upcoming design will likely be very similar to the one in Figma, but instead of checkboxes for the role table, it will use radio buttons. Upon each selection, the description field of the table will expand to allow forest client selections if the role is an abstract role.
The two "Add Permission" screens were combined into one during the refactor completed in Sprint 21.
Acceptance Criteria
[ ] Refactor /components/AddPermissions/RoleSelectTable.vue so that forest client selection occurs in the description column when expanded. Create a new component to abstract logic if needed.
[ ] Refactor components so they display the red * for required field
[ ] The Delegated Admin row should appear if and only if the user is an App Admin for a given app.
[ ] For the delegated admin row, use a dropdown for role selection
[ ] Form validation should work appropriately.
[ ] Ignore the expiration date and organizational unit in the current Figma design.
[ ] The send email checkbox should be checked as default for FAM prod for all app environments (Add comment regarding GC notify only send emails to a selected list of email addresses)
Description
Our "Add User Permission" and "Add a Delegated Admin" screens are very similar. The new design in Figma consolidates these two screens into one. The Figma design currently allows multiple roles to be selected in a single form, but our backend can only handle one role assignment per submission at the moment.
Ideally, a new UI design should be finalized before implementation begins. However, we can start implementing it based on these general concepts. The upcoming design will likely be very similar to the one in Figma, but instead of checkboxes for the role table, it will use radio buttons. Upon each selection, the description field of the table will expand to allow forest client selections if the role is an abstract role.
The two "Add Permission" screens were combined into one during the refactor completed in Sprint 21.
Acceptance Criteria
/components/AddPermissions/RoleSelectTable.vueso that forest client selection occurs in the description column when expanded. Create a new component to abstract logic if needed.Additional information
None selected (use radio button)
Selected with description field expanded