Customer Portals

Microsoft Dynamics CRM Customer Portal
with the documents, not just the records.

Their opportunities, quotes and orders, and the documents attached to each one, on a login you own. It reads live from Microsoft Dynamics CRM, and from SharePoint where the files usually sit rather than in Dynamics itself.

Dataverse and SharePoint are two different problems and a portal usually has both. Fixed-price scope, an Australian team, and support after it goes live.

Covers Dynamics 365 Sales, Dynamics 365 Customer Service and Dynamics CRM on-premise.

  • No per-user fee Portal logins do not cost Microsoft Dynamics CRM seats
  • 18+ yrs Building business software
  • Fixed Price scopes, no surprises
  • You own it Code, docs and credentials
Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.

What your customers see

What your customers see in a Microsoft Dynamics CRM portal

Every screen reads live from Microsoft Dynamics CRM, so the figures match because they come from Microsoft Dynamics CRM rather than from a copy somebody refreshes.

  • Their opportunities, quotes and orders
  • Cases, updates and resolutions
  • Documents, including those held in SharePoint
  • Forms writing back to the correct Dataverse table
  • Account and contact details they maintain

Who logs in

  • Customers
  • Partners
  • Suppliers

Editions covered

  • Dynamics 365 Sales
  • Dynamics 365 Customer Service
  • Dynamics CRM on-premise

What people ask us for

Start with the job your Microsoft Dynamics CRM portal has to do

The same portal gets asked for in six different ways depending on where you are up to. Select any one to read how we approach it.

Microsoft Dynamics CRM customer portals

Microsoft Dynamics customer portal and client portal

A customer portal for Microsoft Dynamics is a login you own, on your domain, where your customers see their own account. A client portal for Microsoft Dynamics is the same build under the name professional services tend to use. Either way it is not the Microsoft Dynamics login: your customers never get access to Microsoft Dynamics, and you do not buy them a seat.

The portal reads live from Microsoft Dynamics through the API, so what a customer sees is what Microsoft Dynamics says right now rather than a figure somebody exported on Friday. A Microsoft Dynamics customer self-service portal removes the calls asking where things are up to.

Microsoft Dynamics CRM customer portals

Microsoft Dynamics customer portal development

We are a Microsoft Dynamics customer portal development company, and this is custom work rather than a product with your logo on it. Microsoft Dynamics portal development starts with what your customers should see and what they should be able to do, because that decides everything after it.

A custom Microsoft Dynamics customer portal is worth building when an off-the-shelf tool cannot model how you actually work: partner hierarchies, multi-contact accounts, or approval steps that would need heavy Dataverse configuration. Where a product would genuinely do the job we will say so rather than quote.

Microsoft Dynamics CRM customer portals

Build a Microsoft Dynamics customer portal, or a customer app

Some clients want a portal on the web, others want a Microsoft Dynamics customer app their customers keep on a phone. The data layer is the same; the difference is how it is delivered and what it costs to maintain, and it is worth deciding deliberately rather than by default.

Either way it is a Microsoft Dynamics customer portal solution scoped and fixed-price before anything is built, running in parallel with how you work now until you agree it is right.

Microsoft Dynamics CRM customer portals

Microsoft Dynamics customer portal integration

Microsoft Dynamics portal integration is the part most projects underestimate. Connecting a customer portal to Microsoft Dynamics means deciding which system is authoritative for each field, how a portal login maps to exactly one Microsoft Dynamics record, and what happens when two things change at once.

Dynamics stores its data in Dataverse, and documents are frequently in SharePoint rather than in Dynamics at all. A portal that shows a case but cannot show the attachment on it is half a portal, so where the documents actually live is settled early. Older on-premise CRM installs are a different integration path again.

If you already have a portal or a website, we integrate the customer portal with Microsoft Dynamics rather than starting again. If you have neither, we build both.

Microsoft Dynamics CRM customer portals

Invoice, payment and account portals

Most Microsoft Dynamics portals start as a Microsoft Dynamics account and case portal: their opportunities, quotes and orders. From there it usually grows into cases, updates and the documents behind them.

A Microsoft Dynamics customer account portal and a Microsoft Dynamics customer billing portal are the same build seen from different angles. The work is making sure anything done in the portal lands against the right record, first time, without anybody reconciling it by hand.

Microsoft Dynamics CRM customer portals

Orders, quotes, documents and dashboards

Documents are frequently in SharePoint rather than Dynamics, so a portal that shows a case but not its attachment is only half built. A Microsoft Dynamics customer order portal, a Microsoft Dynamics quote portal for approvals and a Microsoft Dynamics customer document portal are all the same portal with more of the account exposed. A Microsoft Dynamics client dashboard on the front page answers the question before they go looking.

What Microsoft Dynamics does not hold, we fetch from wherever it does live. That is usually the job system, the CRM or a database, and joining those is the same work as any other integration.

One place, one view

Your customers should not need three logins

Microsoft Dynamics CRM holds part of the picture. The rest is in the job system, the CRM, the payment gateway and wherever your documents live. A portal that only reads Microsoft Dynamics CRM hands your customer a fragment and sends them back to the phone for the rest.

We join them. One login, designed to your brand, showing a complete account view built from every system that has a piece of it.

  • SharePoint, where the documents usually actually live
  • Your accounting system, so invoices and payments sit beside the account
  • Your delivery or job system, for what happens after the sale
  • Payment gateways, so paying in the portal reconciles correctly
  • Your website or app, so the login is part of your brand rather than beside it

How it works now

Every question lands on your desk

  • Customers ring or email to ask the same questions
  • Somebody exports from Microsoft Dynamics CRM and sends it out
  • Chasing takes a person the best part of a day a week
  • No record of who was told what, or when

After

Customers look it up, straight from Microsoft Dynamics CRM

  • Available any time, straight from Microsoft Dynamics CRM
  • Nothing rekeyed, because it is read rather than copied
  • Anything they submit posted back where you want it
  • An audit trail of who saw what and when

Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.

Get a fixed-price scope
Common questions

Questions owners ask about a Microsoft Dynamics CRM portal

Is this the Microsoft Dynamics CRM login?

No. The Microsoft Dynamics CRM login is where you and your staff work. This is a separate portal you own, for your customers, that reads and writes your Microsoft Dynamics CRM data. Your customers never get access to Microsoft Dynamics CRM itself.

What can customers actually see?

Typically their opportunities, quotes and orders, cases, updates and resolutions, documents, including those held in sharepoint. What they cannot see is anything else, because the portal only ever requests the records belonging to that contact.

What is the hardest part of Microsoft Dynamics CRM portal work?

Dynamics stores its data in Dataverse, and documents are frequently in SharePoint rather than in Dynamics at all. A portal that shows a case but cannot show the attachment on it is half a portal, so where the documents actually live is settled early. Older on-premise CRM installs are a different integration path again.

Do we need a licence for every portal user?

No. The portal reads through the API under one connection, so the number of customers logging in does not change what you pay Microsoft Dynamics CRM. That is usually the reason a custom portal costs less than the alternative once you have more than a handful of users.

Will it slow Microsoft Dynamics CRM down or put our data at risk?

The portal reads through the API rather than touching your system directly, so day-to-day use is unaffected. Writes are limited to what you approve, and everything is logged so you can see what changed and when.

How long does it take?

A straightforward portal over Microsoft Dynamics CRM is usually weeks rather than months. We scope it and quote fixed-price before starting.

Tell us what your customers keep ringing about

Which Microsoft Dynamics CRM edition you are on, roughly how many customers would use it, and what they most often ring about. We will come back with a straight answer and a fixed-price scope.

Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.