> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/troubleshoot/branding/why-dont-i-see-the-branding-node-in-the-cloud-portal.md).

# Why don’t I see the “Branding” node in the Cloud portal?

*Applies to: Patch My PC Cloud*

### SYMPTOMS

I have signed into the Patch My PC (PMPC) Cloud portal, but I don’t see the **Branding** node under **Settings**.

<figure><img src="/files/oRjOZCskDePskrGkjKnu" alt="No &#x22;Branding&#x22; node"><figcaption></figcaption></figure>

### CAUSE

This is because your portal is not connected to an Intune tenant.

{% hint style="info" %}
**Note**

Not having an Intune tenant connected will also prevent the **Notifications** node from appearing.
{% endhint %}

### RESOLUTION

To resolve this issue, follow the [Connecting to an Intune tenant](broken://pages/RoXhXa1jcXhIcPcKJk05#connecting-to-an-intune-tenant) section of the [Managing Intune tenants](broken://pages/RoXhXa1jcXhIcPcKJk05) process.

Once your portal has been connected to an Intune tenant you will see the **Branding** node.

<figure><img src="/files/5RSMHbESRDirJe0QZmkj" alt="&#x22;Branding&#x22; node is now visible"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.patchmypc.com/patch-my-pc-cloud/troubleshoot/branding/why-dont-i-see-the-branding-node-in-the-cloud-portal.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.