Accepting a project invitation used to be fragile for anyone who didn't already have an account — the sign-up flow could lose track of the invitation entirely, leaving collaborators stranded with no clear path forward.
Invitation links now detect whether the recipient already has an account and show the right call to action. New users see Create Account to Accept; returning users see Sign In to Accept. Both paths carry the invitation context through to completion, so accepting happens automatically once you're signed in or your account is created — no second step required.
During sign-up or sign-in, an Invitation Banner appears at the top of the form showing the organization, the location, and the email address the invitation was sent to. If you switch between the sign-in and sign-up pages, the banner and invitation context stay with you. The banner also helps if you're signing in from a different browser or device than the one where you first clicked the link.
If an invitation token has expired, you now see an informative screen with the inviter's contact details instead of a silent redirect to the homepage. This gives you a clear path to ask for a new link rather than wondering why nothing happened.
As a fallback, invitation context is preserved locally in your browser for 24 hours. If the authentication flow drops the redirect at any point — for example, behind a corporate firewall or a browser that strips redirect parameters — you'll be returned to the invitation automatically when you reach the dashboard.
None of this changes the flow for collaborators who are already signed in when they click an invitation link. That path continues to work as before.