Getting Started

This page explains the first-time path for agency users: signing in, understanding the shell, choosing the right workspace, and starting useful work without touching system administration screens.

Sign In

  1. Open the Studio login page at /auth/login.
  2. Enter your email and password.
  3. After login, Agency Admins and Agency Members land in Studio or can use the top navigation to open /studio.
  4. If you see an unauthorized screen, confirm you are using the correct account and that you have been added to the agency workspace.
Scope note: The System Admin route is intentionally not part of this guide. Agency users should not need provider operations, training controls, user-credit override panels, or deployment health tools to make campaigns.

Understand The Product Shell

The top product shell stays visible on authenticated Studio pages. It shows:

Studio Sidebar

The Studio sidebar is the main user navigation inside /studio:

ItemUse it forWho sees it
CampaignsList, create, open, delete, and manage campaign workstreams.Agency Admins and Agency Members.
Brand KitsCreate, edit, preview, and assign reusable brand systems.Agency Admins and Agency Members.
ProjectsOpen project workspaces directly, search/filter projects, and create project work.Agency Admins and Agency Members.
MediaBrowse Studio media and reusable assets.Agency Admins and Agency Members.
Design ReviewReview creative/design outputs in the design-review lab.Agency Admins and Agency Members.
SettingsStudio configuration and status notes.Agency Admins.

Recommended First Campaign

  1. Open Campaigns.
  2. Create a brand kit first if you have brand rules, colors, logo, voice, or photo direction.
  3. Create a campaign and attach the brand kit.
  4. Upload source material: logo, lifestyle/product imagery, any video clips, and any known audio/voice assets.
  5. Open Creative Director and enter a plain-language campaign goal.
  6. Apply the plan, open the generated projects, and review or regenerate each surface.

What A Blocked Job Means

Studio prefers truthful blockers over fake success. If a job is blocked, the UI is telling you a requirement was not met. Common examples:

Safe Working Habits