# How to Share Global "Template" Dashboards with All Embed Users (or a select group)

**URL:** <https://community.omni.co/t/how-to-share-global-template-dashboards-with-all-embed-users-or-a-select-group/439>\
**Category:** Embedded Analytics\
**Tags:** embed\
**Created:** [January 27, 2026, 11:40am UTC](https://community.omni.co/t/how-to-share-global-template-dashboards-with-all-embed-users-or-a-select-group/439 "2026-01-27T11:40:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![conor](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.omni.co/conor/32/45_2.png) [@conor](https://community.omni.co/u/conor)\
**Post date:** [January 27, 2026, 11:40am UTC](https://community.omni.co/t/how-to-share-global-template-dashboards-with-all-embed-users-or-a-select-group/439/1 "2026-01-27T11:40:06Z")

</div>

If you are setting up Omni in **Application Mode** (see [Create Mode docs](https://docs.omni.co/embed/customization/create-mode)), you often encounter a common requirement: **How do I provide a standard set of “Template” dashboards that every embedded user can see, but not modify?**

You might want every customer to start with a specific set of KPIs, which they can then duplicate and customize in their own private folders without altering the originals.

Here is the recommended workflow to achieve this using Groups and Embed URL parameters.

### Step 1: Create a “Global” Group

First, you need a way to group all your embedded users together inside Omni.

1. Navigate to **Settings \> Groups**.
2. Create a new group. For this example, we will call it **“All Embed Users”**.

It’s worth noting that each Embed entity will automatically have their own group created which you can view in `Settings` → `Groups` → `Embed`. In this example we are building templates to share with all embed users however.

### Step 2: Organize and Share Your Content

Next, set up the folder structure that holds your templates.

1. Create a folder (e.g., named **“Templates”** ) and move your standard dashboards into it.
2. Open the **Share** settings for that folder.
3. Add the **“All Embed Users”** group you created in Step 1.
4. **Crucial:** Set their access level to **Viewer**.

 ![Sharing the Templates folder with the group](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/6d39d35446e21e08478f314c46950abed9f2c0e3.png)

This ensures that users in this group can see the dashboards and explore the data, but they cannot edit the original dashboards or save new content into this protected folder.

### Step 3: Automate Group Membership via Embed Parameters

Now, you need to ensure that every time a user logs in via your application, they are automatically added to this group. You don’t need to do this manually; you can handle it dynamically during the Embed URL generation.

**Side remark** : Users are added to the embed entity group automatically. But to add to any other group, you have to use the [groups](https://docs.omni.co/embed/setup/url-parameters/groups) parameter.

When generating the signed URL for the user, include the `groups` parameter in your payload. This parameter accepts an array of group names.

**The Parameter:**

> `groups`: `["All Embed Users"]`

Refer to the [Parameters documentation](https://docs.omni.co/embed/setup/url-parameters/groups) for the exact syntax.

If you are using the Omni URL embed builder (useful for testing), it looks like:

 ![Adding to groups in the Omni URL embed builder](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/02428b6944d0ad0667b57fbe608e7fccf451669c.png)

### The Result: What the User Sees

Once this is configured, here is the experience for your end-users:

- **Automatic Access:** Upon their session start, the user is instantly added to the “All Embed Users” group.
- **Read-Only Templates:** They will see the “Templates” folder in their file browser.
- **Safe Exploration:** Because they are “Viewers,” they can open these dashboards, filter them, and explore. If they want to make changes, they can **Duplicate** the dashboard into their own private folder or entity folder to save their own version.

 ![Example hub for with pre-loaded templates for an embed user in application mode](https://canada1.discourse-cdn.com/flex004/uploads/omni/original/1X/9ad986249f7c132beccc8aa426168009bfaafa67.png)

This approach keeps your official templates clean while giving users the freedom to build on top of them.