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

# Organisation Settings

> Configure your organisation's name, discussion notifications, and finding identifier

Organisation Settings is where Admins control how the workspace operates: the organisation name, how email notifications for finding discussions behave, and the prefix used in finding identifiers. Open it from the user menu in the top-right corner.

<Info>
  Only **Admin** and **Owner** roles can edit organisation settings. Other members see a read-only view of the same information.
</Info>

## General information

The general section shows your organisation's name and discussion notification defaults.

### Organisation name

The display name for your organisation, visible to all members throughout the platform. Admins can change it at any time. Saving requires [step-up verification](/platform/step-up-verification).

### Discussion reply emails

When someone (Borg or a teammate) replies in a finding's [discussion thread](/platform/findings#discussion-and-activity), Odin can send an email so you don't miss it.

* **Discussion reply emails (toggle)**: when on, all members receive emails for new discussion replies on findings, unless overridden by each user in their [profile](/platform/profile). When off, no emails are sent by default — only users who opt in via their profile receive them.
* **Minimum severity for reply emails**: only findings at or above this severity trigger reply emails. Defaults to all severities.

<Tip>
  Mentions (e.g. <code>@alice</code>) always send an email, regardless of severity threshold or the organisation default.
</Tip>

## Finding identifiers

Every finding in your organisation gets a unique identifier like `ACME-42`. The prefix (`ACME`) is your **finding prefix** — choose something short and memorable, typically your organisation's abbreviation.

The prefix can be set once during onboarding and changed afterwards. Changing it renumbers nothing — existing findings keep their identifiers, new findings use the new prefix going forward.

Saving a new prefix requires [step-up verification](/platform/step-up-verification).

## Default finding subscribers

Owners and Admins choose who is subscribed automatically when a new finding is reported, from the **Default finding subscribers** setting:

* **All members** — every member is subscribed automatically, except **Read Only** users. This includes people who join the organisation later.
* **Custom** — only a selected list of members is subscribed automatically.

This only sets the starting subscriber list for new findings. Individuals can still [follow or unfollow](/platform/findings#following-findings) specific findings themselves, regardless of the default.

## Organisation overview

A summary card shows key details about your organisation:

* **Members**: the current member count, with a link to [Team Management](/platform/team-management) for admins
* **Status**: your organisation's current status
* **Products**: which products are active on your subscription
* **Created**: when the organisation was created

## Domain join

If your organisation has **domain join** enabled, anyone with an email address matching your allowed domain(s) can join automatically without an invitation.

Domain join is configured by Borg as part of onboarding. It appears as a read-only field on the General Information card. Contact [mail@borghq.io](mailto:mail@borghq.io) if you need it enabled or changed.

<Warning>
  Domain join is powerful — anyone with a matching email can join. We only enable it for verified company domains, never for shared providers like `gmail.com`.
</Warning>

## Legal and agreements

The **Legal & Agreements** card links the documents that govern your use of the platform:

* **Master Services Agreement**, **Data Processing Agreement**, and **AI Services Addendum** — the agreements an Owner accepted during onboarding, opening as PDFs
* **Privacy Policy** and **Subprocessors** — the in-app policy pages

Every member can open these links, regardless of role. The same documents are also collected on the [`/legal`](/getting-started/terms-of-service#finding-the-agreements-later) page.