Snap | Rookie Sport Admin

PLATFORM CATALOGUE

Supported sports

Sports available across leagues, clubs, Play and product modules.

ORGANISATIONS

Leagues

League records and their linked clubs, sports and setup status.

ORGANISATIONS

Clubs

Club identity, league links, enabled modules and membership activity.

IDENTITY & ACCESS

Users

A login identity can hold different memberships and roles at every level of Rookie.

Not loaded

PLATFORMRookie AdminSupport

LEAGUEOwnerAdminOfficial

CLUBOwnerAdminCommitteeContent Manager

TEAMManagerCoachAssistant CoachOfficial

RELATIONSHIPSPlayerParentGuardianFollower

Open this section to load Rookie users.

AZURE STORAGE

Rookie data model

How directory records, managed organisations, users and product configuration connect.

9 active stores

How to read this

Azure Table Storage has no enforced foreign keys. Relationships below are application-level links made through PartitionKey, RowKey, and identifier fields.

flowchart LR
  subgraph discovery["DISCOVERY DATA"]
    direction TB
    DL["directoryLeagues
PK geography · RK league id"]
    DC["directoryClubs
PK geography · RK club id"]
    LEG["directoryOrganizations
legacy read-only fallback"]
  end

  subgraph core["LOOKUP & OWNERSHIP"]
    direction TB
    IDX["clubs search index
PK sport:name prefix · RK club id"]
    ORG["organizations
PK organization · RK organisation id"]
  end

  subgraph access["ACCESS & OPERATIONS"]
    direction TB
    PROFILE["userProfiles
PK identity hash · RK profile"]
    MEMBER["organizationMembers
PK identity hash · RK organisation id"]
    INVITE["organizationInvites
PK email hash · RK organisation id"]
    TEAM["clubTeams
PK club id · RK team id"]
  end

  CONFIG[("Blob: published/config.json
sports · milestones · designs")]
  API["Rookie API"]
  APPS(["Web & native products"])

  DC -->|"one row per sport"| IDX
  DL -.->|"candidate / display data"| ORG
  DC -.->|"claim / manage"| ORG
  LEG -.->|"fallback; split rows win"| API
  ORG -->|"organisation id"| MEMBER
  ORG -->|"organisation id"| INVITE
  ORG -->|"club id"| TEAM
  PROFILE -->|"identity hash"| MEMBER
  INVITE -->|"claim creates membership"| MEMBER
  IDX -->|"type-ahead search"| API
  ORG --> API
  MEMBER -->|"permissions"| API
  CONFIG --> API
  API --> APPS

  classDef directory fill:#132c3d,stroke:#527a94,color:#edf7ff,stroke-width:1.5px
  classDef legacy fill:#28252f,stroke:#81778d,color:#c9c2cf,stroke-dasharray:5 4
  classDef primary fill:#183520,stroke:#b9ff38,color:#f4ffe1,stroke-width:2px
  classDef index fill:#2d2040,stroke:#bf77ff,color:#f4eaff,stroke-width:1.5px
  classDef access fill:#142b3b,stroke:#52c7ff,color:#e7f8ff
  classDef config fill:#132f3d,stroke:#52c7ff,color:#e7f8ff
  classDef service fill:#3b2c0f,stroke:#ffd45c,color:#fff6d9,stroke-width:2px
  class DL,DC directory
  class LEG legacy
  class ORG primary
  class IDX index
  class PROFILE,MEMBER,INVITE,TEAM access
  class CONFIG config
  class API,APPS service

Directory tables

Core fields: name, type, country/state, verification status, source hash
recordJson: Sports, source evidence, location, league names and extended metadata
Enrichment: Website, socials, logo, brand colours and research evidence

Managed organisations

Identity: name, slug, type and status
Product links: modules, sports and leagueIds stored as JSON arrays
Branding: logo URL, colours, official URL and researched links

Identity and permissions

Identity hash: SHA-256 of tenant and object IDs; avoids storing raw IDs as partition keys
Membership: Organisation ID, role(s), status and identity metadata
Invitation: Email hash, organisation ID, role and claim status

Compatibility

Legacy directory: directoryOrganizations remains read-only; split tables take precedence by record ID
Rugby: New rows use rugby-league or rugby-union; generic legacy Rugby remains searchable
Joins: All links are resolved in the API because Azure Tables do not perform joins

Designs

Designs

Designs

Canvas

Selected layer

Supported sports

Leagues

Clubs

Users

Rookie data model

Directory tables

Managed organisations

Identity and permissions

Compatibility