> For the complete documentation index, see [llms.txt](https://help.circlehd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.circlehd.com/management/settings/portal-settings.md).

# Portal Settings

On the **Portal Settings** section, you can define the below:

![](/files/-MOem6eLs8H4gm7A0Jct)

**1-** Enter your **Organization Name \[1]**&#x20;

**2- Describe** your portal in a few words **\[2]**&#x20;

**3-** Set the portal **Logo** **\[3]**, for best results upload a transparent png 400X50px image or larger with 1:8 ratio&#x20;

**4-** **Video Embedding Whitelisting of Domains \[4]**&#x20;

By default users must be logged in to watch on the embed. If you have a trusted site, and you don't like to force the users to log-in before watching, you can enable trusted site under portal settings.

Users accessing iframe based embedding from these domains will not be prompted to login. However, the username will not show up in analytics if they have not previously logged into CircleHD

**5-** Select the **Default Timezone** for the portal **\[5]**&#x20;

**6-** Click on the "**Save**" button **\[6]** when finish


---

# 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, and the optional `goal` query parameter:

```
GET https://help.circlehd.com/management/settings/portal-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
