Get to know the basics, and a few helpful tips & tricks along the way!Want to learn more about setting up your team? Look no further!Supplemental Slack info for you and your team.Tips and tools for beginners and experts alike.Useful tips for working together in Slack!Launching a new team or joining one for the first time?
Our easy-to-read guides help your team work better, together, from day one.Ready to level up? Browse our time-saving tricks and practical tips for
making Slack work for you.All kinds of teams thrive with Slack — take a look at our department-specific guides.
More coming soon!Get familiar with Slack Enterprise Grid for large organizations.
Enter your current password and new email address. Double-check that you've spelled the email address correctly.
Tap Update Email.
Check your inbox for an email from Slack with the subject “Confirm your new email address”.
Open the email and tap Confirm your email address.
The confirmation link will take you back to your Account page, where you'll see your new, confirmed address in the Email Address section.
Note: If single sign-on is enabled for your team, your Team Owner may restrict the ability for members to edit their personal information, including usernames and email addresses.
Update your email on multiple teams
While you can use a single email address when signing up for multiple Slack teams, the settings for each team are separate. To change the email address associated with another Slack team, sign in and repeat the steps above.
Missing confirmation emails
You should receive a confirmation email from Slack shortly after you update your address. If you’re not getting the email, try the following:
Check your spam or junk folder, and any tabs in your inbox.
Open your email settings and check for typos in the email address. If the address is incorrect, you can change it by following the steps above.
If you’re still not receiving the confirmation email, send us a note and we’ll do our best to help!
Thanks so much for your feedback!
Thanks for your feedback.
Oops! We're having trouble. Please try again later!