Workspace lifecycle
Every workspace your organization provisions through Kybera Impact has a defined lifecycle — Active, Archived, or Disposed. No ambiguity, no zombie workspaces, and no manual coordination across SharePoint and Microsoft Teams.
The three states
- Active — the workspace is in production. Compliance and audit run on it. Users work in it as normal.
- Archived — paused. The workspace is preserved but read-only. If the workspace is Teams-connected, the Team is archived through Microsoft Graph; the underlying SharePoint site is locked through PnP. Compliance and audit don't run on archived workspaces — there's nothing to validate.
- Disposed — formally ended. The Microsoft Team and the SharePoint site are removed; audit data is purged; the registry row is retained as an audit trail until the configurable retention window expires.
The six lifecycle operations
Six coordinated operations move workspaces between states, covering both Teams-connected workspaces and SharePoint-only workspaces:
| Teams-connected | SharePoint-only | |
|---|---|---|
| Archive | Archive the Team, lock the site read-only | Lock the site read-only |
| Unarchive | Reactivate the Team, unlock the site | Re-enable site editing |
| Dispose | Remove the Team and the site, purge audit data | Remove the site, purge audit data |
Lifecycle operations are initiated from the IM Portal by your IM team, or from the Broker Portal by brokers where your organization delegates that authority.
Why your organization benefits
- Every workspace has a defined end. Workspaces don't drift into permanent abandonment. When a project ends, when a team disbands, when a campaign closes, the workspace moves through a governed transition.
- Two services, one operation. Archiving a Teams-connected workspace coordinates Microsoft Teams and SharePoint Online automatically — no manual sequencing across two admin centres.
- Recoverable at every step. Archived workspaces unarchive. Disposed sites remain in SharePoint's recycle bin for ~93 days. Even the registry row goes through the list recycle bin when it's cleaned up.
- The registry stays honest. If a workspace is deleted outside the platform's flow, the audit catches it and marks the workspace deleted. If a site exists without a registry row, tenant reconciliation rebuilds it.
What's coming
A planned records management module will bring structured retention schedules, records declaration workflows, and end-of-retention disposition into the same platform. Finer-grained Teams lifecycle — Team-only archive or disposal independent of the underlying site — is also on the roadmap. See the Roadmap for status.
Where this fits
Lifecycle ends what Provisioning begins. The Compliance disposed-cleanup pass handles the registry audit trail after disposal.