01 / Central client management
Control across client workspaces
A central overview of client portals, users, workspace connections and access settings.
ENABLE / Client portal & central client management
One client portal for dashboards, data and AI
Bring dashboards, data products and applications together in a recognisable client workspace with ENABLE. Data Analytics helps configure sources, users and permissions so clients receive the information and tools that fit their work.
Inside the platform
A look inside ENABLE
From managing client workspaces to using dashboards and applications every day: two perspectives on the same platform.
02 / Client portal
Everything in one client portal
Dashboards, applications and activity together, with an overview of access and workspace configuration.
Illustrative, anonymised views based on the platform; no live client data. All data and names are fictional.
01
From scattered dashboard links to a shared workspace
A report by email, a dashboard in another tool and an application behind yet another link: clients have to remember where information lives. Administrators face the same fragmentation. When someone joins or a client leaves, someone must work out which permissions were granted where. A client portal for dashboards and AI organises the user experience around the client workspace rather than individual tools.
This is a business workspace for BI, data and applications, not a standard customer-service ticket portal. The goal is to share dashboards and applications with clients through a clear workspace. An organised portal does not remove the configuration behind the scenes: source permissions, report access and management responsibilities still need to be correct separately.
02
What does your client see in the workspace?
The illustrated portal view brings together a dashboard overview, favourites, recently viewed items, applications and activity. The client workspace is the starting point: relevant reports and applications are determined during setup. The public ENABLE platform demo also shows dashboards, user management and groups. These elements provide a foundation for organising users and content deliberately.
SQL Explorer is visible in the public platform demo as an analysis workspace with a query, result and chart. Whether clients receive access depends on their role, connected sources and agreed data permissions. The illustration also shows AI Builder and AI applications in the navigation. This does not promise that every AI application is ready to use or can take actions in your systems: available apps, models and permissions are agreed for each setup.
03
Central client management for service providers and accountants
Serving several organisations requires more than a good portal for end users. You also need an overview of configured client workspaces, their users and workspace connections that need attention. The illustrative Clients view shows this management perspective: a client overview with status, usage, Power BI and access settings. All names and counts in this image are fictional.
For an accounting firm, an initial setup might focus on periodic reports for each set of accounts. For a service provider, it might involve dashboards and a focused analysis app per client. These are setup examples, not proven customer outcomes. Agree who onboards clients, approves access and reviews changes. In a multi-tenant client portal, separation between organisations must be explicitly designed and tested; a client list alone does not prove technical isolation.
Explore AI for accountants04
Power BI in your client portal: reports and permissions
A client portal with Power BI dashboards provides a recognisable starting point for reporting. Connecting it involves reviewing existing reports, workspaces, the semantic model and how clients receive access. This website includes a Power BI embed integration; availability for your organisation requires appropriate Microsoft configuration, licensing or capacity and configured report and workspace permissions. A portal does not replace these requirements.
An existing semantic model can be the starting point, avoiding the need to reinvent definitions and calculations for each application. First check the model's quality, ownership and access rules. A possible MCP connection to a Power BI semantic model is a separate track for authorised AI analysis. That connection is not automatically active because a report appears in the client portal, and does not grant extra permissions beyond the agreed scope.
05
Secure collaboration starts with access profiles
Define the difference between a client user reading reports, an analyst investigating data and an administrator managing access. User management and groups are visible in the platform demo; exact permissions must match your setup. Portal access, dashboard access, source access and AI app access are separate controls. Test with representative users whether they can reach only the intended information, including outside the navigation.
Include access revocation in the management process. When someone leaves or an engagement ends, accounts, group memberships and permissions in connected systems need review. Account for active sessions and previously issued access tokens: a change in one system does not automatically revoke all access immediately. Separate client environments, logging and periodic permission reviews also require demonstrable configuration. We do not claim absolute security or automatic compliance.
06
AI where it fits, with deliberate data access
An AI client portal for businesses should be more than a chatbot next to a dashboard. First choose the question an application needs to support, such as investigating an anomaly in a report. Then define which data, calculations and context the application may use. Review answers substantively and agree human oversight before AI shares information or performs an action. The example screens are not evidence of autonomous actions.
Private AI and an external AI service connected through MCP are different choices. A restricted platform environment does not automatically keep model processing local. With external models, permitted context may be processed outside your organisation. Discuss model choice, data flows and access boundaries separately. MCP is a possible connection to authorised data and tools, not a language model or a security guarantee.
From requirements to setup
A client portal in four steps
- 01
Connect sources
Select reports, models and sources for the first client workspace. Check availability, definitions and ownership.
- 02
Configure permissions
Define client boundaries, roles and approval. Test portal, report and source permissions with different user profiles.
- 03
Make dashboards and apps available
Set up a recognisable workspace with agreed content. Review reports and any AI outputs before granting user access.
- 04
Monitor and expand
Agree management, permission reviews and incident follow-up. Add clients or applications only after validating the setup.
Frequently asked questions about the client portal
Can I share Power BI dashboards with clients?
That is a use case for the client portal. For your setup, we check reports, workspaces, Microsoft configuration, licensing or capacity and authorisation. Portal access alone does not grant access to every report.
Can I onboard my own clients?
The management illustration shows a central client overview. Discuss in the demo who may create client workspaces and which steps are needed for users, connections and approval. The image does not prove that a complete self-service onboarding process is already configured for your organisation.
How does authorisation work in the client portal?
Users and groups help organise access. Define which reports, sources and applications each role may reach, then test this in both the portal and connected systems. Also define how access is revoked and active sessions are handled.
Can my existing Power BI semantic model be connected?
An existing model can be a starting point after reviewing definitions, permissions and technical connectivity. Any MCP connection for AI analysis is configured separately; a portal or embed does not automatically make it available.
Can the client portal be combined with Private AI?
Discuss your preferred hosting and model choice. On-premise, private cloud and managed cloud are possible approaches. What stays local and which context an external model service receives depend on the chosen solution and must be explicitly checked.
Can I see a demo of the client portal?
Yes. Book an ENABLE demo and tell us which dashboards, client organisations and applications you want to discuss. We compare the platform approach with your needs and explain what is available and what requires additional configuration. The screens on this page are fictional illustrations, not live client data.
Explore your data and AI options
Discuss your own client portal
Which dashboards do you want to share, which clients need access and which apps are useful? Explore what fits your organisation and what configuration is needed in an ENABLE demo.