# Trusted Domains

> **Caution**
>
> These settings are restricted to **Hub administrators.**

Hub keeps two different allowlists here. **Internal email domains** decide which company email domains can receive internal access when a portal enables that option. **Trusted domains for embedded content** decide which secure websites may host authenticated embeds. Add a domain to the list that matches the access problem you are solving; the two lists are not interchangeable.

## Internal email domains

Internal email domains simplify access management for your organisation’s portals. Instead of adding company domains to each portal, Hub administrators define one global list of approved domains.

> **Note**
>
> 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/#unlock-internal).

### Adding an internal email domain

Navigate to the global **Settings > Trusted domains** via the overview page or the workspace dropdown within a workspace.

Click the **Add domain** button in the *internal email domains* section

Add your internal email domains. For example: **example.com**

## Trusted domains for embedded content

Verified User Tokens and manual sign-in are only supported for embeds served from domains on this allowlist and only when the hosting page uses HTTPS. Add the origin of the page that contains the embed, not the Released URL. This prevents an authenticated embed from being reused on an unapproved site.

### Adding a trusted domain

Navigate to the global **Settings > Trusted domains** via the overview page or the workspace dropdown within a workspace.

Click the **Add domain** button in the *trusted domains for embedded content* section

Add your trusted domains. For example: **example.com**

> **Note**
>
> If you run into issues embedding your portal, see the [Embeds Troubleshooting Guide](/guide/resources/troubleshooting/embeds/).