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

# Settings

> The Settings area: portal language, user management, attribute ingestion, storefront filters, appearance, market groups, tracking diagnostics and analytics API keys.

The Settings area is where a store configures Depict itself: who can access
the portal, which store data becomes attributes, which filters shoppers see,
how markets are grouped, and whether tracking events are arriving correctly.
It has eight sub-pages in the sidebar: **General**, **Users**, **Attributes**,
**Filters**, **Appearance**, **Markets**, **Tracking** and **Admin**.

## Limits and behavior

* All settings are per store. Switching store in the merchant switcher
  switches every setting described on this page.
* There are no user roles. Every member of a store has the same permissions;
  a view-only account cannot be created.
* There is no numeric limit on the number of users per store.
* You cannot remove your own account from a store's user list.
* Standard filters cannot be edited; only their order can be changed.
* The **Appearance** page exists only for stores on Shopify. It is hidden for
  all other platforms.
* The **Attributes** page is configurable only for stores on Shopify or
  Centra. Other platforms see "Not available for your platform".
* The **Admin** page is internal Depict tooling and is visible only to Depict
  staff.
* Deleting a market group moves its markets to the default group and deletes
  every merchandising exception scoped to that group.
* The **Tracking** page shows the last 72 hours of events and refreshes every
  30 seconds.
* Analytics API keys (created on **General**) are capped at 50 active keys
  per store; the key secret is shown once and cannot be retrieved again.
* The interface language setting is stored in the browser, not on the
  account: it applies per browser, not per user.

## General

The General page holds portal-wide preferences and the analytics API keys.

| Setting | Values | Default |
| - | - | - |
| **Language** — the portal interface language | English, Svenska | English |

When analytics is enabled for the store, the General page also shows an
**API keys** card for creating and revoking the read-only analytics API keys
used with the `X-API-Key` header. See
[Analytics API keys](/headless/features/analytics#analytics-api-keys) for the
key format, limits and the endpoints the keys unlock.

## Users

The Users page manages who can access the store in Depict. It lists every
member by email, with a **You** badge on your own account and an **Admin**
badge on Depict staff accounts. Every member has the same permissions — there
is no role system and no view-only mode.

To invite a teammate:

1. Open **Settings**, then **Users**.
2. Click **Invite user**.
3. Enter the teammate's work email.
4. Confirm the invite.

Result: the teammate appears in the member list. If they do not have a Depict
account yet, one is created — they sign in via "Forgot password" or SSO, and
they have the same permissions as you.

To remove a member, use the remove action on their row and confirm. Removal
takes effect immediately, and the person can be invited again at any time.
You cannot remove your own account.

## Attributes

The Attributes page configures which store data is ingested as Depict
attributes, used across search, filters and merchandising. The page's
contents depend on the store's platform:

| Platform | What the page offers |
| - | - |
| Shopify | Map Shopify options, metafields and tags to Depict attributes |
| Centra | Configure standard, mandatory and custom Centra attribute ingestion |
| Any other | "Not available for your platform" — contact Depict support |

### Shopify attribute mapping

Each attribute row shows its name, status (**Configured** / **Not
configured**) and data source. Four attributes are mandatory and always
present: **Color**, **Size**, **Gender** and **Age**. Title, description,
variant, image, original price, sale price, stock levels and brand are
ingested automatically and need no mapping.

To add an attribute:

1. Click **Add attribute**.
2. Enter a name in **Name the attribute**.
3. Pick one or more sources under **Select a source for its data** —
   Shopify options, Shopify metafields or Shopify tags.
4. Click **Add**.

Result: the attribute appears in the list with status **Configured**.

Constraints on the form:

| Rule | Value |
| - | - |
| Attribute name length | 1–255 characters |
| Sources per attribute | At least 1 |
| Tags as source for **Color** | Not allowed |

Tags with a shared prefix can be used as **Grouped tags**: all tags with the
same prefix are grouped, and future tags with that prefix join the group
automatically. The prefix must be followed by `-`, `_`, `/`, `:` or `+`
(for example `Designer_Chanel`).

### Centra attribute configuration

Three tabs: **Standard Centra attributes**, **Mandatory Depict attributes**
and **Custom Centra attributes**. Each row is configured with these columns:

| Column | Meaning |
| - | - |
| **Attribute ID** | Identifier for the attribute (custom attributes are prefixed `custom.`) |
| **Attribute Type** | The attribute's type |
| **Field Name** | The Centra field the data comes from |
| **Default Value** | Value used when the field is empty |
| **Set as N/A** | Marks the attribute as not applicable |
| **Include in display response** | Whether the attribute is returned in display responses |

Attribute IDs must be unique, and every row needs an attribute ID, type and
field name before the page can be saved.

## Filters

The Filters page configures the filters shoppers use to narrow product
listings on the storefront. Filters can be added, edited, deleted and
reordered by dragging. Standard filters cannot be edited; custom filters can.

<Warning>
  Deleting a filter removes it from the storefront and the Depict app
  immediately after you confirm.
</Warning>

Each filter is configured with:

| Setting | Values |
| - | - |
| **Filter name** | Free text |
| **Titles per locale** | One title per storefront locale; **Auto-translate** fills the other locales from one title |
| **Attribute used for its data** | Any configured attribute |
| **Filter type** | Checkbox, Radio Button, Color Checkbox, Hierarchical Checkbox |
| **Visibility** | "Shoppers (web store) and You (Depict app)" or "You only (Depict app)" |

Standard filters render with fixed types — for example price as a range
slider, on-sale and in-stock as toggles, size as a grid checkbox, categories
as a hierarchical checkbox, and color as a color checkbox.

Filter values can be managed per filter:

| Capability | Behavior |
| - | - |
| Value groups | **Add a group** collects values under one label; values can be moved between groups or un-grouped |
| Color swatches | A **Color swatch** (any CSS color, e.g. `#ff0000`) can be set per value |
| Sort | **Size**, **A-Z**, **Z-A**, **Occurrence** or **Custom** (drag values into order; the order is saved when the sort is set to "Custom") |

## Appearance

The Appearance page exists only for stores on Shopify. It configures how
Depict-rendered product cards, grids and sliders look on the storefront, with
a live approximate preview switchable between **Mobile**, **Tablet** and
**Desktop**. Two tabs: **Product card** and **Grid & slider**.

Product card settings:

| Setting | Values |
| - | - |
| **Image corner radius** | 4 steps from **None** to large |
| **Alignment** | **Align left**, **Align center**, **Align right** |
| **Show by default** | Toggles for **Title**, **Price**, **Original price**, **Sale badge**, **Sizes**, **Color options** |
| **Show on hover** | Toggles for **Switch to hover image**, **Image carousel** |
| Text styling (per text element) | **Text color**, **Background color**, **Bold**, **Italic**, font size up/down |
| **Custom design** | Ejects the product card to a fully custom implementation in TSX and Sass; disable to return to the settings above |

Grid & slider settings:

| Setting | Values |
| - | - |
| **Mobile columns** | 1–3 |
| **Tablet columns** | 2–5 |
| **Desktop columns** | 3–6 |
| **Margins** | 4 steps from **None** to large |
| Slider **Layout** | **Bleed over** or **Clean** |
| Slider **Show arrows** | On or off |

<Note>
  While **Custom design** is enabled, the product card settings above do not
  apply — the card is configured manually in code.
</Note>

## Markets

The Markets page groups a store's markets into market groups. Markets in a
group share merchandising rules and analytics scope — market groups are the
unit that merchandising, analytics and stock are scoped by across the portal.

* Drag a market onto a group to move it. Changes apply when you save.
* **Add market group** creates a group with a **Group name**; the group id is
  derived from the name and must be unique.
* One group is marked **Default**.
* Every group needs at least one market before the page can be saved.

<Warning>
  Deleting a market group moves its markets back to the default group and
  deletes every merchandising exception scoped to that group.
</Warning>

## Tracking

The Tracking page is a live diagnostic of the store's tracking integration:
the last 72 hours of events, whether their product ids map to the ingested
catalog, and purchase attribution quality. It refreshes every 30 seconds.

Four event feeds are shown, each with the id the events must use:

| Feed | Required id |
| - | - |
| **Click events** | Depict result IDs (unique to each product card in a Depict surface) |
| **Product page view events** | Product ID, on all product detail pages |
| **Add-to-cart events** | Product ID, on all add-to-cart actions |
| **Purchase events** | Transaction product ID, on the order confirmation page |

Each feed carries a product-id mapping status:

| Status | Meaning | Action |
| - | - | - |
| "All event product IDs map to ingested products" | Tracking ids match the catalog | None |
| "Some event product IDs can not be mapped to ingested products" | Part of the events reference unknown products | Check which id the integration sends against the **Product ID examples** table |
| "No event product IDs can be mapped to ingested products" | The integration sends ids Depict does not recognize | Fix the id field in the tracking integration |
| "No event product IDs to map" | No events of this type in the window | Verify the event is implemented and firing |
| "Couldn't load" | Diagnostic data unavailable | Retry later |

The page also shows **Purchase device ids with attribution events** — the
share of purchases whose device also produced attribution events — and a
**Product ID examples** table with sample ids from the ingested catalog, as
tracking events should reference them.

## Admin

The Admin page contains internal tools for Depict staff and is visible only
to Depict superusers. It is not part of the merchant-facing product.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.