Skip to content
Interface language: English
Design / Signal

The invitation has arrived. Why am I signed in to the wrong account?

The invited email and signed-in account do not always match. Design identity selection, expired links and a clear status for the inviter.

Article language: English

In a garden at night, a woman examines an illuminated white petal beside a sleeping cat.
In this article

“You can't accept this invitation.” That is a chilly welcome for someone we have just invited, especially when the message reached the right address, the button looked inviting, and nobody explains that the browser remembers another account. The recipient tries again. The inviter sends another message. Soon they have two links and the same problem.

An invitation offers specific access: to a person, into an organization, in a particular role. It is neither ordinary registration nor a link to the home page. The design needs to preserve those connections from the message through to a recognizable outcome. That includes a recipient who is already signed in, but not in the way the invitation expects.

Imagine Obrys, a studio with a collaboration portal for subcontractors. Its administrator invites Tomasz to a catalogue project using his work email. Tomasz has a personal account open in the same portal. We cannot assume the two accounts can be merged automatically. First, he needs to see which account is active and how to return to the invitation after changing it.

The message invites someone into a specific relationship

Before clicking, Tomasz should be able to recognize the sender, the organization and the purpose. “Join us” is too vague when he works with several studios. The message could say that Obrys is inviting him to collaborate on a catalogue and that accepting will open the specified workspace. How much detail it reveals should fit the project and its access rules.

Describe the role through capabilities that matter to the recipient. “Collaborator” may mean viewing materials or editing them. If the invitation allows Tomasz to add photographs but not approve publication, say so before he decides. There is no need to paste the whole technical permissions list. Explain the work he is being invited to do.

The distinction between a user, buyer and payer (in Polish) matters here too. The person accepting an invitation is not necessarily the person ordering or paying for the service. The screen should not suggest buying a plan just because the organization has no available seat or the inviter chose the wrong role. The administrator may need to resolve that problem.

Also prepare for someone saying, “I don't recognize this organization.” The recipient should be able to decline or find a contact who can explain. Do not make them accept first just to find out whom to ask. The sender and purpose need to be recognizable before that step.

Signing in does not determine who should get access

The first screen after opening the link should recognize Tomasz's situation. If he is signed out, it should guide him to an appropriate sign-in method. If he is signed in, it should show the account that will accept the invitation. Greeting him simply as “Tomasz” settles nothing when both accounts have the same name and photo.

GitHub describes a specific rule for organization invitations: when someone is invited by email, the address must match a verified email address on their personal account. The instructions do not apply to Enterprise Managed Users accounts.

Our portal may use a different model. A designer needs to understand it before writing “The addresses don't match.” Does the system check the account's primary address, an additional verified address, or an identity from a particular sign-in provider? Similar-looking emails do not by themselves establish an account-linking rule. The message should reflect the mechanism that actually exists.

When the wrong account is active, show Tomasz the current identity and a clear action: “Switch accounts to accept the invitation.” If displaying the full invited address is permitted only after an additional check, provide the appropriate variation. Agree the amount of information displayed with the person responsible for invitation access.

Switching accounts should not lose the purpose of the visit. After signing in, Tomasz should return to the same collaboration offer, not an empty dashboard that asks him to find the message again. This resembles returning after a session expires (in Polish), but what needs to be preserved here is the invitation and its current status. We are not simply copying an arbitrary earlier form.

Microsoft Entra B2B documentation describes choosing an account when a sign-in name matches both an organizational Entra account and a personal Microsoft account. It also shows that redemption depends on the identity providers configured.

This is a useful distinction to discuss with the implementation team. A “Sign in with...” button does not necessarily explain which profile at the provider Tomasz is using. Passkey sign-in design (in Polish) also separates the sign-in method from the account it opens. The invitation should preserve that distinction after identity is successfully confirmed.

Tomasz may have unsaved work in his personal account along the way. Do not surprise him by signing him out of every tab. Define the scope of the change and provide the necessary information before he leaves his work. If the portal permits choosing another account only in a separate flow, explain that route specifically. The instructions must not sound like advice to erase the entire browser history because of one invitation.

Choosing an account can take time. Meanwhile, the administrator may withdraw the invitation or change the proposed role. Before final acceptance, the screen should retrieve the current terms. If Tomasz was shown editing rights but will now receive view-only access, silently changing a small label is not enough. Show the new scope and let him decide on that basis. A screen seen before sign-in does not prove the offer is still current.

Tomasz opens the message after a holiday. Instead of an accept button, he sees that the invitation has expired. The message should distinguish expiry from lack of access on the current account and from an offer withdrawn by the administrator. These states call for different next steps. A generic “Error” does not tell him whether to switch accounts or request a new invitation.

Aeneia conceptual photography

In GitHub's standard instructions, a pending invitation expires after seven days. An organization owner can resend or cancel an expired invitation. That is a rule for this product, not a recommended deadline for every portal.

For Obrys, validity depends on agreed rules. Show a specific expiry time in the message, with a clear time reference. Once it expires, offer an available route: request a new invitation or contact someone who can send one. A “Resend” button is honest only if the recipient can actually start that action.

A request to resend is not a new invitation. Tomasz should be able to distinguish receipt of his request from confirmation that a message was sent. The administrator may need to check the address or scope of collaboration. If a new invitation already exists, the screen should help him find the current route instead of encouraging duplicates.

Plan for opening the old link after a resend too. Was the previous offer replaced, or is it still valid? The invitation mechanism determines the answer, but the outcome needs its own message. In our example a withdrawn link does not grant access. Tomasz is told to use the current message, without being told to create a new account.

If the portal offers a decline option, define its effect too. Tomasz may not want to join this catalogue while still working with Obrys on another. “Decline the catalogue invitation” should not mean leaving the entire organization. After confirmation, show what the decision covered. The administrator needs to distinguish a deliberate refusal from an invitation nobody has answered yet.

A link that has already been used successfully is different again. If Tomasz returns with the correct account, it can point him to the existing collaboration and the project. There is no need to perform acceptance a second time. If he uses another account, the fact that an authorized person accepted earlier should not open the project to that new profile.

The administrator needs a real outcome too

Sending a message does not mean Tomasz has joined. The invitation list should distinguish waiting, confirmed acceptance and a state that needs action. Do not replace these with a single green “Done” status. Name the event that was actually confirmed: the invitation was created, a message was handed off for sending, or the person joined the organization.

The confirmation should identify the person, organization and agreed role. If Tomasz's account uses a different name from the address used for the invitation, present the result so the connection is recognizable without detective work. But do not add “read” if the system can confirm only acceptance.

When correcting a typo in the address, do not pretend nothing changed. The administrator needs to know whether she is editing the existing invitation, withdrawing it and creating another, or merely correcting contact details for an existing person. These actions affect sent links differently. A plain “Edit” label should not conceal a change of access recipient.

The invitation list also needs a recognizable date and scope for the last action. After a message is resent, show the outcome of that attempt alongside the earlier invitation-creation record. If sending fails, the saved record may still exist. The team needs to know whether it is correcting an address, retrying communication or creating an access offer from the beginning. Check the difference in the recipient's view after the next message.

When Tomasz already has access, another invitation attempt should reveal that. The real need may be a role change, access to another project, or simply a link to the existing workspace. These are three different decisions from creating membership. Recognizing the existing relationship prevents duplicate accounts and pending offers for the same work.

Slack explains that the same email can be used in multiple workspaces while their accounts remain separate. A similar address alone therefore does not settle whether there is one shared product account.

The same practical need appears when switching organizations in a portal (in Polish): the user must recognize where they have entered. After acceptance, show the name Obrys and the catalogue project. Do not stop at a generic “Success” that leaves Tomasz unsure where to work.

The first task is a better ending than confetti

An acceptance confirmation can lead to the specified material or explain what Tomasz is still waiting for. If the administrator must separately share the project, organization membership should not pretend that the catalogue is ready to edit. An empty page saying “Create your first project” would be particularly misplaced: we invited someone into work that another team has already started.

During first use of a tool (in Polish), the person's task matters more than a mandatory interface tour. Tomasz may need to open photographs and add one comment. Preserve that concrete goal through sign-in, account switching and confirmation of access. A long introduction cannot repair a lost connection to the project.

For acceptance testing, use two accounts with clearly different addresses and an invitation to a prepared organization. Start with the wrong account, switch it and check the result from the administrator's side as well. Separately open a withdrawn, an expired and an already accepted invitation. Each attempt should end with a recognizable state, without creating another account just in case.

Aeneia Design can develop the screens, messages and transitions needed for this kind of collaboration invitation. The invitation has achieved its purpose when Tomasz finds the right catalogue under the right account and the administrator sees confirmed access. Then “Good to see you” will no longer require account recovery instructions.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear