getsentry / getsentry/sentry

Registration form in organization invite flow should pre-fill email address

Open
#121,594 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Good First Issue Improvement Product Area: Sign In Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

When a user receives an organization invitation and clicks "Accept your invite"
in the email, they are directed to the "Accept organization invite" page.
Instead of immediately showing a registration form with the invitation email
pre-filled, the page displays multiple confusing options.

Impact:

  • Higher abandonment rates during user onboarding
  • User confusion about which action to take next
  • Unnecessary complexity for a core workflow

Screenshots:
Image
Image

Solution Brainstorm
Current Behavior
  1. User receives email: "Join [Organization] in using Sentry"
  2. User clicks "Accept your invite"
  3. → Redirected to "Accept organization invite" page
  4. → Page shows multiple confusing options (rather than a clear registration form)
Expected Behavior
  1. User clicks "Accept your invite" in the email
  2. → Directly shown a registration form with:
    • Email field pre-filled (read-only or disabled) with the invitation email
    • Password field
    • Optional: Name field
  3. → After registration: User automatically logged in and added to the organization
Additional Context
  • This workflow affects every user invited via member.invite
  • This is a fundamental onboarding path, not an edge case
  • The current experience contradicts the intent of the invitation (join this org)
Device/Environment
  • Platform: [Chrome/Edge/Firefox/Safari on Windows/MacOS]
  • Sentry version: [latest/self-hosted-sentry]
  • Steps to reproduce: Invite a new user to your organization via "Add Team Member" → Send invite → Click link as new user
Product Area

Profiling

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the member.invite flow and the Accept organization invite page, then reproduce the email-link path using the listed browser steps. Done means a newly invited user sees a registration form with the invitation email pre-filled, can complete registration, and is automatically logged in and added to the organization.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, authorization, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.