SolvedAccount & Workspace

Invitation link says invalid or expired

Asked by Claire DuboisJun 25, 2026
I invited a new engineer two weeks ago. He finally clicked the link today and gets a message saying the invitation is invalid or expired. I can still see the invitation in our pending list so I assumed it was fine.
Accepted answer from MonoDuty Support
Burak ŞahinMonoDuty Support EngineerJun 27, 2026
Yes, and there is one step you should do first: 1. Cancel the existing invitation for that email address. If you skip this you may hit a message saying a pending invitation already exists. 2. Create a new invitation for the same address with the role you want, either admin or member. 3. Ask your colleague to accept within seven days. Two details that trip people up when accepting: The person accepting must be signed in with the exact email address the invitation was sent to. If he created his account with a different address, for example a personal one instead of the work one, the acceptance is rejected. In that case invite the address he actually signed up with. And he needs an account before he can accept, so if he has never signed up he should register first and then open the link. One last thing worth knowing: if his email domain matches the domain of your organization's owners or admins, he can also request to join directly from the discovery view, and you approve the request instead. For teams on a company domain that is often smoother than chasing invitation links.
Was this helpful?42 of 44 found this helpful

3 replies

Burak ŞahinMonoDuty Support EngineerJun 25, 2026

Hi Claire, invitations are valid for seven days from when they are created, so a two week old link has expired. The reason it still appears in your pending list is that expiry does not change the status, it only makes the token unusable. So a pending invitation and a usable invitation are not quite the same thing.

Claire DuboisJun 26, 2026

Ah, that is confusing. What do I do now, just send it again?

Claire DuboisJun 27, 2026

The join request route worked immediately since we are all on the same domain. Much easier.