# Trusted Domains

{% hint style="warning" %}
These settings is restricted to **Released administrators.**
{% endhint %}

## Internal email domains

Internal email domains simplify access management and for your organization’s portals in the Product Hub. Instead of manually adding company domains to each portal, Released administrators can define a global list of approved domains. 

{% hint style="info" %}
Internal email domains will get access to a portal when the internal domains option is enabled within the [portal access settings](/guide/product/portals/access.md#internal). 
{% endhint %}

### Adding an internal email domain

{% stepper %}
{% step %}
Navigate to the global **Settings > Trusted domains** via the overview page or the workspace dropdown within a workspace. 
{% endstep %}

{% step %}
Click the **Add domain** button in the *internal email domains* section
{% endstep %}

{% step %}
Add your internal email domains. For example: **example.com**
{% endstep %}
{% endstepper %}

## Trusted domains for embedded content

To protect your users, Verified User Tokens and manual sign‑in are only supported for embeds served from domains on your configured allowlist and only when the hosting page uses HTTPS. In other words, the embed’s origin must be explicitly permitted in your application’s domain settings, and the page that hosts the embed must be delivered securely (https\://) with a valid TLS certificate.

### Adding a trusted domain

{% stepper %}
{% step %}
Navigate to the global **Settings > Trusted domains** via the overview page or the workspace dropdown within a workspace. 
{% endstep %}

{% step %}
Click the **Add domain** button in the *trusted domains for embedded content* section
{% endstep %}

{% step %}
Add your trusted domains. For example: **example.com**
{% endstep %}
{% endstepper %}

{% hint style="info" %}
If you run into issues embedding your portal, see the [Embeds Troubleshooting Guide](/guide/resources/troubleshooting/embeds.md).
{% endhint %}


---

# 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.released.so/guide/product/administration/trusted-domains.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.