External Collaboration Portal
Your external network, served. Your data, at home.
A white-label portal for the partners, brokers, suppliers, members and clients you work with. They sign in without a password, read what is meant for them, download secure documents, and submit claims and requests that land straight in your Dataverse. Deployed into your own Microsoft Power Platform environment, so their data never leaves your tenant.
- Runs in your Microsoft tenant
- Native Dataverse
- Passwordless, invitation-only sign-in
- No per-user fees from us
- White-label and multi-brand
One portal, any external audience:
- Insurers and brokers
- Employee-benefits networks
- Distributors and dealer networks
- Franchise systems
- Associations and member bodies
- Manufacturers with resellers or service partners
- Suppliers and outsourced providers
- Key clients who need a shared workspace
Your external network runs on email and phone calls.
Scattered communication
Your partners email you for documents and phone to ask where a claim is. They miss last month's announcement because it was one of forty emails that day.
Unstructured submissions
Claims and requests arrive as attachments somebody has to re-key, with no status the partner can see.
The usual fixes are worse
A custom-built portal means a systems-integrator project and a yearly maintenance budget. A SaaS portal moves your data into a third-party cloud and charges per company, per module or per seat.
Modules you switch on per portal, and per company.
Home page and page builder
A home page you compose, not code. Choose a layout, drop in web parts such as a hero banner, announcement bar, news cards, upcoming events, quick links or a countdown, and publish. Editors see the draft exactly as partners will.
News and events
Publish to your whole network or to a single partner. Write in a block editor inside the portal, schedule the publish date, add categories, and let the notification bell tell partners something new is waiting.
Secure document library
Share contracts, guides and price lists with the right company and nobody else. Files sit in private cloud storage and are downloaded through short-lived links generated on each click.
Claims
Submit claims with attachments and follow them to resolution. A comment thread on each claim keeps the external user and your back office in one conversation, with each side clearly labelled.
Service requests
Every kind of request, in one structured place. Define a request type, describe its fields, and the form builds itself. A new type is a row of configuration, not a project.
Support tickets
A support desk with statuses your partners can see, and a FAQ section that answers the questions before they are asked.
Notifications
A notification bell shows each user what is new for them: news, upcoming events, new documents, and event reminders. Users only ever see notifications about things they are allowed to read.
Entitlements and access tiers
Turn modules on or off for the whole portal, then refine per company. Give every organisation in your network a foothold with a lighter tier, and unlock the full portal for the ones you licence.
Branding and multi-brand
Your logo, your colours, your fonts. Branding is configuration, so launching a second brand or a second site does not need a developer.
Passwordless sign-in
External users sign in with a one-time code sent to their email. No passwords, no Microsoft account required. Invitation-only: without an invitation nobody can create an account.
Administration without deployments
Module switches, branding, content, pages and entitlements are configuration. Your Power Platform team keeps control, and nobody waits for a release.
No user cap, no company cap, your tenant, native Dataverse.
- 01
It runs in your tenant.
Deployed into your own Power Platform environment. External companies are your Accounts, their users are your Contacts, submissions are your Dataverse records. No vendor cloud, no data export, no integration project.
- 02
No per-user fees from us.
One flat monthly fee whatever the size of your network. Editions differ by modules, sites and support, never by users or companies.
- 03
Security enforced at the data layer.
Who sees what is decided by Power Pages table permissions on the record, not by filters in the browser. If someone tampers with the page, they still cannot read another company's data.
- 04
Your team runs it without developers.
Content, pages, branding, entitlements and settings are configuration. New request types are data. New brands are rows.
- Fits the Microsoft stack you already own: Dataverse, Dynamics 365, Power Automate and Entra.
- A fraction of the cost of a custom build: a flat monthly fee and a one-time launch package.
- Built for networks: per-company content and entitlements, a lighter tier, and a comment thread on every claim.
- White-label and multi-brand from the same solution.
- Your data stays in the Microsoft region of your Power Platform environment.
- Upgrades that never break your setup: a managed solution, and every upgrade is additive.
Everything after the browser is your own tenant.
- 1
We deploy into your environment
A managed Power Platform solution plus a Power Pages site, installed in your tenant, in your region, next to your Dynamics 365 data.
- 2
Your external users are your CRM records
Companies are Accounts, users are Contacts. Invite someone by creating the contact and giving it a role.
- 3
They sign in without a password
A one-time code by email, through Microsoft Entra External ID. Uninvited users cannot register.
- 4
Everything is filtered at the source
Power Pages table permissions decide which news, documents, claims and requests a user can read. The portal only shows what the data layer returns.
- 5
Your team publishes from the portal
Pages, news, events, documents, branding and entitlements are configuration. No release needed.
- 6
Submissions land in Dataverse
Claims, requests and tickets are records your staff handle in Dynamics 365, with Power Automate for anything that needs a workflow.
Isolation enforced where the data is, not in the browser.
- Data residency
- All portal data is Dataverse data in your own environment and Microsoft region. Innodux Labs holds no copy.
- Authorisation at the data layer
- Table permissions scope every table to the user's company or to a global audience. Client-side code cannot widen access.
- Fail closed
- If entitlement data cannot be read, the portal shows a “contact support” state rather than falling back to full access.
- Documents
- Private Azure storage, no public containers, time-limited download links generated per click. The browser never receives a permanent file address.
- Identity
- Microsoft Entra External ID for external users, your corporate Entra ID for staff. Invitation-only, enforced at the identity provider and at the portal.
- Content safety
- Rich text authored in the portal is sanitised on save and again on render.
- Separation of duties
- Content managers can publish but not delete; only administrators delete. Archiving is the normal path.
- Managed solution
- The product's schema cannot be altered by accident, and upgrades are controlled.
The underlying platform is covered by Microsoft's Power Platform compliance programme.
The real alternative is a custom build.
If you want external users' data inside your own Microsoft tenant, the choice is between this portal and a systems-integrator project.
| Criterion | Custom build | Enterprise partner suite | Generic client-portal SaaS | External Collaboration Portal |
|---|---|---|---|---|
| Where the data lives | Your tenant | Vendor cloud, often North America | Vendor cloud | Your tenant, native Dataverse |
| Pricing basis | Project plus yearly maintenance | Per company, module or seat | Per seat or per portal | Flat monthly fee |
| Time to live | Months | Weeks to months, plus integration | Days, but disconnected from your CRM | Weeks |
| Dynamics 365 / Dataverse | Custom | Connector, sync | None or shallow | Native, same records |
| Who runs it day to day | Developers | Vendor admin console | Vendor admin console | Your own team, from configuration |
A flat monthly fee. No per-user fees from us.
- A flat monthly fee, invoiced annually.
- No user cap and no company cap on any edition.
- Editions differ by modules, number of sites or brands, and support level.
- A one-time launch package covers deployment into your tenant, identity setup, branding, permissions and administrator training.
- You also pay Microsoft for Power Pages capacity, metered per authenticated user per month. We always quote it alongside our fee, so you see the all-in cost.
For an all-in quote, tell us two numbers: how many external companies you work with, and how many of their users you expect to sign in each month.
Get a quoteA launch package, not a project. Weeks, not months.
- 1 Environment check and deployment of the managed solution and Power Pages site.
- 2 Identity: Entra External ID for external users, corporate Entra ID for staff.
- 3 Branding and home page composition.
- 4 Roles, entitlements and table permissions for your tiers.
- 5 First content: news, events, documents, request types.
- 6 Administrator training and handover.
Prerequisites: a Microsoft Power Platform environment with Dataverse, Power Pages capacity licensing, and an Entra External ID tenant for external sign-in (we set this up as part of the launch package).
Questions we're asked most.
Where does our data live?
In your own Dataverse environment, in the Microsoft region you chose. Innodux Labs keeps no copy. External companies are your Accounts and their users are your Contacts.
Who can we use it with?
Anyone you collaborate with outside your organisation: partners, brokers, distributors, suppliers, members or clients. The portal is the same; you decide the audience, the modules and what each company sees.
Do external users need a Microsoft account?
No. They sign in with a one-time code sent to their email address, through Microsoft Entra External ID. Your own staff sign in with their corporate Microsoft account.
Can anyone register?
No. Registration is invitation-only and enforced both at the identity provider and at the portal. A user without a matching contact cannot get in.
What licences do we need from Microsoft?
A Power Platform environment with Dataverse and Power Pages capacity, which Microsoft meters by authenticated users per month. We quote it alongside our fee so you see the all-in cost.
Is there a per-user fee?
Not from us. Our fee is flat whatever the size of your network. Microsoft's Power Pages capacity is priced per active user, and we always show it in the quote.
Can we brand it?
Yes. Logo, colours and fonts are configuration, and several sites or brands can run from the same solution.
Do we need developers to run it?
No. Content, pages, branding, entitlements and settings are managed from the portal and from configuration. Your Power Platform team can extend it if they want to.
Can different companies see different things?
Yes. Modules can be switched on per company, news and documents can be targeted to one company, and a lighter tier gives others a trimmed home page with selected announcements.
How do submissions reach our teams?
Claims, service requests and support tickets are Dataverse records. Your staff work on them in Dynamics 365 or a model-driven app, and Power Automate can drive any workflow you need.
Is it a partner relationship management (PRM) system?
No. It is a service and communications portal: news, events, documents, claims, requests and support. It does not do deal registration, marketing funds or lead distribution.
How are upgrades delivered?
As managed solution updates. Upgrades are additive and never require you to reconfigure your portal.
What languages does it support?
The interface is in English. The content you publish can be in any language.
If your partners already live in your Dynamics 365, their portal should too.
See it working with our demo tenant, then talk through your network, your modules and an all-in quote.