Compliance & Audits

• Compliance & Audits

  Compliance & Audits This article explains what to log and retain for compliance, how to design audit trails for admin actions, and practical steps to prepare for audits (internal or external). Goals Provide tamper-evident records of administrative and sensitive actions. Establish retention and deletion policies that meet business / regulatory needs. Make it easy to answer audit requests (who did what, when, and from where). What to log At a minimum, maintain structured lFew readers

Auth & Tokens

• Auth & Tokens

  Authentication & Tokens This article documents authentication patterns used by CJH, token types, and operational best practices for issuing, storing and rotating tokens. Authentication model (overview) CJH requires authentication for API calls; user sessions are validated server-side before access is granted. Many client components call a server-side auth library (the repo uses Supabase client calls in components). Example client call pattern: supabase.auth.getUser(). :contentRefereFew readers

Admin Tools

• Admin Tools

  Admin Tools This article explains the administrative screens and controls CJH provides (or should provide), best practices for tenant administration, and operational guidance for managing integrations. Common admin functions Tenant configuration & Integrations — Per-tenant settings for Mapbox, push providers, payment connectors, and feature flags. The Jobs Map doc shows per-tenant Mapbox configuration under Settings → Integrations. :contentReference oaicite:6 index=6 UserFew readers

RLS & Data Scoping

• RLS & Data Scoping

  RLS & Data Scoping This article explains Row Level Security (RLS) concepts and recommended patterns for ensuring data is always scoped to a tenant/organization. Why RLS RLS enforces data access at the database level so that even if an application bug exists, the DB prevents cross-tenant data leakage. Jobs Map notes that RLS policies enforce data access control and are central to tenant scoping. :contentReference oaicite:11 index=11 Core recommendation Every multi-tenant taFew readers

Access & Roles

• Access & Roles

  Access & Roles This article defines a recommended role model for CJH, practical onboarding/offboarding steps, and operational controls to maintain least privilege. Recommended role model Adopt a small, well-defined set of roles with clear responsibilities. Example roles: Owner / Tenant Admin: Full access to tenant configuration, integrations, billing, user/role management. Dispatcher / Manager: Create/assign jobs, schedule, modify jobs and clients, view reports. AccFew readers