Skip to content

Make room for user emails#450

Closed
HazAT wants to merge 1 commit into
mainfrom
user-email-schema
Closed

Make room for user emails#450
HazAT wants to merge 1 commit into
mainfrom
user-email-schema

Conversation

@HazAT

@HazAT HazAT commented Jul 10, 2026

Copy link
Copy Markdown
Member

We only know people by their Slack ID, which means nothing to any other system. First step to fixing that: give users an email field. (1/3 — filling it and exposing it come next.) 🥔

@HazAT
HazAT requested a review from a team as a code owner July 10, 2026 11:10
Add a nullable slack_email column to the users table, plus the
corresponding entity property and email validation rule.

The column is nullable because email is only available from Slack's
users.info API when the app has the users:read.email OAuth scope, and
existing rows need a backfill. Population happens in a follow-up
change to keep the schema migration independently deployable.

slack_email is added to the entity's _hidden list so it does not leak
into the JSON output of existing endpoints that serialize user
entities (leaderboard, user list, profile). Exposing it deliberately
where needed is a follow-up change.
@HazAT
HazAT force-pushed the user-email-schema branch from 70e8407 to 0b94587 Compare July 10, 2026 11:13
@HazAT

HazAT commented Jul 10, 2026

Copy link
Copy Markdown
Member Author

Folded into #452 — one PR for the whole email story.

@HazAT HazAT closed this Jul 10, 2026
@HazAT
HazAT deleted the user-email-schema branch July 10, 2026 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant