Employees and managers
Find current guidance, submit complete requests and see decisions without following a trail of emails and chat messages.
Give employees one place to find an answer, make a request and see what happens next. We build custom intranets on Microsoft 365 around your team's daily work.
Tell us what you need
A new colleague needs onboarding guidance. A manager needs to review an equipment request. An operations team needs to see what is waiting for a decision. The intranet should connect those tasks to the right information and owner.
We design the navigation around those journeys, then bring knowledge, forms and status views together. Company news can have its place without pushing daily work out of view.
The role matrix describes what each person can see and do. It becomes a practical checklist for design and testing, not just a document filed away before launch.
| Role | Typical access to agree and test |
|---|---|
| Employee | Read relevant guidance, submit requests and see their own status. |
| Manager | Review requests assigned to them and the team information they are permitted to see. |
| Content owner | Maintain assigned pages and documents, with publishing and review responsibilities. |
| Process owner | Monitor the relevant workload and handle exceptions within agreed access boundaries. |
| Administrator | Manage configuration and access with documented responsibilities. |
Sensitive records need their own access decisions. We test actual users and groups across content, workflow data and reports rather than relying on a hidden navigation link.
Start with an inventory of pages, files, forms, integrations and active requests. Keep the parts that serve people well; identify what needs cleanup, a replacement or an archive. Assign a source of truth to each process while both systems are in use.
Then pilot one employee journey, validate the migrated content and access, and agree on the rollout. Training, support and the point at which the old portal becomes read-only belong in the plan. A staged transition gives your team time to check the new way of working.
SharePoint and Microsoft 365 can provide the content and collaboration foundation. Power Apps and Power Automate can support request forms and approvals, with reporting built in Power BI and a scoped assistant built on Copilot Studio where it is useful.
We review your tenant, subscriptions and integration requirements before settling on the combination. The employee experience should feel like a complete task, even when several services sit behind it.
The VIPAR Heavy Duty portal brings role-specific information, a knowledge base and support workflows together. Our wine and spirits distribution system connects customer and internal tasks. These custom applications inform our approach to roles and workflows.
Find current guidance, submit complete requests and see decisions without following a trail of emails and chat messages.
Own the content and processes behind the portal, with access rules and publishing responsibilities that stay manageable as the business changes.
Navigation and task entry points for onboarding, policies, equipment requests and the workflows you choose for the first release.
A structure for searchable guidance, with named editors, review responsibilities and a clear home for the current version.
Forms, routing, decisions and status views, including rejected requests, missing information and absent approvers.
An access matrix, representative user tests, content migration decisions and a staged move from the existing portal.
Talk to employees and process owners, examine the current portal and agree on one useful journey from start to finish.
Senior engineers use AI-assisted delivery to target the first working release in 14 days. Pilot it with a small group, refine the journey and expand in agreed milestones.
Pricing: Fixed price per milestone, no hourly billing. About a third of a traditional team's quote for the same scope. Existing subscriptions and any additional licensing are reviewed before development.
It can include news, but our focus is the work employees need to complete: finding current guidance, making a request, reviewing a decision and seeing its status. We choose the first journeys with your team.
Yes. We inventory the content and workflows, then decide what to keep, connect, move or retire. The transition can happen in stages, with a defined owner for each process during the change.
We define a role matrix with your content and process owners, then test representative accounts. Employee, manager, editor and administrator access are considered separately, including sensitive records and reporting.
Your team receives the agreed documentation and training for content and workflow ownership. We define who manages publishing, permissions and support, and can agree on further development or maintenance separately.
Yes. A focused release lets employees use a complete workflow before it is rolled out more widely. We agree on the first department, acceptance criteria and how its feedback will inform the next milestone.
Choose the way you prefer to get in touch.
Pick a time for a 30-minute conversation. No need to fill out that form if you don’t want to :)
Book a 30-min callWrite to us directly at hello@devvela.com.
Your inquiry has been received. We will reply to the email address you provided.