-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Update the invitation process to include the role of the person being invited to a workspace #54794
Comments
@anmurali If a user invites multiple members at once, should the selected role be applied to all the invited members? |
Edited by proposal-police: This proposal was edited at 2025-01-04 02:33:28 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
pass the above App/src/libs/actions/Policy/Member.ts Line 750 in b23c478
we can use the
App/src/libs/actions/Policy/Member.ts Line 691 in b23c478
instead of default
App/src/libs/actions/Policy/Member.ts Line 750 in b23c478
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
@truph01 The Proposal looks good to me. I believe that role would be assigned to all invited members. |
@anmurali what are you thinking to change it to? Perhaps something like "Confirm invite"? |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Workspace - Member - Invite member - select (or enter) email or phone number - add message
Let's add the role as the final step in the invitation process
@jamesdeanexpensify @shawnborton should we also change the title of this step?
The text was updated successfully, but these errors were encountered: