Overview
Content administration in Creator Studio covers everything tied to what appears in the library: template lifecycle, moderation, creator records, and operational settings. These areas are intended for admins and approved creators submitting work—not for end-user RBAC (that lives under RBAC).Templates
The Templates area (/creator-studio/admin) is the hub for library items: templates, stickers, frames, and related assets that power the Vision Studio flyout.
Typical workflow:
Author in Vision Studio
Build or refine a design on the canvas, then save to the library flow your app provides (personal vs library scope may affect review status).
Draft or submit
Non-admin submissions often land in pending until an admin publishes or requests changes.
Review queue
Review queue (/creator-studio/admin/review) is where admins approve, reject, or request changes on submissions. Feedback is stored so creators can revise and resubmit.
Use this when you need a controlled quality gate before public library visibility.
Creators
Creators (/creator-studio/admin/creators) lists creator profiles tied to Clerk users—applications, approval state, and related metadata. This is about people in the creator program, not platform-wide user roles (those are under RBAC).
Settings
Settings (/creator-studio/admin/settings) holds Creator Studio–specific configuration (integrations, defaults, or policy toggles your deployment wires up). Keep platform-level security and role management in RBAC unless your team intentionally colocates a setting here.
Content vs platform admin
| Topic | Where to go |
|---|---|
| Library templates, moderation, creator applications | Creator Studio → content sections above |
User roles, Genners, affiliates, publicMetadata | RBAC |
Related
Creator Studio overview
Navigation model and entry points.
RBAC
Roles, permissions, and Clerk metadata.