-
Notifications
You must be signed in to change notification settings - Fork 3
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
add copy to Invite a team member page and email #2262
Comments
hi @jonathanbobel and @CathyBeil could you both read the descriptive sentences in this ticket body to confirm the wording works for clarity on Invite and team member page? thank you much |
I might say something more like "Team members must be invited directly using their .gov email address, they cannot join from a forwarded invitation. Team members have 24 hours to accept an invitation and create a Notify.gov account. Expired invitations can be re-sent on the Team members page [link to page?]." |
ah, much more direct with who we're talking about and to. updating |
updated copy as of 3:12pmEST (went through it again to switch up how the sentences started). review please and thank you @CathyBeil |
Looks great! |
fantastic! next is @jonathanbobel when we have a moment to sync (if needed). maybe we can pair on this (?) to get the verbiage live this week |
hi @alexjanousekGSA ! let me know when you may want to schedule this work, so i can assist in adding more information as needed to this ticket. thank you! |
make it clear to the user when on the invite a team member website page to keep in mind to things: time sensitive nature of invites. the important of invites coming from inside notify.gov directly. Add as paragraph copy:
where: the Invite a team member page just below the link to 'learn more about user permissions'
what: Team members must be invited directly using their .gov email address, not from forwarded invitations. Invitation links to create a Notify.gov account are active for only 24 hours. Expired invitations can be re-sent from the Team members page.
The text was updated successfully, but these errors were encountered: