Skip to content
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

Incorrect prompt when removing user from org #9758

Closed
charlesmathias opened this issue May 20, 2024 · 1 comment · Fixed by #9759
Closed

Incorrect prompt when removing user from org #9758

charlesmathias opened this issue May 20, 2024 · 1 comment · Fixed by #9759
Labels
bug p3 Should be addressed when able

Comments

@charlesmathias
Copy link

Slack thread 🔒.

Currently, when a Billing Leader or Org Admin removes a user from their org, they see the following message:

Are you sure?
This will remove User from the organization. Any outstanding tasks will be given to the team leads. Any time remaining on their subscription will be refunded on the next invoice.

The final sentence here is no long er true as, on the Team plan, we currently charge for the number of active users that they have on the day of the invoice.

Additionally, this is not relevant for Enterprise-level contacts.

I propose we update the text to read:

Are you sure?
This will remove User from all teams within the organization. Any outstanding tasks will be given to the respective team leads.

@charlesmathias charlesmathias changed the title Prompt when removing user from org needs to be updated Incorrect prompt when removing user from org May 20, 2024
@jordanh jordanh added the p3 Should be addressed when able label May 20, 2024
@github-project-automation github-project-automation bot moved this to To triage in Product May 20, 2024
@jordanh
Copy link
Contributor

jordanh commented May 20, 2024

Assigned priority during scrub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p3 Should be addressed when able
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants