Keep the workspace organized and accountable.
The dashboard connects projects with reusable assets, POI data, user access, usage, subscription, and developer tools. What you can see and change depends on your account role and enabled services.
Dashboard areas
| Area | Purpose | Typical user |
|---|---|---|
| Audio Creatives | Create, open, rename, duplicate, and manage Studio projects, and open a campaign's Delivery report. | Creators and producers. |
| Playground | Try supported generation or audio capabilities outside a campaign workflow. | Creators and evaluators. |
| Embed Builder | Configure the Embedded SDK experience and generate integration settings. | Product and developer teams. |
| Users | Manage account members where role allows. | Account administrators. |
| POI | Create and maintain geographic entity lists. | Campaign operators. |
| Data | Create and maintain data collections: products, stores, offers, and other lists your ads read from. | Campaign operators; account admins make changes. |
| Usage | Review consumption and activity. | Creators and administrators. |
| Subscription | Review plan, entitlement, and billing controls. | Billing/account administrators. |
| API Keys | Manage credentials for approved developer integrations. | Authorized administrators/developers. |
Organize projects
- Name projects by campaign, market, or flight.
- Name creatives by treatment or decision role.
- Duplicate before a high-risk structural experiment.
- Delete only after confirming that no active release or integration depends on the project. Studio asks you to confirm in a dialog; a deleted project cannot be restored.
- Avoid concurrent edits to the same project in multiple tabs.
Reusable asset views
Voice, Music, and SFX selectors expose library content, Favorites, and account-owned assets. Use Favorites as a shortlist; use My Voices, My Music, and My SFX for assets that belong to the account workflow.
- Give uploaded or generated assets a recognizable name.
- Retain licence and consent evidence outside the display name.
- Remove obsolete favorites to keep selectors useful.
- Before deleting an owned asset, check projects and releases that reference it.
Users and roles
Roles should follow least privilege. A creator needs project capabilities; an account administrator manages people and account settings; platform-level administration is a separate operational responsibility.
Usage and credits
Credits are consumed by eligible generation and processing operations, not by every edit. Review the cost confirmation shown by Studio and use Usage to reconcile campaign activity: it shows Granted Credits, Used Credits, and Remaining Credits for the current billing period, with usage By Action and By User and a Download CSV button.
| Usually consumes credits | Usually does not consume generation credits |
|---|---|
| Speech synthesis, Rephrase, supported AI generation, and audio import/processing. | Text edits, project autosave, asset browsing, timeline moves, configuration, and ordinary playback of existing audio. |
Pricing and entitlement can change by plan or provider. Treat the confirmation shown for the current account as the authoritative estimate before starting an operation.
Account menu
Click your avatar or name to open the account menu: My profile for your name and password, Workspace settings for the workspace name and country where your role allows it, Help & user guide, and Log out.
Subscription and entitlements
The plan controls available services, limits, and commercial terms. If a capability such as voice cloning, AI music, publishing, or administration is absent, check Subscription and account role before treating it as an application error.
API keys and developer guides
API keys are sensitive account credentials. Create and store them only in authorized server-side systems; never place a long-lived secret in browser code.
Embedded SDK →
Place the creative experience inside another product using short-lived user tokens.
REST API →
Generate and operate from a server-to-server integration.
Platform administration
Platform administrators may see additional areas such as Accounts, Subscriptions, provider catalogs, or Data Feeds. These controls affect multiple accounts or the platform catalog and are intentionally outside the normal Studio creation path.
Monthly operational review
- Archive or identify inactive projects.
- Review users, roles, and departed team members.
- Reconcile Usage with campaign activity.
- Review subscription and provider terms.
- Rotate exposed or obsolete API keys.
- Confirm that active Delivery releases still have a current owner.