> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexalytica.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Nexalytica Control Plane: Data Governance Settings
> Set your org's data-governance posture: manage policies, run security and PII scans, configure automation rules, and generate compliance reports.
The **Control Plane** is your organisation's command centre for data governance. It brings policy enforcement, security scanning, privacy classification, and compliance reporting into a single screen so you can maintain a consistent governance posture as your data estate grows. Navigate to **Settings → Control Plane** to access it. The six tabs each handle a distinct governance domain, and your active tab is reflected in the URL.
Control Plane configuration is **org-admin only**. Managers and employees work within the guardrails you set here — governance settings are not visible to them.
***
## Scoreboard
Four read-only tiles at the top of the page give you an at-a-glance health check before you dive into any tab.
Number of governance policies currently armed and enforcing rules across your org
Total violations detected by armed policies since the last reset
High-severity issues surfaced by security scans that need immediate attention
Count of sensitive data fields that have a masking, redaction, or flagging action applied
***
## Policy Engine
The **Policy Engine** tab lists every governance policy available to your org and lets you arm or disarm each one independently.
### Policy list
Each row in the policy table shows:
| Column | Description |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Severity | Risk level of the policy (e.g. Critical, High, Medium, Low) |
| Description | What the policy detects or enforces |
| Violation count | How many times this policy has been triggered |
| Sources covered | Number of connected data sources the policy evaluates |
| Last evaluated | Timestamp of the most recent policy evaluation run |
| **Enabled / Disabled** switch | Toggle the policy on or off for your org (enabled = enforced) |
| **Violations** link | Live violation count; click to open the list of open violations for this policy |
| **Gear** (settings) | On policies that are configurable, opens a dialog to tune the policy's settings (thresholds, allow-lists, and so on) |
Use the **Enabled / Disabled** switch on any row to activate or deactivate that policy without affecting others.
Per-agent policy rules are authored separately, on each agent's **Policy** tab in the Agent Foundry — not from the Control Plane.
***
## Security Scans
The **Security Scans** tab surfaces vulnerabilities across your connected infrastructure — credential leaks, weak authentication, and misconfigured surfaces.
### Scan list
Each scan entry shows:
| Column | Description |
| ------------- | ----------------------------------------------------- |
| Scan name | Type of check being performed |
| Status | Current state (e.g. Idle, Running, Completed, Failed) |
| Target | The resource or surface being scanned |
| Last run | Timestamp of the most recent execution |
| Finding count | Number of issues discovered in the latest run |
### Running scans
| Action | What it does |
| ---------------------- | --------------------------------------------------------------- |
| **Run all scans** | Triggers every listed scan simultaneously |
| **Re-run** (per scan) | Re-runs a single scan independently of the others |
| **Details** (per scan) | Expands the row to show individual findings from the latest run |
Run all scans after adding a new data source or rotating credentials to verify your configuration is clean before agents start querying the new connection.
***
## Privacy & PII
The **Privacy & PII** tab discovers and classifies sensitive columns across all your connected data sources, so you can make informed decisions about how each field is handled.
### Running a PII scan
Click **Run PII Scan** to start a scan across all connected sources. Nexalytica analyses column names, data types, and sample values to detect personally identifiable information.
### PII counters
Three counters update after each scan run:
| Counter | Meaning |
| --------------- | ------------------------------------------------------------ |
| Fields Detected | Total PII fields found across all sources |
| Protected | Fields with a masking, redaction, or flagging action applied |
| Needs Review | Fields detected but not yet assigned an action |
### PII field table
Each detected field appears as a row:
| Column | Description |
| ----------- | --------------------------------------------------------- |
| Source | The connected data source containing the field |
| Table | Table or collection name |
| Column | Column name |
| PII type | Category of sensitive data (e.g. Email, Phone, SSN, Name) |
| Sensitivity | Risk level of this field |
| Action | Per-field handling instruction |
### Setting a per-field action
Use the **Action** dropdown on each row to choose how Nexalytica treats that field when agents access it:
| Action | Effect |
| ---------------- | ---------------------------------------------------------------------------- |
| **None** | No special handling; field is passed through as-is |
| **Masked** | Field value is partially obscured (e.g. `***-**-1234`) |
| **Redacted** | Field value is replaced entirely (e.g. `[REDACTED]`) |
| **Flagged** | Field is surfaced in reports and logs as sensitive, but value is not altered |
| **Needs Review** | Marks the field for a human reviewer without applying a transformation yet |
***
## Data Quality
**Data Quality is coming soon.** This tab is reserved for a future milestone and displays an on-screen notice confirming it is not yet available. No data populates it at this time.
When it launches, the Data Quality tab will provide automated checks and scorecards for the data flowing through your connected sources. Watch the Nexalytica release notes for availability.
***
## Reports
The **Reports** tab lets you generate governance and compliance reports from your Control Plane data and download them for stakeholders or regulatory submissions.
**File generation and download are arriving in a later milestone.** You can configure report parameters and queue a report today, but the **Download** button is currently disabled (hover for a tooltip confirming this). Generated reports will appear in the Recent reports list and become downloadable once the feature ships.
### Available templates
| Template | Purpose |
| ------------------------------- | ------------------------------------------------------------------------------- |
| **GDPR Data Processing** | Documents how personal data is collected, stored, and processed across your org |
| **Data Quality Scorecard** | Summarises the quality and completeness of data in connected sources |
| **Board-Ready Executive Brief** | High-level governance summary suitable for board or senior-leadership review |
### Configuring and queuing a report
Select one of the three report templates listed above.
Enter a **From** date and a **To** date to define the period the report should cover.
Toggle between **PDF** and **CSV** depending on how the report will be used.
Click **Generate**. The report is queued and appears in the **Recent reports** list with its current status.
Once report downloads are enabled, click **Download** next to any completed entry in the Recent reports list.
***
## Customization
The **Customization** tab — labelled **Alerts & thresholds** — lets you configure governance notification channels and alert thresholds.
### Notification channels
Click **Configure** next to any channel to set up how your team receives governance alerts:
| Channel | Use case |
| ------------- | ----------------------------------------------------- |
| **Slack** | Real-time alerts in a dedicated governance channel |
| **Email** | Alert emails to nominated addresses |
| **PagerDuty** | Incident-style on-call alerting for critical findings |
| **Webhook** | POST alerts to any HTTPS endpoint for custom routing |
### Thresholds
Adjust the sliders to set your governance sensitivity:
| Slider | What it controls |
| --------------------------------------- | --------------------------------------------------------------- |
| **Risk-score alert threshold** (0–100) | The minimum risk score that triggers a notification |
| **Audit-log retention (days)** (1–3650) | How long audit log entries are retained before automatic expiry |