> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/workflow-guides/assurance/platform-policy.md).

# Platform Policy

Set application-wide classification, connectivity, mapping, News, trial and delegated-work defaults without weakening the deployed security boundary.

**Who uses this:** Administrator\
**Open in CORTEX:** `/administration/platform/policy`\
**In-app guide:** `/help?topic=platform-policy`

**Expected result:** A versioned runtime policy is retained with the administrator, reason and exact settings; subsequent identity and provider checks use that revision.

## Before you start

* Confirm the persisted global-administrator role and the current deployed OFFICIAL or OFFICIAL-SENSITIVE boundary.
* Identify which approved providers are actually configured; enabling a policy never supplies credentials or assurance evidence.
* Choose a classification floor, organisation default and ceiling that fit existing grants and retained work.

## What to do

{% stepper %}
{% step %}

## Review classification

Set the minimum, default and maximum classification.

New identity reads clamp effective clearance to the ceiling; existing retained content and markings are not rewritten.
{% endstep %}

{% step %}

## Configure connectivity

Set the platform internet default, then enable only the required News and mapping categories.

Organisation policy can narrow access further; it cannot override a platform-wide Offline decision.
{% endstep %}

{% step %}

## Check provider readiness

Open News or the map readiness panel.

OSM uses the standard same-origin gateway. Satellite and hybrid need an operator-configured licensed source; News connections need current System assurance approval.
{% endstep %}

{% step %}

## Configure trial and delegation

Allow detailed trial provisioning only when the platform can create the complete isolated synthetic lifecycle.

Delegated work remains assigned to a named owner for review and generates the normal notification/email.
{% endstep %}

{% step %}

## Record and verify

Enter an accountable reason, save once, then verify the retained revision in Policy history and reload an affected workspace before testing effective access.
{% endstep %}
{% endstepper %}

## Check the result

* Does the default sit between the floor and ceiling?
* Does the immutable deployed profile permit internet transport?
* Are provider credentials and System assurance approvals current?
* Did I record why the platform-wide behaviour changed?

## If you get stuck

<details>

<summary>Why can I not enable internet?</summary>

An OFFICIAL-SENSITIVE deployment is an immutable Offline boundary. Change requires a separately assured deployment, not a runtime toggle.

</details>

<details>

<summary>Why is satellite or hybrid still unavailable?</summary>

The runtime switch permits an already reviewed category. The operator must also configure the licensed server-side provider, credential, attribution, limits and current assurance evidence.

</details>

<details>

<summary>Why is News still held?</summary>

Open the readiness action and System assurance. Each exact feed connection needs a current data-flow approval; platform and organisation Online settings do not bypass it.

</details>

<details>

<summary>When do classification changes apply?</summary>

New operations refresh identity and organisation policy. Existing retained markings stay unchanged; reload the workspace before testing a new boundary.

</details>

## Responsibility and limits

* Never use runtime policy to imply provider accreditation, legal authority or a change to retained handling.
* Treat satellite credentials and provider tokens as protected deployment configuration. Configure the platform SMTP mailbox through Platform email delivery; secrets are protected and never entered into the runtime-policy form.

## Reference and scope

Runtime configuration is a bounded administrative decision. The immutable deployment profile remains the security floor and external providers still need exact configuration and assurance approval.

## Related workflows

* [Onboard a customer organisation](broken://pages/ef1d5d98a05d8d88291cb372765cb5673ebb3f03)
* [Maintain a system control and evidence baseline](broken://pages/699956df97c18fc4ddd8894884fea67a7b6e90ce)
* [Record UK processing paths and approved uses](broken://pages/d1a5ce8a791f7e21103f6f699e97b63ddcffb253)
* [Turn an unassessed news lead into a reviewed question](file:///7397340/direction/news.md)
* [Explore and retain governed geographic evidence](file:///7397340/analyse/map.md)
* [Work through connection and deployment limits](broken://pages/e2892068271c3c1f3c4471ca5a8f532a8174ba43)