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

# Organizations

> Organizations are the top-level tenant in nOps. Manage settings, domains, subscription tiers, SAML/SCIM, and audit logs for your team.

## Overview

An **organization** is the top-level boundary in nOps. All users, canvases, integrations, and cost data belong to an organization. Each organization maps to an internal **nOps Client ID** that isolates your data from every other tenant on the platform.

When you first sign up, nOps creates an organization for you. Administrators can then configure settings, invite users, connect cloud providers, and enable enterprise security features.

## Organization settings

Administrators can manage the following from **Settings** in the nOps dashboard:

| Setting                | Description                                                                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Name**               | The display name for your organization (editable).                                                                                 |
| **Domain and Slug**    | Your organization's verified domain and URL-friendly identifier (read-only).                                                       |
| **Available Products** | The nOps products enabled for your account (read-only).                                                                            |
| **Plugins**            | [Clara MCP](/plugins/clara-mcp) connectors and the [Clara Slack agent](/plugins/clara-slack-agent) — under **Settings → Plugins**. |

## Enterprise identity

nOps supports enterprise identity management through SAML and SCIM.

<Note>
  Setting up SSO and SCIM requires the **Inform** plan. See [Security and authentication](/platform/security-and-auth#setting-up-sso) for the full setup flow.
</Note>

<AccordionGroup>
  <Accordion title="SAML single sign-on">
    Enable SAML SSO to let your team sign in through your identity provider (Okta, Azure AD, Google Workspace, and others). Once enabled, nOps provides an **ACS URL** and **Entity ID** that you configure in your IdP.

    Administrators can also **enforce SSO** so that email/password and social logins are disabled for the organization.
  </Accordion>

  <Accordion title="SCIM provisioning">
    Enable SCIM to automatically sync user accounts from your identity provider. When a user is added or removed in your IdP, the change is reflected in nOps within minutes.
  </Accordion>
</AccordionGroup>

## Roles and data scopes

Beyond who can sign in, administrators can control what each role can see and do. Roles carry both feature permissions and, optionally, a **data scope** that limits which cost data a role can access — see [Roles and data scopes](/platform/roles-and-data-scopes) for details.

## Auth policies

Every organization has authentication policies that control MFA requirements, SSO enforcement, session duration, and password rules. These are set to secure defaults for every organization; contact nOps support if you need a policy changed for your organization. See [Security and authentication](/platform/security-and-auth#auth-policies) for the full list and current defaults.

## Audit logs

nOps records key actions taken within your organization — user sign-ins, role changes, integration modifications, and more. Administrators can view and export audit logs from **Settings > Security**.

## Switching organizations

If your account belongs to multiple organizations, you can switch between them from the organization picker in the top navigation. The active organization determines which data, canvases, and integrations you see.

***

<Card title="Next: Users and roles" icon="arrow-right" href="/platform/users">
  Learn how to manage team members, assign roles, and control access with permissions.
</Card>