Glossary

Definitions for the Kybera Impact and Microsoft 365 governance terms used throughout this documentation. Terms are cross-linked to the detail pages where they're described more fully.

Adaptive scope. A Microsoft Purview feature that targets retention or sensitivity policies based on site or content properties, rather than by enumerating target sites explicitly. Impact's workspaces carry consistent metadata (workspace type, Business Authority) that adaptive scopes can target reliably. See Purview alignment.

Ad-hoc library. A document library created directly on a SharePoint site by a site owner or user, outside of Impact's template and catalogue model. Ad-hoc libraries are outside Impact's compliance enforcement scope and count against the Enterprise Adoption audit KPI. Contrast with Impact-managed library.

Archived workspace. A workspace lifecycle state indicating the workspace is retained but no longer in active use. See Workspace lifecycle.

Audit run. A scheduled Kybera Impact operation that scans every Impact-managed workspace, computes governance KPIs, and writes results to the portal. Audit observes and records; it doesn't modify content. See Insights & audit.

IM Portal. The Kybera Impact app where information-management users maintain workspace templates, repository templates, taxonomy, and user roles. See IM Portal.

Broker (business broker). A user granted authority to approve or reject workspace requests within a configured scope (typically by Business Authority). See Request approvals.

Broker Portal. The Kybera Impact app business brokers use to review requests and oversee workspaces in their scope. See Broker Portal.

Bulk provisioning. Impact's capability to provision many workspaces in a single run — typically used during initial rollout to stand up an organization's hub-and-spoke structure in one pass. See Workspace provisioning.

Business Authority. Impact's bilingual, two-level hierarchical ownership metadata. Travels with workspaces and content through provisioning, compliance, and records scenarios. See Business Authority.

Catalogue. Impact's shopping-cart model for adding pre-approved libraries and lists to existing workspaces. Available through the New Repository Request app. See New Repository Request.

Compliance run. A scheduled Kybera Impact operation that validates Impact-managed workspaces and repositories against their templates and applies automatic corrections to drift. See Compliance.

Content type. A Microsoft 365 definition of a kind of content (Contract, Policy, Meeting Record) carrying a defined set of metadata fields. Kybera Impact deploys enterprise content types tenant-wide and references them in templates. See Information architecture.

Controlled Vocabulary list. An Kybera Impact portal list that drives displayed text across the apps. Lets organizations customize terminology dynamically — including bilingual variants — without modifying the apps. See Multilingual support.

Enterprise adoption. An Kybera Impact audit KPI measuring the proportion of libraries on a workspace that are Impact-managed versus ad-hoc. Higher enterprise adoption means stronger inheritance of the enterprise information architecture. See Audit KPIs reference.

Force-run flag. A per-workspace setting that causes the next scheduled compliance run to process the workspace regardless of its last-run status — used to propagate template changes immediately. See Compliance.

Governance score. An Kybera Impact audit KPI; the 0–100 aggregate of the other governance KPIs, weighted by workspace type and sensitivity. The headline number in the Insights app. See Audit KPIs reference.

Hub site. A Microsoft 365 site model where a designated hub site groups related workspaces for navigation, search, and visual consistency. Kybera Impact templates support hub registration and association. See Information architecture.

Impact-managed library. A library provisioned from an Kybera Impact repository template and tracked in the provisioned-repositories inventory. Participates in compliance runs and contributes to enterprise adoption. Contrast with ad-hoc library.

Impact-managed workspace. A workspace provisioned by Kybera Impact from a workspace template and tracked in the provisioned-workspaces inventory. Participates in compliance, audit, and Insights reporting. Contrast with workspaces created outside Kybera Impact (which aren't in enforcement scope until explicitly brought under management).

Insights. The Kybera Impact app surfacing tenant-wide governance dashboards — workspace inventory, KPI health, usage, activity, provisioning analytics, and lifecycle operations. See Insights app.

Managed identity. An Azure feature letting automation authenticate to Microsoft 365 and Azure without stored passwords. Impact's Azure Automation runs under a managed identity. See Security & tenant boundaries.

Managed metadata service. The Microsoft 365 service hosting the term store — where Impact's taxonomies (Business Authority, controlled vocabularies) live. See Information architecture.

New Repository Request. The Kybera Impact app users open to add libraries and lists to their workspaces from the catalogue. See New Repository Request.

New Workspace Request. The Kybera Impact app users open to request a new SharePoint site or Microsoft Team. See New Workspace Request.

Portal (Kybera Impact portal). The set of SharePoint sites in the client tenant that hold Impact's configuration, requests, templates, inventory, audit history, and taxonomy artefacts. See Portal site.

Provisioned-workspaces inventory / provisioned-repositories inventory. The Kybera Impact portal lists tracking every workspace or repository Kybera Impact has provisioned — with template, owners, Business Authority, compliance status, and lifecycle state.

Purview. Microsoft's compliance platform — retention labels, sensitivity labels, adaptive scopes, records management, data-loss prevention. Kybera Impact aligns with Purview for labels and adaptive scope targeting. See Purview alignment.

Repository. Impact's term for a list or a document library. Used to distinguish the in-workspace provisioning surface (repository templates, repository requests) from the workspace-level provisioning surface.

Repository template. A template defining the structure of a list or library — columns, content types, views, default labels. Available through the catalogue. See Workspace & library templates.

Schema governance. An Kybera Impact audit KPI measuring whether content types in Impact-managed libraries still match their template definitions — detecting unauthorized schema drift. See Audit KPIs reference.

Sensitivity label. A Microsoft Purview classification that can be applied to sites (controlling sharing and access) and documents (controlling encryption and rights). Kybera Impact templates can carry site-level and document-level default sensitivity.

Shadow library risk. An Kybera Impact audit KPI measuring the presence of unmanaged libraries carrying significant content — detecting libraries that should be in the catalogue but aren't.

Site column. A reusable field definition in SharePoint that lists and libraries can reference. Kybera Impact deploys enterprise site columns bilingual by default. See Information architecture.

Solution (Power Platform solution). The Microsoft-recommended packaging for Power Apps and flows — enabling version control, cross-environment deployment, and environment-variable-driven configuration. Impact's five apps ship as solutions. See PowerApps deployment.

Taxonomy. A controlled vocabulary held in the term store. Business Authority is a taxonomy; classification schemes and topic hierarchies can also be taxonomies. Maintained by IM users through the IM Portal's Excel-based workflow.

Template (workspace template / repository template). A packaged definition of the structure and settings of a SharePoint site, Microsoft Team, list, or library. Every Impact-provisioned resource is created from a template. See Workspace & library templates.

Term store. See managed metadata service.

Workspace. Impact's term for a SharePoint site, optionally with a linked Microsoft Team. The unit of provisioning at the workspace level.

Workspace template. A template defining the structure and settings of a workspace — libraries, content types, labels, hub association, property bags. Available through the New Workspace Request app. See Workspace & library templates.

What to read next​

What to read next