Partner Portalexternal
Partner-Scoped Reports & Dashboards
Can we give a partner a report or dashboard without giving them our internal reporting?
Reports and dashboards in continON carry a permission scope, and that scope can name partner audiences as well as internal positions. A dashboard intended for a supplier is the same definition your team built — the scope decides who sees it, instead of anyone maintaining a second copy.
How it works
Permissions are a property of the report or dashboard definition itself. When a report or dashboard is designed, its access list is assigned in the same designer that built it, and that list can reference internal position seats and partner audiences through one permission model. There is no separate partner reporting tool to maintain: the artifact is designed once and scoped for each audience that should see it.
Because the scope is enforced at the permission layer, what a partner-scoped report exposes is bounded by that scope and by the organization the records belong to. The practical effect is that a recurring question — can our supplier see the status of their own orders without seeing anyone else’s — becomes a scoping decision on an existing report rather than an export someone emails every week.
Where the control sits
Outside the organization
Scoped at the definition, not the export
Access is assigned on the report or dashboard definition itself, so scope survives every refresh instead of depending on who a file was emailed to.
Positions and partners in one model
The same permission mechanism that binds reports to internal position seats can name partner audiences — one model for both sides of the boundary.
Built with the standard designers
Partner-facing reports and dashboards are produced by the same report and dashboard designers used internally; there is no parallel toolchain.
Organization-bound data
Report data stays scoped to the owning organization and the records the permission scope allows, which is what makes partner-facing output safe to share.
InsideThe record inside Partner Portal
What this touches
- Report Designer
Reports are designed and permission-scoped — including partner scopes — in the report designer. - Dashboard Designer
Dashboards carry the same permission assignment, applied when the dashboard is designed. - Identity & Access
Partner scoping rides the platform permission model that also binds access to positions and seats.
See partner-scoped reports & dashboards running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.