Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion site/guide/reporting/_create-an-analytics-page.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,6 @@ a. On the Add New Page module, enter the following:

- **Page Name**
- **Description** (optional)
- **Visible to Roles** (optional) — Select one or more organization roles to limit who can see the page. Leave empty to make the page visible to everyone in your organization.

a. Click **Add New Page** to create your custom analytics page.
a. Click **Add New Page** to create your custom analytics page.
21 changes: 21 additions & 0 deletions site/guide/reporting/manage-custom-reports.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,27 @@ Add, edit, or remove custom data to your analytics within the {{< var validmind.

:::

### Restrict an analytics page to roles

Custom analytics pages can be limited to selected organization roles, so that a page only appears on **{{< fa square-poll-vertical >}} Analytics** for the users who need it.

{{< include /guide/shared/manage-views/_role-visibility.qmd >}}

::: {.callout-important title="The default analytics page is always visible to everyone."}
Because the default page is every user's fallback, it cannot be restricted to roles — the **Visible to Roles** option is not offered when editing it.

:::

To change who can see an existing custom page:

1. On **{{< fa square-poll-vertical >}} Analytics**, click on the tab for the custom page you want to change.

2. Click **{{< fa pencil >}} Edit Dashboard**.

3. Click **{{< fa pencil >}} Details**.

4. Add or remove roles under **Visible to Roles**, then click **Save Changes**.

## Edit custom analytics

1. On **{{< fa square-poll-vertical >}} Analytics**, click on the tab for your custom page you'd like to edit the visualization for.
Expand Down
11 changes: 10 additions & 1 deletion site/guide/shared/manage-views/_organization-field-views.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,16 @@ To publish a saved personal layout to your organization, you must have permissio

6. (Optional) Edit the **Layout Name** and **Description** for your shared layout.

7. Click **{{< fa upload >}} Publish Layout** to share your layout with your organization.
7. (Optional) Select one or more roles under **Visible to Roles** to limit which users can see the layout.

8. Click **{{< fa upload >}} Publish Layout** to share your layout with your organization.

{{< include /guide/shared/manage-views/_role-visibility.qmd >}}

::: {.callout-important title="The organization default layout is always visible to everyone."}
Because the default is the layout every user falls back to, it cannot be restricted to roles. If you set a role-restricted layout as the organization default, clear its roles first.^[[Set shared layout as default](#set-shared-layout-as-default)]

:::

### Unpublish or remove shared layouts

Expand Down
31 changes: 29 additions & 2 deletions site/guide/shared/manage-views/_organization-table-views.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,13 @@ To publish a saved personal view to your organization, you must have permissions

6. (Optional) Edit the **View Name** and **Description** for your shared view.

7. Click **{{< fa upload >}} Publish View** to share your view with your organization.
7. (Optional) Select one or more roles under **Visible to Roles** to limit which users can see the view.

8. Click **{{< fa upload >}} Publish View** to share your view with your organization.

{{< include /guide/shared/manage-views/_role-visibility.qmd >}}

Role restrictions apply to shared views only — a personal view is only ever visible to you, so there is nothing to restrict. Unpublishing a view clears its role restriction.^[[Unpublish shared organization views](#unpublish-shared-organization-views)]

### Unpublish or remove shared views

Expand Down Expand Up @@ -94,12 +100,33 @@ To remove a saved organization view:

### Edit shared views

Editing while a shared view is active updates your personal default view instead of modifying the organization view. To edit a shared organization view:
#### Edit what a shared view contains

Editing while a shared view is active updates your personal default view instead of modifying the organization view. To change the filters, columns, or sorting of a shared organization view:

1. Unpublish the shared view from your organization.

2. Make the desired changes to your personal view.

3. Share the edited view with your organization.

#### Edit a shared view's name, description, or roles

Renaming a shared view or changing who can see it does not require unpublishing:

1. Click on the name of your saved view, or **{{< fa bookmark >}} Select View** if you are not currently displaying a saved view.

2. Select **Organization (#)**.

3. Hover over the view you want to change.

4. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select **{{< fa pencil >}} Edit View**.

5. Adjust the **View Name**, **Description**, or **Visible to Roles**, then click **Save Changes**.

::: {.callout title="Displaying a view that's no longer available to you?"}
Click **Exit View** to return to the default listing at any time.

:::

:::
13 changes: 13 additions & 0 deletions site/guide/shared/manage-views/_role-visibility.qmd
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
<!-- Copyright © 2023-2026 ValidMind Inc. All rights reserved.
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->

::: {.callout title="How role visibility is applied"}

- **Leave {{< fa users >}} Visible to Roles empty** to make this available to everyone in your organization. This is the default.
- Only organization roles can be selected,^[[Manage roles](/guide/configuration/manage-roles.qmd)] not record stakeholder types.^[[Manage record stakeholder types](/guide/configuration/manage-record-stakeholder-types.qmd)]
- [{{< fa hand >}} Customer Admin]{.bubble} users are not affected by role restrictions — they continue to see everything shared with the organization.
- Whoever published it keeps access, even if their own role isn't among the selected roles.
- If every role a restriction relies on is later deleted, it stays hidden rather than becoming visible to everyone. An admin can still reach it to adjust the roles or unpublish it.

:::
2 changes: 1 addition & 1 deletion site/llm/chatbot-product-map.md
Original file line number Diff line number Diff line change
Expand Up @@ -603,7 +603,7 @@
**Docs (related):**

- `/guide/configuration/customize-your-dashboard.html`
- Sections: Prerequisites; Manage dashboards; Add dashboards; Edit or remove dashboards; Manage widgets; Arrange widgets; Add widgets; Remove widgets
- Sections: Prerequisites; Manage dashboards; Add dashboards; Edit or remove dashboards; Share a dashboard with your organization; Manage widgets; Arrange widgets; Add widgets

- *No direct help link in frontend; related docs inferred from keywords.*

Expand Down
Loading