Customer & employee portals
Put information and tasks where people need them.
A portal gives customers or employees appropriate access to documents, activities and tasks. I develop protected web applications that support your existing workflows and connect relevant information.
Discuss your project Explore the focus areasWhen collaboration depends on the inbox.
- Customers regularly ask for order updates or documents.
- Internal requests and approvals are lost in long email threads.
- Different groups need access to specific information.
Possible applications
Access that makes collaboration easier.
Customers and employees need access to different information and tasks. I plan navigation, content and permissions for each group.
Customer portals
Bring order status, documents and messages together in a personal area. Customer-service and ticket portals let customers submit requests and track progress, while responsible staff keep track of follow-up questions and next steps.
Employee portals
Bring onboarding, internal requests, absence management and approvals together. Roles determine who can view information, make changes or approve decisions.
Further portal uses
Manage memberships and training, or organise applications and interviews. Integrations bring the required data together; approvals and hiring decisions remain with the responsible people.
Concept example
The right draft. Feedback linked directly to it.
A printing business currently reviews brochures by email. It is not always clear which file a comment refers to. In the customer portal, the current draft is attached to the order. The customer can request changes or approve that version for printing. The printer sees which version was approved and what remains to be done.
- 01
Share the draft
The printer uploads the current brochure version to the order’s customer area.
- 02
Link the feedback
The customer requests changes or approves that exact version for printing.
- 03
See the next step
The responsible person sees feedback and approval status against the order and can plan the next action.
Working together
Build a portal around your collaboration.
We plan the portal around the tasks of your customers or employees. Features, design and access rights are agreed together. Introduction and any ongoing support are planned early on.
- 01
Clarify tasks
We discuss who will use the portal and which information or tasks they need. Recurring questions and existing systems provide the starting point.
- 02
Agree structure and access
I plan pages, usability and sign-in. We decide who may view or edit each type of data and review the design against your needs.
- 03
Develop and test
I develop the agreed features and integrations. Access rights and typical workflows are tested, and we review progress as agreed.
- 04
Prepare for use
At launch, I complete the agreed access, handover and guidance steps. User administration, content maintenance and technical support responsibilities are defined during planning.
Good to know
Common questions
Access, existing systems and mobile use: key questions before getting started.
What determines the scope?
A useful project scope starts with your workflows, existing data and the first result you want to achieve.
- User groups and permissions
- Tasks and approval workflows
- Documents and data sources
- Sign-in and existing identity management
- Notifications and integrations
Can the portal connect to our existing website?
Depending on the technology, it can be integrated or connected as a separate application. Design, sign-in and data access are coordinated.
Do all users see the same information?
No. Access follows agreed roles and assignments. Who can read or change each type of data is defined and tested during implementation.
Is a mobile app required?
Many portal tasks work well in a responsive web application. An additional app is planned only when the use case supports it.
How are documents and versions managed?
Depending on the agreed scope, files can be attached to orders, versions distinguished and feedback or approvals recorded. We agree access rights in advance. Special retention or archiving requirements are clarified separately before implementation. Operations and backups are agreed to suit the portal.
Your portal
Which recurring questions could a portal answer?
Describe who needs access and which information or tasks should be available. An initial idea is a useful starting point too.
Discuss your project