Single sign on and identity
One sign in that works with the identity provider you already use, plus invitation flows, self-registration with approval, multi-factor authentication and clean session handling for shared or public computers.
Solutions · Web Portals
Web portals for clients, members, staff and partners
One secure place where the people outside your organisation can sign in, find their documents, submit forms, track approvals and pay. Built on top of the systems of record you already run, so nobody has to rekey anything.
You own the code and IP Weekly demos Reply within one business day
Portal
Members
Directory
Documents
Roles
Audit log
Search members, roles or centres
Single sign-on
MemberRoleLive
Admin
Member
Board
Member
1,284
Members
99.9%
Uptime
0
Access issues
Web Portals, in short
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds secure web portals for clients, members, staff, dealers and citizens.A portal gives each audience its own signed-in view: documents, forms, approvals, notifications, payments and a full record of who did what. We connect the portal to your existing systems of record rather than replacing them, and roll it out in phases so one audience is live before the next begins. Where an off the shelf product already covers what you need, we will say so.
Key facts
- 01Service
- Secure web portal design, build and integration
- 02Typical audiences
- Clients, members, staff, dealers, franchisees, citizens
- 03Sign in
- Single sign on, multi-factor, invitation and self-registration flows
- 04Core modules
- Documents, forms, approvals, notifications, payments, reporting
- 05Accessibility
- WCAG 2.2 AA, with EN and FR where you need it
- 06Based in
- Vancouver, British Columbia, serving clients remotely across Canada
The short answer
What we build into a portal
Roles and permissions
Permissions modelled on how your organisation actually works: role, organisation, region, dealer or file. People see everything they are entitled to and nothing more, and an administrator can change who sees what without a code release.
Document exchange
A shared place for statements, contracts, drawings, claims and reports, with versioning, expiry dates, virus scanning on upload and a record of every download. No more chasing attachments through email threads.
Forms, workflow and approvals
Multi-step forms that save drafts, validate as people type and route to the right approver. Conditional logic, delegation while someone is away, reminders when a step stalls and a clear status the submitter can see at any time.
Payments and account history
Invoices, balances, receipts and online payment through a payment provider whose account you hold. We keep card data out of your systems by using the provider's hosted fields, and reconcile activity back to your finance system.
Audit trails and dashboards
Every sign in, view, upload, approval and change recorded with who, what and when, plus dashboards and exports for the people who need the numbers. Retention rules keep the log useful rather than endless.
Process
How an engagement runs
Discovery and audience mapping
We list every audience, what each one needs to do, and what they do today instead. That usually surfaces the email threads, spreadsheets and phone calls the portal is meant to replace.
Architecture and the build versus configure call
We map the systems of record, the integration points and the identity model, then make an honest recommendation on building, configuring a product, or combining the two.
Design and first working demo
Screens for the first audience, tested with people who resemble your real users. You get a working demo every week from here on, not a status report.
Phased build
One audience and one workflow at a time, each phase released to a small group before it opens to everyone. Security review and accessibility checks run inside each phase.
Launch, measure and improve
Onboarding material, support handover and a dashboard showing adoption and where people get stuck, so the next phase is based on what actually happens.
How we work
How we approach a portal build
01
Build or configure, decided early
The first question is whether you should build at all. If your need is a standard one, a mature product for membership management, ticketing or client accounting will get you there faster. We build when the workflow is specific to your organisation, when several systems have to meet in one place, or when the product on the table needs so much configuration that it stops being off the shelf. We will tell you which case you are in before anyone writes code.
02
Treat the portal as a front door
Your CRM, ERP, finance system, document store or case management tool stays the source of truth. The portal reads from it and writes back to it, so staff keep working in the tools they know and nobody maintains two versions of the same record. Where an API does not exist, we use scheduled or event driven syncs and make the failure cases visible.
03
Phase the rollout by audience
One audience and one workflow go live first, for example clients viewing documents. Once that is steady, we add forms, approvals, payments and the next audience. Phasing keeps training manageable, gives you something real to react to, and means a delay in one area does not hold up the rest.
04
Security and privacy from the first sprint
Least privilege by default, encryption in transit and at rest, multi-factor authentication, logging of every meaningful action and clear separation between environments. Where data residency or privacy obligations apply, we design to the requirements you and your counsel set. This is engineering, not legal advice.
05
Accessible, bilingual and usable on a phone
We build to WCAG 2.2 AA, keep the first screen short, write instructions in plain language and test on real devices. Bilingual EN and FR is available where your audience or your obligations call for it. A portal only saves your team time if the people outside can actually use it without calling you.
06
Handover you own outright
You own all code, designs, accounts and intellectual property. Repositories, environments, documentation, runbooks and credentials come to you at the end of the engagement, and we are glad to work alongside your internal team or another vendor afterwards.
Who it's for
Web Portals for organisations that have to get it right.
Corporations
Client and supplier portals that sit in front of an ERP or CRM, with roles that match your org chart, approval chains your finance team recognises and audit trails your risk group can read.
Associations and government
Member and citizen portals for renewals, credentials, document requests, public forms and approvals, built to WCAG 2.2 AA and available in EN and FR where that matters.
Franchises
Dealer and franchisee portals for orders, marketing assets, training, compliance sign offs and territory reporting, with head office visibility across every location in one view.
Entrepreneurs and startups
A first portal scoped to the one workflow that proves the model, built so it can grow with your customers rather than be rewritten the moment they arrive.
00
Portals launched
00
Systems of record integrated
00
Audiences served in one portal
FAQ
Web Portals — questions we hear first.
Sometimes buying wins. If the requirement is standard, a mature product for membership, ticketing or client accounting will cover it faster than anything custom. We build when the workflow is specific to your organisation, when several systems have to meet in one place, or when the product needs so much configuration that it stops being off the shelf anyway.
Through APIs where they exist, and scheduled or event driven syncs where they do not. The portal is usually a front door rather than a new source of truth: your CRM, finance system, document store or line of business application stays authoritative, and the portal reads and writes to it so nobody rekeys data.
That depends on how much goes into the first release. We aim to get one audience and one workflow live early, for example clients viewing their documents, then add forms, approvals and payments in later phases. You see a working demo every week from the start, so progress is visible rather than reported.
No. Some portals use email and password with multi-factor authentication, others connect to an identity provider your staff already sign in to. Single sign on is worth it when users are internal or already hold accounts elsewhere. For external audiences we usually offer both, with an invitation flow you control.
Least privilege by default, encryption in transit and at rest, multi-factor authentication, logging of every meaningful action and separation between environments. Canadian organisations often ask about data residency and about PIPEDA or provincial privacy law: we design to the requirements you and your counsel set. This page is not legal advice.
Yes, if the portal is designed for them. We build to WCAG 2.2 AA, keep the first screen short, write instructions in plain language, make it work properly on a phone and offer EN and FR where you need it. We also plan for the person who forgets their password at eight in the morning.
You do. Clients own all code, designs, accounts and intellectual property, and the data stays yours throughout. We hand over repositories, environments, documentation and credentials at the end of the engagement, and we are happy to work alongside your internal team or another vendor after launch.
Let’s connect
Let’s scope your web portals project.
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.