# Subsidiary Branding & Default Catalog

The Subsidiary Branding & Default Catalog section lets you assign a logo, theme, and default product catalog for the selected subsidiary. These settings override the global branding from [General Settings](/netsuite-admin-guide/overview/general-settings.md).

## Accessing Subsidiary Branding

{% stepper %}
{% step %}

### Open the NetSuite Admin view

Switch to **NetSuite Admin** in <code class="expression">space.vars.productName</code>.
{% endstep %}

{% step %}

### Select the subsidiary

Use the subsidiary switcher at the top right.
{% endstep %}

{% step %}

### Open Configurations

Click **Configurations** in the left sidebar, then scroll to the **Subsidiary Branding & Default Catalog** section.
{% endstep %}
{% endstepper %}

## Fields

| Field               | Description                                                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Logo**            | Upload an image to use as the portal logo for this subsidiary. If left blank, the global logo from General Settings is used. |
| **Theme**           | Select a theme to use for this subsidiary. If left blank, the global theme is used.                                          |
| **Default Catalog** | The product catalog shown to users of this subsidiary when no other catalog rule applies.                                    |

Click **Save Changes** after editing.

## How branding inheritance works

<code class="expression">space.vars.productName</code> resolves branding through a cascade — more specific settings override broader ones:

```
Global Branding (General Settings)
  └── Subsidiary Branding (Configurations)
        └── Location Branding
              └── Entity Role Branding
                    └── User-Specific Branding
```

If no logo is set at the subsidiary level, users in this subsidiary see the global logo. If a location or role has its own branding configured, that takes priority over the subsidiary branding.

## Tips

* You don't need to configure branding at every level. Set it only where it needs to differ.
* The Default Catalog determines which catalog loads first when a user logs in to the portal. Users can switch catalogs if their workflow permits it.

## Related Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>General Settings</strong></td><td>Global branding fallback.</td><td><a href="/pages/wQdfp866XcwgC1lNk6Pf">/pages/wQdfp866XcwgC1lNk6Pf</a></td></tr><tr><td><strong>Theme Builder</strong></td><td>Create and edit themes to assign here.</td><td><a href="/pages/tKpdt9UlBIUiF0YP8r0t">/pages/tKpdt9UlBIUiF0YP8r0t</a></td></tr><tr><td><strong>Configurations Overview</strong></td><td>All sections on the Configurations page.</td><td><a href="/pages/gogCTxJRLdzy1P6i1xeB">/pages/gogCTxJRLdzy1P6i1xeB</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/netsuite-admin-guide/overview-1/subsidiary-branding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.