Role
- Workflow design
- Dataverse modelling
- Power Pages implementation
- Automation
Stack
Power PagesDataversePower AutomateSharePointMicrosoft Lists
Project summary
A Power Platform solution that organizes employee asset requests, approvals, signatures and generated documents in a structured workflow.
The problem
Asset requests and employee records were difficult to track consistently when information lived across separate manual documents, emails and spreadsheets.
Requirements
- Track employee and asset request information.
- Capture approvals and signatures.
- Generate request documents automatically.
- Store structured data in Dataverse.
- Keep sensitive employee data out of public screenshots and case-study assets.
Architecture
01Employee request
02Power Pages
03Dataverse
04Power Automate
05Document generation
06SharePoint storage
Your responsibilities
- Mapped the request lifecycle.
- Modelled Dataverse tables and relationships.
- Built portal pages and automation flows.
- Documented privacy constraints for public presentation.
Technical implementation
- Power Pages provides the front-end request experience.
- Dataverse stores normalized employee, asset and approval data.
- Power Automate coordinates document generation, notifications and storage workflows.
Engineering challenges
Turning documents into structured workflow
The original process depended on forms and files rather than clear data entities.
The platform separated employee, asset, approval and generated-document records into reusable data structures.
Low-code platforms still need careful information architecture.
Security and privacy
- Employee information is treated as sensitive data.
- Public case-study material avoids real names, IDs, tenant details and internal domains.
- Access control is designed around organizational roles.
Outcome
- Centralized asset request tracking.
- Generated request documents automatically.
- Reduced manual coordination across forms, approvals and document storage.
Lessons learned
- Power Platform is most effective when the data model is designed before automation flows.