What Digital Office Premium includes
- Premium website, business email, SEO and GEO.
- Secure client portal with individual accounts and document sharing.
- Employee portal for internal documents, forms and announcements.
- OCR and PDF processing, and automated document generation from templates.
- Custom iOS and Android apps on request, quoted separately.
Designing access across offices
The key question in a multi-office portal is who sees what. A typical model gives each client account access only to its own documents, gives staff access by office or team, and gives group functions such as finance or compliance a wider view. Agree this model before anything is built, because it shapes the account structure, folder layout and notifications.
| Role | Typical access | Example |
|---|---|---|
| Client user | Own documents and messages only | A client downloads signed reports and uploads requested files |
| Office staff | Clients assigned to their office | A team in one country manages its local client files |
| Group function | Read access across offices | Finance checks invoices issued by every entity |
| Administrator | Accounts, permissions, settings | An operations lead adds new starters and removes leavers |
How a platform project runs
- You describe your offices, users and documents, and the processes the portal should support.
- We agree the access model, document types and any integrations in a written scope.
- We configure accounts, folders, templates and notifications.
- Pilot with one office before rolling out to the others.
- Train administrators, then hand over with documentation.
Custom platforms and apps
Some organisations need more than a portal: a booking engine shared across offices, a field app for site visits, or a dashboard drawing on several systems. These are scoped and quoted in writing with no public price. Connecting a platform to existing CRM and accounting tools is covered in our guide to website and system integrations, and the automation side in AI and workflow automation.
Security basics we build in
- Individual accounts for every user, never shared logins per office.
- Permissions assigned by role, so access follows the job rather than the person.
- A simple process for removing access when staff leave or a client relationship ends.
- HTTPS throughout and documents shared inside the portal rather than as email attachments.
Limits
A portal is only as good as the process behind it. If offices currently work in very different ways, part of the project is agreeing a common approach. We do not migrate unlimited historical archives by default; the scope says what moves.
Common questions
Can each office have its own branding in the portal?
The portal follows the group design, and office or entity names can appear where relevant. Fully separate branding per office is possible as a custom option and would be included in the written scope.
Can we start with one office?
Yes, and we recommend it. Piloting with one office reveals gaps in the access model and document structure before other offices join.
Are mobile apps included?
Custom iOS and Android apps are available on request and quoted separately. Many organisations find a mobile-friendly portal is enough to begin with.