Your data, in your tenant, under your own agreement
From where the membership data sits to how access is controlled and what connects to what — how MemEx is built, and which parts of it you own outright.
Frequently asked
MemEx runs on Microsoft Dataverse inside each customer’s own Microsoft tenant. Member data never leaves that tenant — a Wattle engineer has to be invited in to work in it, the same as any other administrator.
Four components
One interface between them.
MemEx CRM is a managed Power Apps solution deployed into your Dynamics 365 environment. MemEx Web runs on your own Umbraco. MemEx Member Portal is a multi-tenant application hosted by Wattle. MemEx API sits between them.
Your Dynamics 365 environment, your Microsoft tenant, your licences. A managed solution with an ALM pipeline.
Your Umbraco instance, your hosting or ours, your content database.
Wattle-managed service. Member data remains in your CRM; the portal holds no second copy of your membership.
Wattle-managed, brokering access between the above. The only component that talks to Dataverse.
In your tenant, under your agreement
What you own.
Membership data
Website content
Microsoft licences
The Member Portal
Membership data
Sits in Dataverse, in your own Microsoft tenant, under your own Microsoft agreement and licences.
Website content
In your own Umbraco database. Your editors, your CMS, your hosting.
Microsoft licences
Held directly with Microsoft — not resold through us. That means the platform underneath MemEx is one your IT function already recognises, already governs, and could already get support for elsewhere.
The Member Portal
Runs as a managed service on our platform, and holds no second copy of your membership: it reads and writes to your CRM.
Identity, permissions and audit
Authentication and audit.
Azure AD B2C for members and staff, one directory per tenant. Sign-in, password reset and MFA are configured per organisation.
Role-based access control, with CRM-side plugins keeping the B2C identity and its security roles in step with the contact record.
Third-party credentials and per-tenant configuration are encrypted at rest.
Platform activity is recorded. Dataverse carries its own audit history on membership records.
Customisation
How much you customise is your choice.
Deep customisation of the membership model is possible, and it trades against how quickly you take platform improvements. We tell you which side of that line a request falls on during scoping, so the decision is yours to make with the trade-off in front of you.
Put your IT function in front of this.
We will take them through the architecture, the boundaries and the audit trail.