Collaboration
Resolve team and workspace context before signup.
Workspace invitation flows break on mobile. A user receives an email invitation with a link; they open it on their phone; they don't have the app yet. They install it from the App Store, but when the app opens, it has no idea they were in the middle of accepting an invitation. The user is dropped into a generic onboarding flow with no team context.
How Forwarded solves it
Route the invitation link through Forwarded. The link carries team_id, invite_id, and role. When the invitee installs and opens the app, the SDK resolves these identifiers immediately. Your onboarding shows 'You've been invited to join Acme Engineering' instead of a generic welcome screen. After account creation, claim the session to bind the invite to the new user.
- 1Generate a Forwarded Link for each invitation. Embed team_id, invite_id, and role in the payload.
- 2Send the Forwarded Link in the invitation email. If the user is on mobile, the Forwarded landing page is shown.
- 3The user installs from App Store or Play. The invite context is captured at session OPEN.
- 4On first launch, the SDK resolves the session. Display the team name and invited role. After signup, claim the session to bind the user to the invite.
- 5Validate the invite_id in your own backend before completing the join. Forwarded carries context — your backend enforces authorization.
Payload schema
This is the JSON you attach to the Forwarded Link. Your app reads it from the resolved session object. Fields shown here are illustrative — use the keys your own backend and mobile SDK expect.
Outcome
New users land in the app with their workspace context already resolved. Onboarding completion rates are higher when the user immediately sees the team they were invited to join.
Next steps
See the invite example
Full worked example in the docs — payload definition, SDK integration, and session claim.
Create a Forwarded Link
Configure your payload, set the landing page, and get a shareable URL in the dashboard.
New to Forwarded? Read the quickstart →