> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organisation Settings

> Configure general settings, agent behaviour, and AI features for your organisation.

<Note>
  Organisation settings apply to all clusters and resources within your organisation. Only administrators can modify these settings.
</Note>

## Accessing Organisation Settings

1. Click your profile icon in the bottom left corner of the Ankra platform.
2. Select **Organisation** from the menu.
3. Click **Settings** in the organisation view.
4. Navigate to **General** to access these settings.

***

## General Settings

### Organisation Name

Change the display name of your organisation. This name appears throughout the platform and helps identify your workspace.

<Steps>
  <Step title="Navigate to Settings">
    Go to **Organisation Settings** → **General**.
  </Step>

  <Step title="Edit the Name">
    Enter a new name in the **Organisation Name** field.
  </Step>

  <Step title="Save Changes">
    Click **Save Changes** to apply.
  </Step>
</Steps>

<Info>
  Only administrators can rename organisations. Members will see the rename option disabled.
</Info>

***

## Agent Settings

Configure default agent behaviour for all clusters in your organisation.

### Auto-upgrade Agents

When enabled, cluster agents automatically upgrade to the latest version when available. This ensures your clusters stay up-to-date with security patches and new features.

| Setting      | Description                                                    |
| ------------ | -------------------------------------------------------------- |
| **Enabled**  | Agents upgrade automatically when new versions are released    |
| **Disabled** | Agents remain at their current version until manually upgraded |

<Tip>
  Individual clusters can opt-out of auto-upgrades in their own settings, even when the organisation setting is enabled. See [Cluster Settings](/platform/cluster-settings) for details.
</Tip>

**How Auto-upgrade Works:**

1. Ankra releases a new agent version
2. The platform detects clusters running older versions
3. If auto-upgrade is enabled (and the cluster hasn't opted out), the agent is upgraded automatically
4. The upgrade process is seamless with minimal disruption

***

## AI Features

Configure AI-powered capabilities for your organisation.

### Proactive AI Insights

When enabled, Ankra's AI continuously scans your clusters and generates insights with root cause analysis, remediation commands, platform-aware actions, and conversation starters. Insights are visible on the dedicated AI Insights page for each cluster, with a detail page, analytics dashboard, and keyboard shortcuts.

<Steps>
  <Step title="Navigate to AI Features">
    Go to **Organisation Settings** → **General** and find the **AI Features** section.
  </Step>

  <Step title="Toggle Proactive AI Insights">
    Enable or disable the **Proactive AI Insights** toggle.
  </Step>
</Steps>

<Info>
  When disabled, AI analysis still works on-demand via the AI Assistant (`⌘+J`), but automatic proactive insights are not generated.
</Info>

| Scenario            | AI Insight                                                          |
| ------------------- | ------------------------------------------------------------------- |
| Pod crash loop      | Identifies common causes like OOM, missing configs, or image issues |
| High resource usage | Suggests scaling recommendations                                    |
| Failed deployments  | Analyzes sync errors and provides remediation steps                 |
| Network issues      | Identifies service mesh or ingress misconfigurations                |

For full documentation on viewing, filtering, resolving, and analyzing insights, see the [AI Insights](/platform/ai-insights) page.

***

## DNS Records

Organisation admins can create manual CNAME, A, and TXT records under your organisation's own delegated Ankra subdomain (under `ankra.cc` by default, or the [Ankra domain your organisation selected](/concepts/applications#the-preview-url)) - useful for aliasing an add-on's auto-generated hostname to something memorable.

<Frame caption="Adding, searching, editing, and deleting DNS records in the organisation console">
  <img src="https://mintcdn.com/ankra/QTIxthxO-T9_QJcI/images/dns-records-walkthrough.gif?s=c6c143928253865027a2f7d4b9e82d1b" alt="Walkthrough of the DNS records console: adding a CNAME record, filtering the list, editing a record's target in place, deleting a record, and switching between light and dark themes" className="w-full rounded-xl" width="1200" height="657" data-path="images/dns-records-walkthrough.gif" />
</Frame>

<Steps>
  <Step title="Navigate to DNS Records">
    Go to **Organisation Settings** → **DNS records**.
  </Step>

  <Step title="Add a record">
    Click **Add record**, enter a label (for example `logs`), pick a record type (CNAME, A, or TXT), enter the target, and choose a **TTL** (Auto, or 1 minute up to 1 hour). Your organisation's zone is appended to the label automatically.
  </Step>

  <Step title="Track its state">
    New records provision asynchronously and show as **Pending** until the record is live in DNS (**Active**), or **Failed** with the reason if provisioning didn't succeed.
  </Step>

  <Step title="Edit or delete a record">
    Use the row actions to **edit** a record's target and TTL in place, or **delete** it. Editing re-points the record and returns it to **Pending** until the change is live. To change a record's name or type, delete it and add a new one.
  </Step>
</Steps>

### Cluster domains

The same page lists every cluster's own delegated Ankra domain (`<cluster-id>.<org-id>.<ankra-domain>`) with its provisioning state. **Remove** hands a cluster's domain back for teardown - the step required on every cluster before [switching the organisation's Ankra domain](/concepts/applications#the-preview-url) - and **Enable domain** brings a cluster (back) under the organisation's current Ankra domain; external-dns picks a newly enabled domain up on the cluster's next cloud-provider pass. The same pair exists in the CLI as `ankra cluster domain <cluster>` and `ankra cluster domain <cluster> --remove`.

<Info>
  Any organisation member can view the record list; only administrators can add, edit, or delete records. A record's own zone must be active before a record can be created under it - new organisations provision this automatically, and the DNS records page shows the zone and its status at the top.
</Info>

<Note>
  A CNAME record can never share a name with another record (standard DNS behaviour), and each name/type pair can only have one record.
</Note>

***

## Danger Zone

<Warning>
  Actions in the Danger Zone are destructive and cannot be undone. Proceed with extreme caution.
</Warning>

### Delete Organisation

Permanently remove your organisation and all associated data, including:

* All clusters (disconnected, not deleted from your infrastructure)
* All stacks and configurations
* All credentials and integrations
* All user memberships

<Steps>
  <Step title="Navigate to Danger Zone">
    Go to **Organisation Settings** → **General** and scroll to the **Danger Zone** section.
  </Step>

  <Step title="Click Delete">
    Click the **Delete** button. Only administrators see this option.
  </Step>

  <Step title="Confirm Deletion">
    Type the organisation name exactly as shown to confirm, then click **Delete Organisation**.
  </Step>
</Steps>

<Warning>
  Deleting an organisation does not delete resources from your Kubernetes clusters. It only removes them from the Ankra platform. Running workloads will continue to run.
</Warning>

***

## Related Settings

<CardGroup cols={2}>
  <Card title="Variables" icon="code" href="/concepts/variables">
    Define organisation-wide variables for use in stacks.
  </Card>

  <Card title="Encryption (SOPS)" icon="lock" href="/guides/sops">
    Configure SOPS encryption for your organisation.
  </Card>

  <Card title="Cluster Settings" icon="server" href="/platform/cluster-settings">
    Configure individual cluster settings.
  </Card>

  <Card title="DNS Records" icon="globe" href="/platform/organisation-settings#dns-records">
    Create custom CNAME, A, and TXT records under your organisation's Ankra subdomain.
  </Card>

  <Card title="User Management" icon="users" href="/concepts/organisations">
    Invite users and manage roles.
  </Card>
</CardGroup>