Dashboard Permissions and Visibility
Understand who can see, edit, and use dashboard widgets.
Dashboard access depends on the user's role, the dashboard owner, and the dashboard visibility setting.
Use private dashboards for personal work and organization dashboards for shared team routines. Do not share dashboards that are still being configured or that contain widgets a wider team should not use.
Built-In Dashboards
Owners and admins receive built-in dashboards for:
- General
- CRM
- Finance
- Projects
Non-admin members receive a focused My Work dashboard with task, attendance, and active-project widgets.
Owned Dashboards
You can edit dashboards you own. Owned dashboards can be renamed, deleted, rearranged, and updated.
If a dashboard is view-only, you can still read it but cannot change its widgets, layout, name, or sharing settings.
Private Dashboards
Private dashboards are for your own workspace view. Use them for personal work queues, private review routines, or dashboards that are still being prepared.
Use private dashboards while experimenting with widgets or filters. Share only after the layout, data sources, and sensitive widgets have been reviewed.
Organization Dashboards
Organization dashboards are shared with the team. Use them for standard operating views such as sales review, delivery review, finance review, or owner overview.
Before making a dashboard organizational, open it with a non-owner role or ask a teammate to review it. Confirm the dashboard is useful to the audience and does not expose finance, HRM, or customer data unnecessarily.
Widget Access
Admins and owners can use the full widget library. Members can use widgets that match their access, including personal task, project, and clock-in/out widgets.
If a widget does not appear in the add-widget dialog, your role may not have access to that widget type.
Before Sharing a Dashboard
Review every widget for sensitive data, module dependencies, and role access. Finance, HRM, reports, and customer widgets may reveal data that not every team member should see.
Test With The Audience
Before sharing a dashboard broadly, test it with a user who has the same role as the intended audience. Confirm they can:
- open the dashboard
- see the expected widgets
- understand the filters and time periods
- open source records when they need to act
- avoid widgets that should stay private
A dashboard can look correct to an owner while showing less useful data to a member with narrower permissions.
Troubleshooting
If someone can open a dashboard but not see a widget, check their module permissions and whether the widget depends on data they cannot access.
If someone cannot edit a dashboard, confirm they own it or have the required admin access.
If a user can see a dashboard but cannot act on its data, review both dashboard visibility and module permissions. Visibility lets them open the dashboard; module access controls whether the underlying records are usable.
Sensitive Dashboard Examples
Keep these private or restricted until access is reviewed:
- owner finance dashboards
- payroll or HRM dashboards
- dashboards showing private customer accounts
- dashboards used for compensation, performance, or collections review
- dashboards with broad report widgets across the workspace
Change Visibility Safely
Before changing a private dashboard to an organization dashboard, remove widgets that expose finance, HRM, customer support, or owner-only operational data. Then ask one user in the intended audience to open the dashboard and confirm both the dashboard and the underlying records are visible.
If a widget disappears for that user, fix module or record permissions instead of assuming the dashboard itself is broken.