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

# Levels & sources

> Where context lives across workspace, brand, and product, and where it comes from.

Context is organized in three levels, and it arrives from three sources. Understanding both answers the question new users ask most: **what do I set up, and where?**

## The three levels of context

Superscale is structured as **workspace → brand → product**, and context can live at any of the three. Each level cascades down. A product inherits its brand's context, and every brand inherits the workspace's.

<CardGroup cols={3}>
  <Card title="Workspace-level">
    Applies to **everything in your account, across every brand**. It's where shared standards live: an agency's house rules, team-wide naming conventions, or approval rules you reuse everywhere.
  </Card>

  <Card title="Brand-level">
    Applies to **one brand and all of its products**. The natural home for identity, colors, guidelines, voice, languages, competitors, and connected ad accounts.
  </Card>

  <Card title="Product-level">
    Applies to **a single offer**. Refines creative for one app, SKU, category, service, landing page, or campaign family.
  </Card>
</CardGroup>

### How the levels combine

When Superscale creates for a product, it reads all three layers together: product context on top of brand context on top of workspace context. You set shared things once at the top and only get specific where it matters. A context file can also be assigned to multiple brands or products when the same source applies in more than one place.

<Frame>
  <img src="https://mintcdn.com/superscale/8-S0dvUwZ0WpjGgh/images/context-levels.svg?fit=max&auto=format&n=8-S0dvUwZ0WpjGgh&q=85&s=79817bc69c619540752a1289699a2a32" alt="Nested workspace, brand, and product levels. Superscale combines all three when creating for a product." width="660" height="300" data-path="images/context-levels.svg" />
</Frame>

<Note>
  **Rule of thumb:** put each piece of context at the **lowest level it's true for**.

  * True for your whole workspace? → **workspace**
  * True for one brand? → **brand**
  * True for one offer or campaign family? → **product**
</Note>

## Where common things belong

| What you have                                                     | Put it here                                                | Why                                                              |
| ----------------------------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------- |
| Agency-wide QA rules, legal review rules, naming conventions      | Workspace                                                  | Every brand should inherit them.                                 |
| Brand voice, colors, logo rules, claim restrictions               | Brand                                                      | They apply to every product under the brand.                     |
| Customer personas or ICPs for one brand                           | Brand                                                      | They shape all creative for that brand.                          |
| A specific app, SKU, bundle, service, collection, or landing page | Product                                                    | The agent needs exact product facts and images.                  |
| One campaign brief or temporary promotion                         | Task/chat, or a product context file if it repeats         | It should not permanently change the brand unless it is durable. |
| Winning ads, product shots, logo files, screenshots               | Asset library/reference images, scoped to brand or product | Visual requirements need visual references.                      |
| Compliance or platform restrictions                               | Brand, or workspace if every client follows them           | The agent needs durable guardrails before it writes claims.      |

<Tip>
  Most brands keep almost everything at the **brand level**. Reach for workspace-level when you run multiple brands, and product-level when one offer needs different facts, images, claims, or audiences.
</Tip>

## The three sources

Wherever context lives, it gets there one of three ways.

<Steps>
  <Step title="You provide it">
    Enter or upload it directly: brand guidelines, audiences, reference images, and [context files](/context/managing), like positioning docs, customer quotes, legal rules, CSVs, or campaign briefs.
  </Step>

  <Step title="Superscale pulls it in">
    Add a product from a source and Superscale imports it for you:

    | Source                  | What comes in                                            |
    | ----------------------- | -------------------------------------------------------- |
    | App Store / Google Play | Listing details and reviews                              |
    | Shopify                 | Catalog, products, variants, collections, and imagery    |
    | Amazon                  | Product or store-page details and imagery                |
    | Website                 | Brand and product details from pages Superscale can read |
    | Manual                  | Anything you type, paste, or upload yourself             |

    Connect your brand's [Shopify](/integrations/shopify), provide a supported URL, or enter the details manually. Review imported context before using it in production creative.
  </Step>

  <Step title="The agent researches it">
    Superscale can find competitors and advertiser pages for you to confirm, scan public conversation like Reddit when research is requested, and learn from campaign performance when your ad accounts are connected.
  </Step>
</Steps>

## The common mistake

New users often upload everything into one place and expect the agent to sort it out. Superscale can read a lot, but the scope still matters. If a rule applies forever, make it context. If it only applies to the next ad, put it in the task prompt. If the requirement is visual, attach a visual reference.

<Card title="Set up your brand" href="/context/brand" horizontal>
  The brand level is where most of your context lives. Start there.
</Card>
