A worked example
A Team should not become next year’s governance problem.
One Team, over eighteen months. A SharePoint site, a guest account or a Power Platform environment goes the same way — this is the shape, not a special case.
- 01 Prevent Day 0
It is correct before it exists.
Operations requests a project Team. The template decides its name, its two owners, its channels, and whether anyone outside the organisation can be invited at all. The requester supplies a title; the governance is already in the template.
- template
- OPS-Project v4
- naming
- OPS-PRJ-{title}
- external sharing
- by request only
- 02 Find Month 14
Nobody filed anything. It was noticed anyway.
The project finished, the owner has left, and one external consultant still has access. Athentra sees that the Team no longer matches policy and raises it as an event — not as a row in a report.
- event
- Compliance.Violation.Created
- policy
- Orphaned workspace with guests
- owner
- unresolved
- 03 Fix Same day
The review goes to the manager, not to IT.
It arrives with the evidence and a recommendation. She removes the consultant, keeps the Team because retention requires it, and writes why. Had she not answered, it would have escalated.
- event
- AccessReview.Completed
- decision
- retain — access revoked
- decided by
- owner, Operations
IT kept control of the process. It did not have to make the decision — and that is true of every resource, not just this one.
