Skip to content

Org Auto-Creation on RSI Profile Link + "Claim Org" Flow #117

@ntatschner

Description

@ntatschner

Problem

Users link their RSI profile and arrive at a StarStats account with no associated org record, even though their RSI profile names a primary public org. There's no concept of "this org exists in StarStats" until someone manually creates it, and no clean path for legitimate org Founders/Board members to take ownership.

Approach

On first RSI profile link, auto-create a shell org record for the user's primary public org if one doesn't yet exist. The shell row is unclaimed — visible but with no admin.

Separate "Claim Org" flow for legitimate Founders / Board members: verify via the standard RSI-description verification-code mechanism (a unique code the claimant temporarily places in their org's RSI description), then grant org-admin to the verifier.

Acceptance criteria

  • First RSI profile link creates a shell org row if absent (idempotent on subsequent links)
  • Shell rows are visible (slug, name, member roster) but expose no admin actions
  • Claim flow generates a unique time-bounded verification code (e.g. 24h)
  • Verification reads the live RSI org description, matches the code, then grants admin
  • Audit-log entry on shell creation + on successful claim
  • Re-claiming an already-claimed org requires an existing admin to delegate (not just verification)

Risks / Open questions

  • Race when two legitimate Founders attempt to claim simultaneously — first valid verification wins; second sees a friendly error
  • Verification code in RSI description is publicly visible during the verification window — short TTL helps
  • Org primary-vs-secondary affiliation: which counts as "primary" for auto-creation if a user is in multiple?
  • Org rename on RSI side: should the shell follow renames, or stay at the original slug?
Original draft notes

When a user first links an RSI profile, auto-create a shell org record for their primary public org if one doesn't exist. Claim flow for legitimate Founders / Board members: verify via the standard RSI-description verification-code mechanism, then grant org-admin to the verifier.


Tracking

Metadata

Metadata

Assignees

No one assigned

    Labels

    channel/alphaTargets the alpha release channel (early testing)channel/betaTargets the beta release channel (pre-release, opted-in users)channel/liveTargets the live release channel (stable, end-user-facing)channel/rcTargets the rc (release candidate) channel — final stabilization before livesurface/tray-whats-newsurface/web-roadmap

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions