Resolve Slack invitation errors after domain migration

draft · accounts-and-access domain-migrationemail-redirection

Generated by docuprocessor (prompt article/v3) · 2026-04-22 08:36

Source thread

thread_id: spaces/AAAA05BdS6s/threads/JfOuaePfED4 · 17 msgs · first 2024-07-09 · participants: Tech ATech B

Tech A 2024-07-09 16:42

Hey guys, I'm getting this screen at slack website. Im logged in with a PDS account from albany that has a PRO plan, not sure if this feature is included on this plan. I see that Secure Channels are included, but not sure. I see that the invitation has been sent to the new domain, not to the old one. Maybe that can be the issue?

image/png image.png

The screen displays a Slack web page indicating an invitation from **Magdalena Perez** from **Teem** to work in the **#albany** channel with 1 other organization. A secondary message reads **"Ready to upgrade?"** stating that shared channels require a **Slack paid plan** and prompting the user to upgrade their account to accept the invitation. No error codes, equipment identifiers, or diagnostic indicators are present.

Tech A 2024-07-09 16:42

(no text)

image/png image.png

This is a Slack web page displaying an invitation acceptance error message. The message states: **"This invitation can only be accepted by omalbany@pdsmgmt.com"** and notes the invitation was sent by **Magdalena Perez** from **Teem**, for the channel **#albany**, involving **Teem and 1 other organization**. A secondary message advises that if sent to the wrong email address, someone from Teem can resend the invitation.

Tech B 2024-07-09 16:44

@Josue Nasini did you read my email about Slack sent to everyone yesterday?

Tech A 2024-07-09 16:44

Yes. That they have to log in with the old account

Tech A 2024-07-09 16:44

I just want to double check with you that the plan is being paid there, so they have to send the invitation there..

Tech B 2024-07-09 16:45

lets go over the steps again Once again, the steps for Slack are: - open https://hqrcmsworkspace.slack.com/ - enter youremail@HQRCMS.COM - receive a code from youremail@PDSMGMT.COM - select PDS-HQRCM workspace when prompted. Its easy to spot it by the # of users in case there are few similar ones. The largest # of users is the workspace you need. - enjoy

Tech B 2024-07-09 16:47

there is no omalbany@pdsmgmt.com account. it should be omalbany@hqrcms.com

Tech A 2024-07-09 17:09

Aomalbany@hqrcms.com That account is not receiving a slack invitation code at the new domain email, was that account created before the migration? I tried to send an email to the old domain, but I didin't received it

Tech B 2024-07-09 17:10

let me see. .maybe it was created after the domain migration

Tech A 2024-07-09 17:48

Tech B 2024-07-09 17:58

yes, my bad. that email was created afterr the email domain migration was there a Slack account at all?

Tech A 2024-07-09 18:10

I saw that she was logged in with the new domain name,but not really sure if there was an account created under that other domain

Tech A 2024-07-09 18:11

Who's the one that manages all that slack accounts?

Tech B 2024-07-09 18:32

we are.

Tech B 2024-07-09 18:32

again, the main thing is to login to the correct workspace

Tech A 2024-07-09 18:34

Yes, but when she tries to log in with the email that's @hqrcms, she should receive a 2fa code. But she's not receiving that code at her @pdsmgmt email address,because there was no @hqrcms email account created before, so there's no redirection of the emails right?

Tech A 2024-07-09 18:36

She only had 1 workspace on that account, it was not the correct one

---
title: "Resolve Slack invitation errors after domain migration"
category: accounts-and-access
tags: ["domain-migration", "email-redirection"]
source_thread_id: "spaces/AAAA05BdS6s/threads/JfOuaePfED4"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T08:36:15"
participants: ["Tech A", "Tech B"]
---

# Resolve Slack invitation errors after domain migration

## Problem

A user received a Slack invitation to join a shared channel but encountered two issues: first, Slack displayed an "upgrade required" message despite having a PRO plan, and second, an error stating "This invitation can only be accepted by omalbany@pdsmgmt.com". The user was attempting to access Slack using their new domain email (@hqrcms.com) but the invitation was sent to the old domain (@pdsmgmt.com). Investigation revealed the user's @hqrcms.com email account was created after the domain migration, so email redirection was not configured, preventing them from receiving the 2FA code needed for Slack login.

## Resolution

1. Verify the user has an email account created in the old domain (@pdsmgmt.com) before the domain migration to ensure email redirection is working
2. If the account was created after migration, set up proper email redirection from the new domain to the old domain
3. Have the user follow the correct Slack login process:
   - Open https://hqrcmsworkspace.slack.com/
   - Enter their email as youremail@HQRCMS.COM
   - Receive the 2FA code at youremail@PDSMGMT.COM (via email redirection)
   - Select the PDS-HQRCM workspace when prompted (identifiable by the largest number of users)
4. If the invitation was sent to the wrong domain, contact the sender (in this case, a colleague from Teem) to resend the invitation to the correct email address

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/JfOuaePfED4`
- Attachments:
  - ![image.png](../attachments/JfOuaePfED4.AmhYM_uKRck/image.png) — This is a Slack web page displaying an invitation acceptance error message. The message states: **"This invitation can only be accepted by omalbany@pdsmgmt.com"** and notes the invitation was sent by **Magdalena Perez** from **Teem**, for the channel **#albany**, involving **Teem and 1 other organization**. A secondary message advises that if sent to the wrong email address, someone from Teem can resend the invitation.
  - ![image.png](../attachments/JfOuaePfED4.JfOuaePfED4/image.png) — The screen displays a Slack web page indicating an invitation from **Magdalena Perez** from **Teem** to work in the **#albany** channel with 1 other organization. A secondary message reads **"Ready to upgrade?"** stating that shared channels require a **Slack paid plan** and prompting the user to upgrade their account to accept the invitation. No error codes, equipment identifiers, or diagnostic indicators are present.

Generated article

draft