Skip to content

Orgs own communities; drop hub curation (orgs phase 2) - #3699

Merged
3mcd merged 1 commit into
mainfrom
orgs-phase-2
Oct 22, 2026
Merged

3mcd merged 1 commit into
mainfrom
orgs-phase-2

Conversation

@3mcd

@3mcd 3mcd commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

An org now owns communities through Communities.orgId instead of curating them through HubCommunities, so its dashboard and analytics cover every owned community with no data access requests.

  • Deletes the existing orgs (the old hubs, none of which has a KF Account) and deactivates their templates, then makes Orgs.kfOrgId NOT NULL. Staff set the KF Account when creating an org in the superadmin dashboard.
  • OrgMembers get a level (view | edit | manage | admin). Any member sees the org pages and dashboard. Admins manage members, communities, featured pubs, templates and settings, and an org keeps at least one admin. /api/orgs/:id/managers becomes /api/orgs/:id/members.
  • Only superadmins add a community to an org for now; org admins can release one. A community created through an org belongs to it.
  • Featured pubs (and suggested pubs) come only from owned communities.
  • Drops HubCommunities, HubOptOuts and OrgFeaturedPubs.dataAccess, with the curated-by dashboard and its curating-orgs/org-opt-out endpoints. The community-side Organization panel replaces them in phase 4.
  • Fixes the org spam filter, which compared against 'confirmed' instead of 'confirmed-spam' and so never excluded spam communities.

An org now owns communities through Communities.orgId instead of curating
them through HubCommunities, so its dashboard and analytics cover every
owned community with no data access requests.

- Deletes the existing orgs (the old hubs, none of which has a KF Account)
  and deactivates their templates, then makes Orgs.kfOrgId NOT NULL. Staff
  set the KF Account when creating an org in the superadmin dashboard.
- OrgMembers get a level (view | edit | manage | admin). Any member sees the
  org pages and dashboard. Admins manage members, communities, featured
  pubs, templates and settings, and an org keeps at least one admin.
  /api/orgs/:id/managers becomes /api/orgs/:id/members.
- Only superadmins add a community to an org for now; org admins can
  release one. A community created through an org belongs to it.
- Featured pubs (and suggested pubs) come only from owned communities.
- Drops HubCommunities, HubOptOuts and OrgFeaturedPubs.dataAccess, with the
  curated-by dashboard and its curating-orgs/org-opt-out endpoints. The
  community-side Organization panel replaces them in phase 4.
- Fixes the org spam filter, which compared against 'confirmed' instead of
  'confirmed-spam' and so never excluded spam communities.
@3mcd
3mcd merged commit 768c69c into main Oct 22, 2026
1 check passed
@3mcd
3mcd deleted the orgs-phase-2 branch October 22, 2026 19:14
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