Skip to main content

Secure Partner Portal

An authenticated self-service portal where partners submit and track requests directly against the system of record, removing a manual re-keying step from every submission.

Client
Membership and partner organisation
Industry
Membership services

Note. Portfolio concepts shown here are anonymised and representative of the kinds of intelligent business systems Aqlyst delivers. Client names, screenshots, and measured results are published only with written approval.

The situation

  • Submissions arriving as email

    External partners sent forms and documents by email, which staff then re-entered into the internal system by hand, introducing delay and transcription errors.

  • No visibility for the submitter

    Partners had no way to check status, so a steady volume of progress-chasing calls landed on the same small team.

  • Access control by spreadsheet

    Who could see what was tracked informally, which made onboarding and offboarding slow and difficult to audit.

How we worked

  1. Design the access model firstRoles, record-level permissions, and the external identity model were agreed before any page was built, because retrofitting access control into a live portal is expensive.
  2. Submit straight into the system of recordForms write directly to Dataverse with validation at the point of entry, so a submission becomes a record rather than an attachment to process.
  3. Accessibility as a build constraintKeyboard operation, contrast, form semantics, and error messaging were part of the component work rather than a pre-launch audit.
  4. Status visible to the submitterPartners see current status and required next actions, which removed the reason for most chasing contact.

How the system fits together

External identity and role-based access in front of Dataverse, with automation handling routing and notification between partner and internal teams.

  1. External

    • Power Pages portal
    • Partner dashboard
    • Document upload
  2. Identity

    • Microsoft Entra External ID
    • Role assignment
    • Access review
  3. Data

    • Dataverse
    • Validation rules
    • Record-level security
  4. Automation

    • Power Automate routing
    • Notifications
    • Status updates
  5. Internal

    • Model-driven app
    • Queues
    • Microsoft 365

What was built

  • Authenticated self-service portalSecure sign-in, role-based access, and a partner dashboard for submissions in progress.
  • Validated structured submissionsForms with server-side validation writing directly to Dataverse, with document handling attached to the record.
  • Automated routing and notificationPower Automate routes each submission to the right internal queue and notifies both sides on status change.
  • Auditable access managementRole assignment through the identity platform with a clear onboarding and offboarding path.

What changed

Figures are published only once the client has approved them. Where a value reads “Illustrative”, the improvement is real but the number has not been cleared for publication.

Manual re-entry of partner submissions
Not yet approved for publication
Status-chasing contact volume
Not yet approved for publication
Accessibility target
WCAG 2.2 AA implementation target

Technology stack

  • Power Pages
  • Dataverse
  • Power Automate
  • Microsoft Entra ID
  • Azure
  • Digital Experience

    Business websites, customer and employee portals, and design systems built for performance, accessibility, and conversion.

  • Power Platform

    Business applications and automation built with architecture, security, reusable components, and a disciplined delivery lifecycle.

Let's talk

Working on something similar?

Bring the problem as it actually is, including the parts that are messy. That is usually the fastest route to a useful first conversation.

Prefer email? info@aqlyst.ai