Client & Employee Portals
One secure place instead of a hundred emails. Customers see their orders, documents, contracts and tickets; employees find procedures, forms and training. With roles, single sign-on and an audit trail, so the right people see the right things and you can prove it.
What you get
- Secure login with single sign-on options: Microsoft 365, Google Workspace, or your own directory
- Roles and permissions down to the document, with an audit trail of who saw and changed what
- Modules that fit the portal's purpose: documents, orders, invoices, tickets, forms, training, news, downloads
- Notifications by email, and in-app, with digests instead of noise
- Connections to the systems that hold the data today: ERP, CRM, document management, ticketing
- Branding, so the portal looks like part of your company rather than a tool you bought
Customer portals
Where customers ask the same questions by phone and email, a portal answers them at any hour: order status, invoices, contracts, certificates, spare parts, service requests. Every request that arrives through the portal is complete and traceable, and every answer is a page your team does not have to write again.
Employee portals and intranets
Procedures, forms, onboarding, training records, internal news, and the tools people actually use, behind one login that works on their phone. We build intranets on our page platform where content matters most, and as applications where workflows matter most, often combined.
Questions we hear often
Can the portal use our existing user accounts?
Yes. Single sign-on with Microsoft Entra ID, Google or any SAML or OpenID Connect provider means no extra passwords and offboarding in one place.
How is data protected?
Encrypted in transit and at rest, EU hosting, role-based access, audit logs, regular backups, and a data protection documentation set you can hand to your DPO. Penetration testing on request.
How long does a portal take?
A first useful version, with login, one or two modules and one integration, in eight to twelve weeks. Further modules follow in cycles.
Guides on this topic
Why B2B customers order by email when you have built them a shop
Find out why B2B customers order by email, sort a month of order emails by reason, and decide which features your shop needs and what stays personal.
AI assistants and document permissions: who may get the answer?
How to design an internal AI assistant that respects document permissions: checks at retrieval time, permission sync, caches, revocation and leak tests.
Caching customer-specific prices: when a fast site shows the wrong price
How page caching can show customer-specific prices to the wrong person, which HTTP headers prevent it, and how to test it with two customer accounts.
Fewer emails, happier customers?
A person answers within one working day. No obligation.