Anonymized engagement summary: SharePoint Online home site launch and Power Automate permission automation for internal and external project sites at a federal government contractor (2024)
Contracted — countersigned (EPC-reported; documents private)First-pass editionA federal government contractor (client not named) · 2024 · Project ID EPC-2024-ANON-FEDCON-SPO
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In June 2024 a federal government contractor countersigned a statement of work with EPC Group for a SharePoint Online intranet initiative. The work:
- launch a new home site and homepage, including a custom LinkedIn web part
- convert the department site template to a communication site
- migrate and modify an existing suggestion form
- automate permissions on internal and external project sites with Power Automate
The permission automation covers site permissions from a configuration list, folder-level permissions, sharing permissions and navigation. The initiative was scheduled for two to three weeks.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The countersigned statement of work is retained privately and is not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from that document.
Verification class
Contracted — countersigned (EPC-reported; documents private). The contractor signed the statement of work electronically in June 2024. No acceptance record or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | A federal government contractor (client not named) |
| Situation | A SharePoint Online intranet being relaunched, with project sites shared internally and with external parties |
| Home site | Set up and launch the new home site and homepage layout; build and configure a custom LinkedIn web part for the homepage |
| Templates | Convert the department site template to a communication site; configure project site templates |
| Forms | Modify an existing suggestion form and migrate it from its current site collection to the new destination site collection |
| Permissions | A configuration list that adds permissions to project sites and external project sites automatically. External sites get the same site admins and owners, with members added manually; internal sites get consistent permissions. Folder-level and sharing permissions are managed through Power Automate, which also configures navigation. Ongoing help with site permissions |
| Timeline | Two to three weeks, delivered in short cycles that each ship a working piece |
Unknowns, not stated in the document cited: the number of sites or users, the launch date, and any measured result.
Approach and artifacts
Permissions as configuration, not clicks. Project sites, internal and external, get their permissions from a configuration list applied by Power Automate. Folder-level and sharing permissions run through the same automation. External sites keep the same site admins and owners, while members are added by hand.
Relaunch the front door at the same time. The home site, homepage and the communication-site conversion of the department template give the intranet one consistent entry point. The existing suggestion form is modified and moved to the new site collection.
Phased and short. Requirements and data discovery, design, deployment with quality assurance and testing, then post-deployment best practices and project closure, with weekly status reporting throughout.
Document (held privately):
| Document | Date |
|---|---|
| Statement of work, Microsoft SharePoint Online initiative (countersigned) | June 2024 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The contractor engaged EPC Group for the home site launch, template conversion, form migration and permission automation | Countersigned statement of work, June 2024 | Contracted (EPC-reported; documents private) |
| Launch completed, automation in production, or measured results | No document cited | Not claimed |
Provenance
- Source: the countersigned statement of work (June 2024), held privately. Engagement ID: EPC-2024-ANON-FEDCON-SPO, an alias unrelated to the client's name.
- Anonymization: sector only, under EPC Group's anonymized-case rule; the contractor's name, agencies served, location, staff names and commercial terms are not published.
- Not claimed: client endorsement, completion, or any measured result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, who signed the statement of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's countersigned statement of work.
Related service
SharePoint governance consulting · SharePoint consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.