notion-policy-guardrails

# Notion Policy & Guardrails ## Overview Governance framework for Notion integrations at scale. Covers integration naming standards for consistent bot identification, page sharing policy enforcement to prevent accidental data exposure, property naming conventions for cross-team database consistency, database schema validation standards, and access audit scripts that scan which integrations have access to which pages. Uses `Client` from `@notionhq/client` for programmatic enforcement. ## Prerequisites - `@notionhq/client` v2.x installed (`npm install @notionhq/client`) - Python: `notion-client` installed (`pip install notion-client`) - `NOTION_TOKEN` environment variable set (admin-level integration recommended for audits) - CI/CD pipeline (GitHub Actions examples provided) ## Instructions ### Step 1: Integration Naming Standards and Token Management Establish naming conventions for integrations so teams can identify which bot accessed what. ```typescript import { Client } from '@notionhq/client'; // Naming convention: {team}-{env}-{purpose} // Examples: eng-prod-sync, marketing-staging-cms, data-prod-etl interface IntegrationConfig { name: string; // Must match: /^[a-z]+-[a-z]+-[a-z]+$/ token: string; environment: 'dev' | 'staging' | 'prod'; owner: string; // Team or individual capabilities: string[]; // What it's allowed to do } function validateIntegrationName(name: string): string[] { const issues: string[] = []; const pattern = ...