Define each tenant’s scope
Package capabilities through controlled module entitlements.
WHY IT MATTERS
Onboarding is more than provisioning.
Gate production access
Treat activation as a review decision, not only a setting.
Separate credentials
Keep institutional configuration and credential boundaries explicit.
THE OPERATING MODEL
What happens, and in what order.
Provision
Establish the institution’s tenant context.
Entitle
Configure the permitted modules and scope.
Review
Evaluate readiness for production activation.
Operate
Maintain venues, reference data and credential isolation.
MAKE THE EVALUATION CONCRETE
Ask to see it.
Use these demonstrations to test the fit with your institution. Capability descriptions are a starting point, not independent assurance.
- Provision a tenant without granting production access.
- Change one module entitlement and inspect its effect.
- Review credential isolation across institutional contexts.
QUESTIONS, ANSWERED
The questions that matter.
Bring the next question to a focused product and architecture conversation.
Does creating a tenant enable production?
No. The inventory treats production activation as a separate review gate.
Can institutions have different capability packages?
Yes. Module entitlements and configuration support differentiated scope.
Is tenant isolation independently certified?
No certification is implied. Review implementation and available assurance through the security evaluation.
CONNECTED CAPABILITIES
Continue the evaluation.
START WITH YOUR REQUIREMENTS
Bring your operating model.
Let’s map the fit.
Discuss the client journey, enabled scope and institutional controls that matter to your team.