Account and project workspaces
A clear home for the records, milestones and updates relevant to each customer or partner. Navigation reflects their responsibilities, with boundaries between organisations, projects and roles.
External workspaces / Shared context
Kerning / IntelligenceClient and partner portal development
Give clients and partners a useful place to work with your business. We design portals around the information they need, the actions they can take and the internal teams responsible for responding.
Shared work needs more than a shared folder.
Project updates, drawing versions, approvals and support requests often travel through different channels. A client can see a file without knowing whether it is current, while the internal team has to piece together what was requested and who should respond.
A portal creates a defined interface between your organisation and the people outside it. The starting point is the relationship: what each party owns, what they can see and which actions need to flow back into the business.
01Scope / Shaped around your process
What we can build.
Documents and review steps
Structured document access with version context and the review or approval actions your process requires. We define what an approval means, who can give it and how the decision is recorded.
Requests and service workflows
Forms and request journeys that collect useful information at the start. Routing, status updates and internal ownership connect the external request to the team expected to act on it.
Access and administration
Invitation, sign-in and membership workflows, together with permissions, account administration and relevant activity records. The design includes what happens when people change roles or leave a relationship.
02Delivery / From context to working software
How the work takes shape.
Define the shared boundary
Map the information that may be shared and the actions each audience needs. Agree organisation-level separation, document access and approval responsibilities before designing the customer-facing screens.
Join the internal process
Identify the project, CRM, document or support system that owns each record. Plan how updates move between systems and how the portal communicates unavailable data or failed requests.
Validate both sides of the journey
Test with representative external users and the internal team receiving their work. Include invitations, expired access, missing documents and exceptional cases, then prepare administration and handover guidance.
Context / Relevant work
A partner workspace around project delivery.
Hemco Partner Hub brings project information, drawings, equipment, deliveries and support into a shared partner workspace. Cronuss Consultants provides another project context: a client-response portal with structured questionnaires and an administrative workspace.
Cronuss Consultants is an application in development. The Hemco example covers partner project coordination and support.
03Before you begin
Useful questions.
Can clients and partners use the same platform?
They can share technical foundations while having different permissions, records and journeys. We define the separation around your relationships and test those boundaries rather than assuming every external user needs the same workspace.
Can the portal connect to our existing project system?
That depends on its supported interfaces and the access available. We review those first, then define which records appear in the portal, whether users can change them and how updates return to the source system.
How are sensitive documents handled?
Document handling is designed around the agreed access, storage and retention requirements. Scope can include authenticated access, permission checks and activity records. Specific hosting or contractual requirements need to be established during discovery.
Could we start with a smaller portal?
Yes. A first release might focus on one relationship or journey, such as project visibility or structured requests. It should still include the access and administration foundations needed to operate that journey responsibly.
Next / Your first conversation
Make the next handoff clearer.
Bring an example of the documents, questions and decisions your clients or partners exchange with you. Together, we can define a workspace that supports that relationship.
Discuss your portal