Agent skill · marketing growth · jeremylongshore
notion-enterprise-rbac
Map Notion connection capabilities, content access, user context, and application roles into an auditable authorization model. Use when designing multi-workspace or enterprise controls. Trigger with "review Notion RBAC", "map Notion permissions", or "audit Notion tenant access".
Why this skill is useful
Provides specific implementation details for OAuth integration and permission management in Notion that the AI wouldn't reliably generate on its own.
What it needs
Requires @notionhq/client, notion-client installed locally. Requires notion account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion Enterprise Authorization Boundary Review Overview Map Notion connection capabilities, content access, user context, and application roles into an auditable authorization model.. This workflow produces an auditable decision or artifact before any live action. Prerequisites Current first-party Notion documentation and the selected integration's tested API-version contract. A named workspace owner, content or data owner, and operation owner. Synthetic or approved non-production fixtures with secrets and workspace content removed. Current Contract Notion connection capabilities, page sharing, installer authority, personal-token user permissions, application roles, and enterprise admin APIs are distinct control planes. None should be presented as universal Notion RBAC. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication Record internal connection, public OAuth connection, or personal access token explicitly. For public OAuth, bind encrypted tokens and refresh state to the correct workspace and installation. Instructions 1. Inventory actors, workspace and tenant boundaries, connection types, capabilities, shared roots, and application roles. 2. Build an operation matrix for read, insert, update, comments, user information, webhook, and administrative surfaces. 3. Calculate effective access as the intersection of token model, capabilities, content sharing, user authority, and application policy. 4. Design authorization checks at every job, cache, queue, and destination boundary. 5. Add joiner, mover, leaver, reauthorization, revocation, and workspace-removal workflows. 6. Review exceptions, separation of duties, audit evidence, and recertification cadence. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-enterprise-rbac