infotechCustomer and partner websites
Create task-oriented experiences for external audiences. Organise navigation, content and forms around the information visitors need to complete their purpose.
Microsoft Power Pages
Bring your business closer to the people you serve.
Create connected business websites for customers, partners and communities.
Built forCustomer, partner and external-service teams
The focusExternal experiences connected to business processes
Our delivery approach The business perspective
Technology witha clear purpose.
External audiences need a practical way to interact with your business. A connected portal can make information and service processes easier to access.
A useful portal does more than put a form online. It helps an external user complete a task and keeps that task connected to the people processing it internally. Power Pages can support that relationship through websites connected with Dataverse. We design the external journey and the operational response together, including identity, records, status and the point at which someone needs assistance. The experience should be clear on a phone as well as a desktop.
Explore the possibilities
Built for the workthat matters.
A closer look at the capabilities and decisions that shape a useful solution.
Dataverse-connected forms
Connect submitted information with business records. Define the validation, supporting evidence and internal ownership needed to process each request.
Identity and access
Choose a supported authentication approach and map users to appropriate roles. Design access around the relationship between the person and the records.
Table and page permissions
Control access to data and site content separately. Validate permissions using representative users, including anonymous visitors where they are supported.
Workflow integration
Connect portal activity with approvals and internal work. Give users meaningful status information without exposing records they should not see.
Site operations
Plan content ownership, accessibility, release management and support. Keep the external experience aligned with changes in the underlying business process.
From capability to everyday value
See itin practice.
Explore possible starting points for your organisation. Each scenario connects a business need with work to consider and measures to review.
Customer services · Illustrative scenario
Give customers a visible request journey.
Customers submit a request but cannot see whether it has been accepted or what is missing. Design an intake process with clear confirmation, supporting documents and a useful status. Connect the request to an internal owner and a route for follow-up.
What to measureCompleted requests and status enquiriesAgree a baseline and targets with your business owners.
Partner operations · Illustrative scenario
Create a shared place for partner submissions.
Partners send information through different email templates. Establish a consistent submission experience and define which records a partner can access. Include the review process, requests for clarification and the point at which an internal team accepts responsibility.
What to measureSubmission completeness and review timeAgree a baseline and targets with your business owners.
External applications · Illustrative scenario
Make a complex application easier to finish.
An applicant needs to provide information in stages. Map the journey into understandable steps, identify the evidence required and test it on mobile devices. Explain what happens after submission and how the applicant can correct or complete the information.
What to measureApplication completion and missing informationAgree a baseline and targets with your business owners.
The Defacto approach
Clarity at every step.Ownership beyond launch.
We map the external user journey, design the site and establish the data and permissions model before integrating workflows and preparing your teams.
Explore our approach- 01
Map both sides of the experience
Define external users, tasks and internal processing responsibilities. Review the information each audience needs to see and update.
- 02
Design data and permissions
Agree the Dataverse model, identity approach and role boundaries. Test permissions and complete journeys with representative external users.
- 03
Prepare the live service
Validate accessibility, mobile usability and content. Establish ownership for site changes, operational support and the records submitted through the portal.
A useful first conversation
Bring the context.
We’ll help shape the next step.
A few examples of your current work will make the discussion more specific.
- External audiences and priority journeys
- Identity providers and user-to-record relationships
- Forms, documents and internal processing workflows
- Content ownership and support for portal users
Experience you can explore
See the workbehind the words.
Customer experienceAnimal Health Ireland
Digital services that support better livestock health.
Automation of registration, reminders, and certificate generation streamlined administrative tasks, allowing the organisation to focus on delivering better animal health outcomes.
Explore the customer storyMake an informed decision
Your questions.Considered answers.
The right scope starts with a clear understanding of your business, the platform and the work ahead.
Can customers see only their own records?
Power Pages provides web roles and table permissions that can support a scoped data-access design. The configuration must match the relationship between users and records. We test both permitted access and attempts to reach another user’s information.
Is signing in enough to protect the data?
No. Authentication establishes identity, while permissions determine access to records and pages. Both need to be designed and validated. A signed-in user should receive only the access required for the tasks they are authorised to perform.
Can the portal connect to our internal workflow?
Yes, through a defined data and integration design. We map what happens after submission, who reviews the information and which updates should be visible externally. The portal and internal application should support one coherent process.
Explore Microsoft guidance
Keep exploring
Connect yournext decision.
Your next chapter starts here
What’s your next?
A challenge to solve. An idea to explore. Let’s talk.