> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/insights/dashboards/dashboard-sharing.md). # Dashboard Sharing Guide Guide to sharing dashboards with teams and via email notifications. This document covers Veza's dashboard sharing capabilities for collaboration with individual users or other teams. You can share custom dashboards directly with [teams](/4yItIzMvkpAvMVFAamTf/administration/administration/users/teams.md) defined in Veza, or distribute them via email notifications with customizable recipients and messaging. Three sharing methods are supported: * **Team Sharing**: Direct sharing with other Veza teams for ongoing collaboration (via the **Share** button) * **Email Sharing**: Send notification emails with links to view dashboards in Veza (via the **Share** button) * **Save and Notify Team**: Publish a dashboard and alert your team in one step (via the **Save** button). Recipients find the dashboard in their **New from Team** section under Favorites. This method requires the dashboard to have Public visibility. {% hint style="info" %} **Sharing individual queries across teams**: Sharing a dashboard is the recommended way to make queries accessible to other teams. To share individual queries with all tenant users, set the query visibility to **Public**. See [Query visibility](/4yItIzMvkpAvMVFAamTf/features/search/saved-queries.md#query-visibility) for details. {% endhint %} {% hint style="info" %} **Sharing edits to out-of-the-box queries**: If a dashboard you share contains out-of-the-box (OOTB) assessment queries that your team has edited, you can opt in at share time to share those edits along with the dashboard. Recipient teams then see your team's edited version instead of their own copy, and any **future edits** you make to those queries propagate automatically to every team the dashboard is shared with — no re-sharing required, exactly like custom queries. See [Share edited out-of-the-box queries](#share-edited-out-of-the-box-queries) below. {% endhint %} {% hint style="info" %} Only custom (user-created) dashboards can be shared between teams. Out-of-the-box (system) dashboards are already available to all users with access to the required integrations and cannot be team-shared — clicking **Share** on an OOTB dashboard shows the message *"This is a built-in dashboard visible to all users. Use 'Share via Email' to notify specific people."* To create a customizable version, clone the system dashboard first. {% endhint %} {% hint style="warning" %} Role Requirements: Team sharing requires Operator role or higher, while email sharing is available to any role. {% endhint %} {% hint style="info" %} Resharing Limitations: Only the original dashboard owner (the team that created the dashboard) can share it with additional teams. If a dashboard was shared with your team by another team, clicking **Share** shows *"This dashboard was shared with your team by another team. You have view-only access."* — it cannot be reshared. {% endhint %} ### Prerequisites Before sharing dashboards: * **Team Sharing**: Target teams must have access to the integrations used in dashboard queries. For example, if a dashboard contains a query like "Okta users who have access to S3 buckets," then the team with whom the dashboard is shared should have access to both Okta and AWS integrations. In case they have access to only one of those integrations, the query will not be displayed. All required integrations must be in the [active team scope](/4yItIzMvkpAvMVFAamTf/administration/administration/users/teams.md#change-the-active-team). * **Email Sharing**: Individual recipients must be configured as Veza Actions (see [Veza Actions documentation](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications.md)), so you cannot address someone who has not already been added as an Email notification target. Okta and Azure AD groups carry no such requirement: Veza resolves each group's members to email addresses when it sends the notification. ### Sharing Methods {% tabs %} {% tab title="Share with Teams" %} Share dashboards directly with other teams in your Veza organization to enable cross-team collaboration and visibility. #### Share Dashboard with Teams 1. Open the dashboard you want to share. 2. Click the **Share** button in the upper-right corner. The modal displays a contextual message — *"This dashboard is only visible to your team. Share it with other teams to grant them view-only access."* — if the dashboard has not yet been shared. 3. In the **Add teams to this Dashboard** field, search for and select target teams. Teams that already have access and your own team are automatically filtered out. 4. Click **Share** to open the confirmation modal with integration validation. ![A warning appears if any integrations aren't shared with the team.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-ede57cc1751cc699aacae4eab935f672c0585869%2Fconfirm-team-sharing.png?alt=media) 5. Review the confirmation details and click **Confirm**. The dashboard appears in the target teams' **Shared** section, with real-time data updates based on each team's integration scope. #### Share edited out-of-the-box queries Out-of-the-box (OOTB) assessment queries — labeled **system queries** in the share dialog — are instantiated separately for every team, so each recipient team owns its own copy. By default, these edits are not shared: the confirmation modal notes that the dashboard's system queries are *"system-created and already available in all teams,"* and each recipient team sees its own copy. For more about how Veza tracks these copies against the query catalog (including updates Veza ships for a query after it has been shared) see [Manage Out-of-the-Box Queries](/4yItIzMvkpAvMVFAamTf/features/search/saved-queries/manage-ootb-queries.md). To share your team's edits instead: 1. Share the dashboard with teams as described above. If the dashboard contains system queries, the confirmation modal shows a **System Queries** section (for example, *"3 System Queries"*). 2. Select **Include system queries (override recipients' copies with this dashboard's version)**. This checkbox appears only for root-team members and only when the dashboard contains system queries. ![The confirmation modal lists system queries with an option to override recipients' copies.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-912f91370d91c76c11362a9600a9621452a2c96d%2Fconfirm-team-sharing-system-queries.png?alt=media) 3. Click **Confirm**. Recipient teams now resolve your team's version of each shared system query, and any future edits you make to those queries propagate automatically — no re-sharing required. {% hint style="warning" %} If any recipient team has locally edited its own copy of a shared system query, selecting the checkbox shows a **Local edits will be overwritten** warning that names the affected teams. Confirming will overwrite each named team's locally edited system queries with this dashboard's version. {% endhint %} {% endtab %} {% tab title="Share via Email" %} Email sharing sends a notification with a link to view the dashboard in Veza. You can address the notification to individual recipients, to Okta or Azure AD groups, or to both. Recipients must have Veza access to view the dashboard content. #### Share Dashboard via Email 1. Open the dashboard you want to share. 2. Click the **Share** button in the upper-right corner. ![Click "Share" to show collaboration options for the dashboard.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-763af1679b3103f6db22693fe345bc0d63b46189%2Fshare-dashboard.png?alt=media) 3. Select **Share via Email** to open the email sharing modal. 4. Select recipients from the **Recipients** dropdown (pre-configured email notifications in Veza Actions). ![Adding a custom subject line and addition note to the email message.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-574f7cc28f1cc9e3272ad96e60c423c740647fcc%2Fshare-via-email.png?alt=media) 5. To address the notification to groups, select one or more Okta or Azure AD groups in the **Groups** field. Type to search the list by group name. 6. Customize the subject line and optionally add a note in the **Additional Note** field. 7. Click **Send** to deliver the email with a "View Dashboard" link. #### Share with Okta and Azure AD groups The **Groups** field addresses the notification to the members of one or more Okta or Azure AD groups, so you do not have to configure each person as an email notification target first. Use it on its own or alongside **Recipients**. A share must name at least one recipient or one group; submitting the form with neither returns *"Select at least one recipient or group."* Only Okta groups and Azure AD (Entra ID) groups are available in the **Groups** field. Other identity providers are not supported. * **Membership resolves when Veza sends the notification**, not when you select the group. A person added to the group before the send receives the dashboard link. * **Membership comes from the Access Graph**, so it reflects your most recent Okta or Azure AD extraction rather than the current state of the directory. A group whose membership changed since the last extraction resolves to the membership Veza last collected. * **Addresses are deduplicated.** Someone who belongs to more than one selected group, or who is also named individually under **Recipients**, receives a single email. * **Members without an email address are skipped.** * **Group members are blind-copied**, so no recipient sees the rest of the group. * A single share accepts at most **50 groups**. {% hint style="info" %} Group members still need Veza access to open the dashboard. Addressing a group does not grant access to the dashboard or to the integrations its queries depend on. {% endhint %} {% endtab %} {% endtabs %} ### Managing Shared Dashboards Teams that receive shared dashboards can find them in the **Shared** section of their Dashboard Library. Shared dashboards display data based on the recipient team's integration scope. Queries requiring integrations that are not in the recipient team's active scope will not be visible in the dashboard. #### Integration Requirements {% hint style="warning" %} For multi-integration queries (e.g., "Okta Users → Salesforce Admin Access"), recipient teams must have access to ALL required integrations. Queries with missing integrations will not be visible in the shared dashboard, but the dashboard sharing itself succeeds. When the recipient team later gains access to the missing integrations, those queries will automatically become visible; no manual re-sharing is required. {% endhint %} ### Unshare behavior To stop sharing a dashboard with a team, open the **Share** dialog and, under **Team Access**, click the delete (trash) icon next to the team you want to remove. Unsharing removes that team's **view access to the dashboard**, but it does not revoke access to the queries that were shared through it. ![Remove a team's access with the delete icon next to its entry under Team Access.](https://1967633068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZDkWMxox3pekd0NsZJ%2Fuploads%2Fgit-blob-7a64801ed95a88d316ba4e0359b557151fbbf04b%2Funshare-dashboard.png?alt=media) * Queries shared through the dashboard (including any OOTB queries shared via the opt-in above) **remain accessible** to the recipient team and are **not removed**. {% hint style="warning" %} Unsharing does **not** restore a recipient team's original local copy of an overridden OOTB query. Because a query may also have been shared directly via another path, Veza cannot safely determine whether restoring the original copy is correct. The recipient continues to resolve the shared version. {% endhint %} ### Limitations * **No retroactive updates**: Dashboards shared before OOTB query edit propagation was available are not updated automatically. You will need to re-share the dashboard to apply the new behavior. * **Static queries out of scope**: Built-in and uneditable static assessment queries cannot be edited and are therefore not affected by OOTB query edit sharing. ### See also * [Team Management](/4yItIzMvkpAvMVFAamTf/administration/administration/users/teams.md) - Managing teams and integration scopes * [User Roles and Permissions](/4yItIzMvkpAvMVFAamTf/administration/administration/users/roles.md) - Understanding role requirements * [Dashboards](/4yItIzMvkpAvMVFAamTf/features/insights/dashboards.md) - Main dashboard documentation and features * [Veza Actions](/4yItIzMvkpAvMVFAamTf/administration/administration/notifications.md) - Configuring email notifications --- # 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://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/insights/dashboards/dashboard-sharing.md?ask=&goal= ``` `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.