Files
hackerspace.sh/lib/permissions-catalog.ts
T
Moheeb Zara 3a2d3ca13f feat(forms): schema + RLS for custom forms and waivers (Phase 1)
Adds the forms and form_submissions tables behind a custom form/waiver
builder. Phase 1 is schema + RLS only; server actions, builder UI, the
public /f/[slug] page, onboarding integration, and retro-linking follow
in later phases.

- scripts/026_forms.sql (idempotent), mirrored as schema.sql Section 17
- forms: globally-unique slug, kind (form/waiver), visibility
  (public_anon/public_auth/members), status, jsonb field schema,
  legal_text, version
- form_submissions: per-row snapshot of schema/legal-text/version for
  immutable waiver records, plus ip/user_agent for e-sign defensibility
- RLS additive + default-deny: forms write gated by forms.manage via
  user_has_permission; form_submissions has no write policy, so it is
  service-client-only and immutable; anon gets no grant on forms
- new forms.manage permission seeded to board + backfilled
- types/database.ts and DATABASE_SCHEMA/DB_SCHEMA_MAP/ARCHITECTURE/HANDOFF
  updated
2026-05-16 14:38:28 -07:00

53 lines
2.8 KiB
TypeScript

// Fixed catalog of permission codes. This is app-owned data, not a table:
// the set of capabilities is part of the product, while which roles hold
// which permissions is per-space (space_role_permissions).
//
// Important: this layer is ADDITIVE. Existing role-based RLS and server-action
// role checks stay in force. A permission grant can only widen what a role can
// do through the surfaces that consult it (the Ops ACL and the Customize
// permissions UI); it never overrides the database RLS that protects tenant
// isolation. `admin` implicitly holds every permission and can never be
// locked out.
export const PERMISSIONS = [
{ code: 'ops.kb.read', group: 'Ops', label: 'Read knowledge base' },
{ code: 'ops.kb.write', group: 'Ops', label: 'Write knowledge base' },
{ code: 'ops.process.read', group: 'Ops', label: 'Read processes' },
{ code: 'ops.process.write', group: 'Ops', label: 'Write processes' },
{ code: 'ops.secrets.read', group: 'Ops', label: 'Reveal secrets' },
{ code: 'ops.secrets.write', group: 'Ops', label: 'Manage secrets' },
{ code: 'ops.arealeads.manage', group: 'Ops', label: 'Manage area leads' },
{ code: 'members.manage', group: 'People', label: 'Manage members' },
{ code: 'payments.manage', group: 'Finance', label: 'Manage payments' },
{ code: 'governance.manage', group: 'Governance', label: 'Manage proposals, incidents, policies' },
{ code: 'forum.moderate', group: 'Community', label: 'Moderate forum and comments' },
{ code: 'forms.manage', group: 'Community', label: 'Manage forms and waivers' },
{ code: 'customize.manage', group: 'Admin', label: 'Customize roles, tiers, areas, invites, onboarding' },
{ code: 'settings.manage', group: 'Admin', label: 'Space settings, integrations, webhooks' },
] as const
export type PermissionCode = (typeof PERMISSIONS)[number]['code']
export const PERMISSION_CODES: readonly string[] = PERMISSIONS.map(p => p.code)
export const PERMISSION_GROUPS: string[] = Array.from(new Set(PERMISSIONS.map(p => p.group)))
// Built-in role defaults seeded per space. `admin` is intentionally absent:
// it holds everything implicitly and is never stored, so it cannot be
// accidentally revoked.
export const DEFAULT_ROLE_PERMISSIONS: Record<string, PermissionCode[]> = {
board: [
'ops.kb.read', 'ops.kb.write', 'ops.process.read', 'ops.process.write',
'ops.secrets.read', 'ops.secrets.write', 'ops.arealeads.manage',
'members.manage', 'payments.manage', 'governance.manage',
'forum.moderate', 'forms.manage', 'customize.manage', 'settings.manage',
],
treasurer: ['payments.manage', 'ops.kb.read', 'ops.process.read'],
member: ['ops.kb.read', 'ops.process.read'],
associate: ['ops.kb.read'],
}
export function isValidPermission(code: string): code is PermissionCode {
return PERMISSION_CODES.includes(code)
}