Governance
Zep applies authorization and audit controls to Context Graph operations. Role-based access control governs dashboard users.
Attribute-based access control governs API keys and UserGroups.
Zep separates two problems:
- Who can manage the account and projects — teammates in the dashboard. Solved with managing team access (role-based access control, RBAC), and, for how those teammates authenticate, enterprise SSO.
- What context each agent and Memory MCP user can reach — agents and other callers. Solved with policy-based access control (attribute-based access control, ABAC), applied to API keys for agent access and to UserGroups for UserGroup access.
Use RBAC for humans. Use policies when you need least-privilege access to context for agents and Memory MCP users. Encryption, compliance certifications, and deployment trust boundaries live under Security & Compliance.
Access and policy
Grant dashboard permissions with account- and project-scoped roles (RBAC).
Make your identity provider the source of truth for member sign-in.
Limit which actions and context each agent and Memory MCP user can reach with ABAC policies attached to API keys and UserGroups.
Visibility
Track dashboard member actions including logins, member management, API key changes, and data operations.
Monitor SDK and API requests, including outcomes from agent access.
Related
- Episode metadata projection — metadata attached at ingestion is what source-based policies evaluate.
- Security & Compliance — SOC 2, HIPAA, BYOK, BYOM, and deployment models.