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

# Manage an organization

> Create an Enterprise organisation, invite teammates, acknowledge releases, audit log, stack health score.

> Organisations are an **Enterprise** feature. They turn Relnx from an
> individual-account tool into a team workspace with shared followed tools,
> roles, an audit log, and the stack health score.

## Create an organisation

1. **Settings → Organisations → Create new** (you must be on Enterprise).
2. Pick a name and slug. The slug becomes part of the URL
   (`www.relnx.io/organizations/<slug>`).
3. You become the **owner** of the new org.

Each Enterprise account can own **1 organisation**.

## Invite teammates

1. From the org page, **Members → Invite**.
2. Enter email addresses. Pick a role per invite:
   * **Admin** — manage tools, members, settings; can't change billing.
   * **Member** — view, follow tools, acknowledge releases.
   * **Viewer** — read-only access to the org's tools and releases.

The **Owner** role belongs to whoever created the org (it controls billing and
can't be assigned via invite).

Invitees receive an email with a join link. They sign in (or sign up) and
are added on accept.

If a member is later removed, their personal account stays — they just lose
access to the org's tools and views.

## Share followed tools

Tools followed at the **organisation level** are visible to all members and
trigger notifications to all members (subject to each member's notification
preferences). This is separate from each member's personal followed list.

## Release acknowledgments

Each release notification has an **Acknowledge** button. When a member clicks
it, the acknowledgment is recorded against the org with the user + timestamp.

* Use it as a "we've seen this" marker for ops review.
* Acknowledgments improve the stack health score.
* They show up in the audit log.

You can also acknowledge from the Slack notification button — see
[Slack commands and buttons](./use-slack-commands).

## Stack Health Score

A per-org score (0–100) that reflects how on-top-of-things the team is. It's
calculated from unacknowledged releases, weighted by feature type:

* Security fixes: -10
* Breaking changes: -5
* Other notable changes: -1

Higher is better. Acknowledging releases brings the score back up. The score
is recomputed every 5 minutes (cached).

## Notification routing rules

Per-org, per-tool, per-feature-type rules — e.g. "post all `Security Fix`
features for `ingress-nginx` to `#sec-ops`, mark urgency `critical`". Set
them at **Org → Notifications → Rules**.

## Audit log

A full chronological log of org actions: tool follows/unfollows, member
joins/removals, plan changes, acknowledgments. CSV export is available.

Open it at **Org → Audit Log**. Each row links to the underlying release or
feature.

## Disconnect / delete

* **Remove a member**: Members → ⋯ → Remove. Soft-deleted (kept for audit).
* **Leave the org as a member**: Members → ⋯ → Leave.
* **Delete the org** (owner): Settings → Danger zone → Delete. Irreversible.

## Related

* [Plans and limits](../reference/plans) — what's included on Enterprise
* [Connect Slack](./connect-slack) — recommended for orgs
* [Use Slack commands and buttons](./use-slack-commands)