Repository navigation
Description
Design for the second half of the operator's ask: Customers on a spoke showing context the hub already holds about the same people. Companion to #19085 (spoke-local country, likely affiliation, notes). Design decision from the consistency deck: hub data in Customers is opt-in, consent first, and off by default. No code is proposed yet because two consent questions below are the operator's to decide.
What exists today (verified in the repo)
- The hub keeps a per-user record (
SaaSUser,pkg/hub/saas.go):full_name,slack_id,notesandcompany(operator-entered CRM text; notes are admin-only, withheld even from hive owners),countrywith a source ofinferred(from the browser language at login),adminoruser(the person chose it),affiliationwithaffiliation_source(cached from public GitHub footprint), providerdisplay_name,email,linked_github_login. - Per-hive access rows already carry
full_nameandslack_idto a hive owner, andnotesonly to a hub admin (saas_access.go). - The hub has no per-person consent state. Nothing records that a person agreed to their fields being shared with a hive.
- A spoke talks to the hub by heartbeat (
POST /api/heartbeat, per-hive bearer); the hub can piggyback data on the reply. There is no endpoint where a spoke asks the hub about a person, and none returning these fields to a spoke. - On the spoke, Customers profile fields carry provenance
autoormanual; "Nothing is read from the hub" is stated in the design doc and ✨ Customers: real name, organization and location on a profile #18973.
Proposed model
Per-field provenance value hub (a third value beside auto and manual), shown as "from the hub", never overwriting a manual field, overwritten by nothing but a person or the next sanctioned import.
Fields by sensitivity
- Country, organization, real name: low risk when the person set them. Importable only where hub provenance is
user(the person entered it).inferredandadminvalues are not imported by default: an inferred country is a guess about a browser, and an admin attribution is a claim by someone else. - Hub
notes: admin-private CRM text that can name other people. Never imported. Not an option. - Email, Slack id: identifiers, not profile context. Not imported in v1.
Who consents (operator decision 1). Options: (a) the person, per hive, through a hub page "share my name, organization and country with hive X"; (b) the hub operator, by policy, for hives the hub itself hosts; (c) the spoke owner, by turning the switch on (which only says the spoke wants it; the hub still decides what to send). Recommendation: (a) is the only option that is consent in the ordinary sense. (b) is defensible only for hives the same operator runs, and must be disclosed in the privacy text. The spoke owner's switch is always required and never sufficient.
What crosses the wire. A signed, per-hive pull: the spoke posts the hash of each confirmed Customers identity it holds (GitHub login or confirmed email, salted per hive) and the hub answers only for persons who consented to that hive, with {match_hash, real_name, organization, country}, each field present only if hub provenance is user. No plaintext identifiers from the spoke, no notes, no unconsented person (the hub cannot tell a spoke whether someone exists on the hub: unconsented and unknown look the same).
Transport and auth. Reuse the existing per-hive bearer and the heartbeat channel (or a sibling endpoint under the same auth). Rate-limited and cached on the hub; off in the spoke unless customers.hub_import.enabled (default off, env override) AND the hive is registered with a hub.
Revocation. Person: withdraw on the hub; the hub stops answering for them, and the next sanctioned import clears spoke fields with provenance hub for that person (a tombstone reply, not silence). Forget on the spoke already deletes the person; a hash tombstone prevents re-import. Forget on the hub (account deletion) is a withdrawal for every hive.
Default. Off, everywhere, until the operator decides 1 and 2 below.
Decisions the operator must make
- Who consents: the person, per hive (recommended), the hub operator for hosted hives only, or the spoke owner alone (not recommended).
- Is it acceptable to ship consent as a new hub page and stored per-person per-hive record before any spoke code? Without it there is nothing to consent to.
- Do
admin-sourced values (an operator typed the organization for someone) ever cross, with the person's consent, or onlyuser-sourced ones? - Should email-derived affiliation on the spoke (✨ Customers: country flag, likely affiliation suggestion and notes rules on a profile (spoke-local) #19085) stay spoke-local forever, or be reconciled with the hub's cached affiliation once a consent record exists?
Out of scope here
Any implementation. A PR is not opened because decisions 1 and 2 change the hub's data model and privacy text.
Activity
hivecommons-hive commentedon Nov 18, 2026
🔓 Claim by @Danathar released (lease revoked).
Claim history
Danathar(contributor on hive hosted-available-oke-11-placeholder-r05x)Danathar(contributor; lease revoked)hivecommons-hive commentedon Nov 18, 2026
What to reply
/hive approve: go with the recommendation/hive decision <your instructions>: go ahead, following your instructions/hive help: show these againIf what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply
/fixedto close it as completed; Hive clears its park labels.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
clubanderson commentedon Nov 18, 2026
Decision needed: one real choice. The other three follow from it or can wait.
Verified against
v5: the hub storescountry_sourceandaffiliation_sourceper user but has no per-person consent record, and no endpoint returns person fields to a spoke. #19085 / #19087 (spoke-local country, affiliation, notes) are merged, so nothing here blocks current Customers work. Default stays off.The one question: who consents to hub-held name, organization and country reaching a hive?
Follow-ons, with defaults that apply unless you say otherwise
admin-entered hub values: never cross in v1; only values the person entered themselves (userprovenance). An operator's attribution of someone else is not the person's statement.Reply
/hive decision 1(or2) to accept that option with the defaults above, or name any default you want changed.clubanderson commentedon Nov 18, 2026
Decision (owner): option 1. The person consents, per hive, on a hub page; the hub consent page and consent record come first; only values the person entered themselves cross to a hive, never admin-entered ones; email affiliation stays spoke-local in v1. Default off until the person opts in.
clubanderson commentedon Nov 18, 2026
/hive decision 1. The person consents, per hive, on a hub page. Build the hub consent page and the per-person, per-hive consent record first, before any spoke code. Only values the person entered themselves (user provenance) cross to a hive, never admin-entered ones. Email affiliation stays spoke-local in v1. Default off until the person opts in. Any setting this needs gets a home in the dashboard Settings UI.
(Same decision as the owner comment above, restated in the form the un-park sweep parses.)
14 remaining items
✨ Customers: import hub-consented fields with hub provenance (#19247)
feat: hub import disclosure, docs and consent views (phase 4 of #19088)
feat: hub import disclosure, docs and consent views (phase 4 of #19088)
clubanderson commentedon Nov 19, 2026
Decision change (2026-11-19, operator): part of the consent-first rule is relaxed for hub-held person fields.
Import switches stay off. Implementation is tracked in a new issue, linked below.
clubanderson commentedon Nov 19, 2026
Implementation of the decision change above: #19306.
feat: hub import disclosure, docs and consent views (phase 4 of #19088)
feat: hub import disclosure, docs and consent views (phase 4 of #19088)
feat: hub import disclosure, docs and consent views (phase 4 of #19088)
✨ Customers: pass hub country and organization labeled, without per-p…
✨ customers: hub import disclosure, docs and consent views (#19253)