# Organization, Identity, Access, and Governance

Organization structure, people, roles, purpose, eligibility, acceptance, access, retention, and governance. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.

## Overview

**Package:** `BND-ORG` · **Type:** Platform foundation · **Documentation:** 1.0

[Marketplace listing](/marketplace/bnd-org) · [Technical reference](/documentation/packages/bnd-org/technical-reference)

Identity enforcement stays in the platform. A business role never automatically grants access to private coaching or restricted ethics cases.

## User guide

1. Define workspaces, business units and role assignments before granting source access.
2. Check purpose and eligibility for the intended processing scope; resolve missing acceptance records.
3. Review access changes, retention rules and exceptional access in the governance workspace.

### Screens owned by this package

- [Administration — Organization](/documentation/packages/bnd-org/screens/administration-organization) — `SCR-ADM-01`.
- [Administration — People & Access](/documentation/packages/bnd-org/screens/administration-people-and-access) — `SCR-ADM-02`.
- [Administration — Governance](/documentation/packages/bnd-org/screens/administration-governance) — `SCR-ADM-04`.

### Contributions to other screens

- [Ethics & Compliance — Review Queue](/documentation/packages/bnd-ethics/screens/intelligence-ethics-review-queue) — owned by `BND-ETHICS`; this package contributes analysis or interface content.
- [Ethics & Compliance — Cases](/documentation/packages/bnd-ethics/screens/intelligence-ethics-cases) — owned by `BND-ETHICS`; this package contributes analysis or interface content.
- [Ethics & Compliance — Policies](/documentation/packages/bnd-ethics/screens/intelligence-ethics-policies) — owned by `BND-ETHICS`; this package contributes analysis or interface content.
- [Ethics & Compliance — Reviewer Audit](/documentation/packages/bnd-ethics/screens/intelligence-ethics-reviewer-audit) — owned by `BND-ETHICS`; this package contributes analysis or interface content.
- [Search Assistant — Search History](/documentation/packages/bnd-search/screens/explore-search-history) — owned by `BND-SEARCH`; this package contributes analysis or interface content.
- [Reports — Scheduled](/documentation/packages/bnd-reports/screens/explore-reports-scheduled) — owned by `BND-REPORTS`; this package contributes analysis or interface content.
- [Reports — Exports](/documentation/packages/bnd-reports/screens/explore-reports-exports) — owned by `BND-REPORTS`; this package contributes analysis or interface content.
- [Administration — Audit & Security](/documentation/packages/bnd-aiops/screens/administration-audit-and-security) — owned by `BND-AIOPS`; this package contributes analysis or interface content.

## Configuration

| Setting | Purpose and behavior |
|---|---|
| Roles and workspace scopes | Map organizational roles to permitted objects and purposes; avoid blanket access through a reporting line. |
| Eligibility and acceptance | Set required participation records and the processing scopes they cover. |
| Retention and holds | Define schedules, hold authority and deletion restrictions for governed objects. |

Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.

## Technical reference

The [implementation reference](/documentation/packages/bnd-org/technical-reference) identifies `DM-ORG`, `WFP-ORG-GOVERNANCE`, 1 owned agent, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.

## Compatibility and dependencies

- [Core Platform and Application Shell](/documentation/packages/bnd-core) — `BND-CORE`.

Direct consumers: [Sources, Integrations, and Evidence Foundation](/documentation/packages/bnd-evidence), [Meeting and Conversation Intelligence](/documentation/packages/bnd-meeting), [Finding Lifecycle, Evidence Assurance, and Review](/documentation/packages/bnd-findings), [Ethics and Compliance Review](/documentation/packages/bnd-ethics), [Evidence Search Assistant](/documentation/packages/bnd-search), [Reports, Scheduling, and Governed Exports](/documentation/packages/bnd-reports), [AI, Platform, Audit, and Security Operations](/documentation/packages/bnd-aiops).

Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.

## Extensions and enrichment

Extend organizational attributes and purpose policies through versioned schemas and deterministic policy checks. P01 consumes those decisions; it does not grant permission.

Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the [developer extension guide](/documentation/developers/package-authoring).

## Versions and upgrades

The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.

1. Compare release manifests, permission changes and migrations against the current lock.
2. Test package behavior and affected dependent workflows with representative, authorized evidence.
3. Promote the signed release after approval and record the resulting lock.
4. Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.

## Used in solutions

[Technology Consulting & Delivery](/documentation/technology-consulting-delivery) includes this package as **mandatory**. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.