Customer & partner portals.
A clear next step.
A shared view of progress.
Give customers and partners a secure place to act, exchange information and see progress. Connect their next step to the team doing the work behind it.
Site instructions
Draft savedSite instructions, documents and updates in one place.
Build around what
people need to do.
A useful portal goes beyond a login screen. We design the tasks, permissions and connections around the service you deliver.
Explore the customer operations problem ↗Access that belongs to an account
Invitations, organisation membership and recovery.
A clear action, wherever they work
Saved tasks, evidence exchange and mobile journeys.
Progress people can trust
Receipt, review and completion with a named owner.
- Record
- ACT-204
- Update
- Approved site pack
- Receipt
- Accepted by destination
A portal connected to delivery
Approved updates with a receipt from your systems.
A common record.
Different responsibilities.
A precise view.
access for ACT-204.
The portal is part
of your operation.
Start with the signed-in person. Identity alone does not grant record access.
Who is this?
Sign-in, membership and session controls.
What may they do?
Account isolation, tasks and server-side permission checks.
Was it accepted?
Authoritative case status and an acknowledged update.
The source and permitted change are saved before delivery.
The destination timed out. The user can see the delay; the update stays available for recovery.
ACT-204 → no receipt · retryableTest the boundaries
Enforce organisation and role permissions on the server. Test record and file access across accounts, including direct links.
Fit the existing estate
Check existing identity, CRM and case-system APIs, licensing and data quality. Agree record ownership and maintenance costs.
Support real users
Test mobile, keyboard and assisted journeys with the people using them.
Technology for your portal.
Connected to your operation.
Use your identity provider and business platforms where they fit. We agree account models, API access, hosting, accessibility and support costs before selecting the stack.
Build the portal around your users, access model and operating environment.
Portal interfaces
React
Next.js
TypeScript
Application services
Node.js
Python
.NET
Customer & partner identity
Auth0
Keycloak
Amazon Cognito
Google Cloud Identity Platform
Microsoft Entra External ID
Business records
PostgreSQL
MySQL
SQL Server
Files & documents
- Amazon S3
- Google Cloud Storage
Azure Blob Storage
Hosting & delivery
- AWS
- Google Cloud
- Microsoft Azure
Docker
GitHub Actions
Bring customer records, operational work and support into one controlled experience.
Customer & partner records
Salesforce
HubSpot
Zoho CRM- Microsoft Dynamics 365 Sales
Orders & operations
Oracle NetSuite
Odoo
SAP S/4HANA- Microsoft Dynamics 365 Business Central
Cases & support
ZendeskFreshdesk
ServiceNow
Jira Service Management
Documents & collaboration
- Microsoft 365
Google Workspace
Existing workflows
Custom applications- Existing APIs
Build on a packaged portal platform where its capabilities and your existing systems fit.
Packaged portal platforms
- Salesforce Experience Cloud
Microsoft Power PagesLiferay DXP
One submission.
Every handoff visible.
- Customer prepares
- Your team reviews
- Partner receives
Ready for the site visit?
Check the site details, then submit the pack.
Access instructions · v1
Site visit access pack.
View site details
- Arrival
- East reception · Building A
- Contact
- Site operations team
- Access
- Weekdays · 09:00–16:00
Report to east reception. An escort is required for Building A. The escort meeting point still needs confirmation.
Awaiting release.
Site instructions are not available to the partner until your team accepts the pack.
Not shared with partner
View the sample decision history (1)
Original v1: report to east reception; escort required for Building A; escort meeting point unconfirmed.
- Draft saved in the customer workspace.
Demo using sample data. No uploads, notifications or system changes are made.
Observe one real journey and its handoffs.
Agree roles, fields and account boundaries.
Deliver one complete path through the systems.
Test permissions, failures and real user tasks.
Assign support, recovery and access ownership.
A first release
with clear boundaries.
- Your team brings
- A process owner, user representatives, current forms, access policies and system contacts.
- Revni delivers
- Agreed user journeys, portal screens, permission enforcement, integrations and operating guidance.
- We agree together
- Release scope, acceptance checks and migration. Match existing accounts and records, assess a phased transition, and assign hosting, monitoring, access administration and support.
Prove the access model.
| Check | Expected result |
|---|---|
| Another customer opens the record | Access denied |
| Assigned partner opens the task | Approved site details only |
| Customer submits a site pack | Received, not approved |
| Case system is unavailable | Pending update retained |
Delivered with journey maps, representative test evidence and a support runbook.
Relevant industries.
Explore the operating context, information boundaries and journeys in your sector.
Connected thinking.
Follow the decisions further.
Give your users a clear next step.
Bring the process, the people involved and the systems they need to reach. We’ll define a useful first release.
Discuss your portal See how we workA useful first conversation.
You don’t need a finished brief. Bring the problem, the systems involved and what a better outcome would look like.