#2769: Org Member Page - Invite A New Member - [NL] #2974
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket 2769
Resolves #2769
Changes
Context for reviewers
Setup
Code Review Verification Steps
Navigate to /Members;
(Verify that the ticket ACs have been met - copied below)
Figma design here - invite a new member
Figma design here - invite a new member but with some radio buttons filled out
From the "Members" page, when you click "Add a new member button" (see this Figma, top right blue button) it should open to a new page called "Add a new member"
Have an email section that is required (see accessibility note)
Have a radio button field for "Member access" which should correlate to a role for a member (see accessibility note)
If a user chooses "Admin Access" conditionally display another set of radio buttons for "Admin access permissions" and vice versa for "Basic access" display "Member access + basic member permissions" radio buttons (see additional context)
Make sure to have the "cancel" button go back to the "Members" page
The "Invite member" button should not fully work, it should still check the form validity but does not need to create a record for User PortfolioPermissions or send an invitation to a user
No user should be able to see this page if they do not have the proper edit permissions
Follow best practices for error messages
As the original developer, I have
Satisfied acceptance criteria and met development standards
Ensured code standards are met (Original Developer)
Validated user-facing changes (if applicable)
As a code reviewer, I have
Reviewed, tested, and left feedback about the changes
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots