Customer portal — module in Consitus Intranet
A customer portal built on Consitus Intranet
We build the customer portal as a module in Consitus Intranet. Customers see cases, documents and status, while your staff work in the same platform — and the information only exists in one place.
- Consitus Intranet
- Login and roles
- Documents
- Custom development
Features
What the portal module typically needs to do
The features below are the most requested and are built on the platform's data and roles. What gets built for you depends on what your customers most often get in touch about.
Login and role-based access
Each customer sees only their own information. Internal users get access by role via the intranet's permission system.
Documents and files
Contracts, reports, drawings and attachments from the intranet's document module — with version control and clear ownership.
Cases and status
Customers can follow a case from creation to completion, see who is responsible, and what's outstanding.
Orders, agreements and history
An overview of what's been purchased, delivered and agreed, so questions about history don't need a staff member.
Same data as internally
The portal shows data from Consitus Intranet, so information doesn't need to be maintained in one more place.
Genuine custom development
If your workflow is unique, the feature is built as a module on the platform — not squeezed into a standard package.
Typical uses
Where a portal makes the biggest difference
The portal pays for itself when it removes repeated enquiries or manual extracts.
- Customers who often ask about case status
- Documents currently sent as email attachments
- Reports produced manually for each customer
- Service cases, repairs and warranties
- Partners who need to see selected data
- Self-service instead of phone calls during office hours
Approach and scope
From platform to portal in daily use
Consitus Intranet is always the foundation. We start with the data in the platform the portal should show, and who is allowed to see what, then build in short iterations. We don't build the portal into your existing systems.
- Mapping data, roles and access in the intranet
- Defining what customers are allowed to see
- First version with the most requested feature
- Expansion with further modules based on actual use
Start with the foundation: see how Consitus Intranet is built.
FAQ
Questions about the customer portal
- What is a customer portal from Consitus?
- It's a portal module in Consitus Intranet: a private area where your customers log in and find cases, documents, agreements, status and history themselves. Data comes from the intranet where your staff work — customers only see what the portal is configured to show them.
- Can the portal pull data from our current systems?
- No. We don't build on top of customers' existing systems, and we don't offer general system integration into other platforms. The portal displays data from Consitus Intranet. If information from other sources is needed, we agree a defined and controlled data exchange into the platform.
- How is access controlled?
- Through the intranet's roles and permissions. A customer's user only sees their own data, while your staff have access based on role. Permissions are part of the platform's data model — not a layer bolted on afterwards.
- Can we start small?
- Yes, and we recommend it. The foundation is already in place in Consitus Intranet, so we can start with the single thing customers ask for most and expand the portal module based on actual use rather than a long wish list.
Related pages
Related reading
Contact
Should your customers be able to help themselves?
Write a few lines about what you would like to work better. We will come back with an honest view of what can be done.