# Account Structure - FAQ

<details>

<summary>Do I need multiple containers for subdomains?</summary>

No. Technically, most subdomain setups work well with one container. Split into multiple containers only if it helps your organizational workflows.

</details>

<details>

<summary>Can I share items across accounts?</summary>

No. Accounts are isolated. Share and reuse configurations **only within the same account**.

</details>

<details>

<summary>Will containers on the same domain share user IDs by default?</summary>

If the **Main Domain Cookie** is enabled, yes—containers on the same main domain and its subdomains will share a user ID. You can disable this per container to prevent sharing.

</details>

<details>

<summary>What if I operate different country domains?</summary>

Create **one container per domain** within **one account** and reuse shared configurations across those containers.

</details>

<details>

<summary>How can I use the same tool or tag on multiple implementations?</summary>

All containers are maintained in a single JENTIS account.

So you can use the same tools, tags and codes in all or only in selected containers. You don’t need to copy-paste settings from one account to another. Even if the container and embed snippet is different on all domains, the JENTIS Tag Manager configuration is always managed globally in a single account.

</details>

<details>

<summary>How do I set up a tool only in one domain?</summary>

A domain is always connected to a single container; this is a 1:1 relationship. To implement a tool or a tag on only one container, you must select only this specific container.

</details>

<details>

<summary>Can I have only one global container on multiple websites (domains)?</summary>

No, a container, embed snippet, and DNS record are defined per domain. JENTIS is a first-party tool and can only be used in a first-party context. As the cookies set and associated with JENTIS are set via HTTP, this architecture does not support loading a third-party JS embed snippet, as the cookies would still be set in that third-party context via HTTP.

This is a browser security and data privacy measure that can not be circumvented.

</details>