🔐Security
Last updated
Trust is at the heart of what we do.
Origin Studio's Security module enables granular, role-based access control. Use it to separate catalogs, protect sensitive fields, and control actions.
First time setting this up? → Concepts & Examples Ready to configure? → Getting Started Guide Already set up? → Managing Access Need to verify access? → Auditing & FAQ
Tenant: your isolated Origin Studio environment. Permission Group: a logically separated library inside your tenant. Role: a named set of permissions (policies). User: a person who logs in and is assigned roles.
Full mental model here.
A Permission Group is like a distinct catalog. It controls Record visibility end-to-end:
Records are excluded from search for unauthorized users.
Records are excluded from filters and API responses.
Use it to segregate departments or business units.
A Role bundles system permissions into a reusable package. One role can contain multiple policies for flexibility.
Example patterns:
TV Content Contributor: create Series/Season/Episode drafts only.
TV Content Reviewer: edit records and approve publication.
Users can authenticate with email/password or SSO. See Setting Up Single Sign-On (SSO).
UI access can be restricted by Data Group and Section. See Fields and Record Layout Management.
Last updated