> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goalgen.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Content library & administration

> Templates, review queue, creators, and Creator Studio settings

## 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](/creator-studio/rbac)).

<Warning>
  Exact screens and permissions depend on your Clerk `studioRole` and app `role`. If a menu item is hidden, your account doesn’t have access yet.
</Warning>

## 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:**

<Steps>
  <Step title="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).
  </Step>

  <Step title="Draft or submit">
    Non-admin submissions often land in **pending** until an admin publishes or requests changes.
  </Step>

  <Step title="Publish">
    Admins can move items to **published** / **draft** / **archived** as your product rules define.
  </Step>
</Steps>

<Tip>
  Thumbnails and metadata (name, description, category) help users discover templates in Vision Studio. Fill them in before requesting review.
</Tip>

## 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](/creator-studio/rbac)                |

## Related

<CardGroup cols={2}>
  <Card title="Creator Studio overview" icon="paintbrush" href="/creator-studio/overview">
    Navigation model and entry points.
  </Card>

  <Card title="RBAC" icon="shield-halved" href="/creator-studio/rbac">
    Roles, permissions, and Clerk metadata.
  </Card>
</CardGroup>