{
  "doc": {
    "id": "cloud/account-management/organizations",
    "title": "Organizations in Cypress Cloud: how to manage application quality at scale",
    "description": "Cypress Cloud organizations group your projects, users, teams, billing, and integrations in one place to manage application quality and access control at scale.",
    "section": "cloud",
    "source_path": "/llm/markdown/cloud/account-management/organizations.md",
    "version": "8d4bb7c9d1af182786c46b47bac667515b9e5d39",
    "updated_at": "2026-08-07T13:17:53.464Z",
    "headings": [
      {
        "id": "cloud/account-management/organizations#cypress-cloud-organizations",
        "text": "Cypress Cloud Organizations",
        "level": 1
      },
      {
        "id": "cloud/account-management/organizations#why-use-organizations",
        "text": "Why use organizations",
        "level": 2
      },
      {
        "id": "cloud/account-management/organizations#whats-in-an-organization",
        "text": "What's in an organization",
        "level": 2
      },
      {
        "id": "cloud/account-management/organizations#manage-your-organization",
        "text": "Manage your organization",
        "level": 2
      },
      {
        "id": "cloud/account-management/organizations#create-organization",
        "text": "Create organization",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#organization-id",
        "text": "Organization ID",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#manage-cloud-ai",
        "text": "Manage Cloud AI",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#member-privileges",
        "text": "Member privileges",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#transfer-an-organization-to-another-owner",
        "text": "Transfer an organization to another owner",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#delete-organization",
        "text": "Delete organization",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#integrations",
        "text": "Integrations",
        "level": 2
      },
      {
        "id": "cloud/account-management/organizations#ai-coding-assistants",
        "text": "AI coding assistants",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#enterprise-data-and-reporting",
        "text": "Enterprise data and reporting",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#source-control-providers",
        "text": "Source control providers",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#issue-management",
        "text": "Issue management",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#team-communication",
        "text": "Team communication",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#single-sign-on-sso-authentication",
        "text": "Single Sign-On (SSO) authentication",
        "level": 3
      },
      {
        "id": "cloud/account-management/organizations#see-also",
        "text": "See also",
        "level": 2
      }
    ]
  },
  "chunks": [
    {
      "id": "cloud/account-management/organizations#why-use-organizations",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Why use organizations",
      "heading_level": 2,
      "content_markdown": "## Why use organizations\n\n*   **Group related work.** Keep all of a team, business unit, or company's projects together so results, [enterprise analytics](/llm/markdown/cloud/features/analytics/enterprise-reporting.md), and usage roll up in one place.\n*   **Control who sees what.** Combine [user roles](/llm/markdown/cloud/account-management/users.md#User-roles) and [teams](/llm/markdown/cloud/account-management/teams.md) to give each person access to exactly the projects they need, no more, no less.\n*   **Govern AI and security centrally.** Turn [Cloud AI](#Manage-Cloud-AI) on or off for everyone at once, and enforce [single sign-on (SSO)](/llm/markdown/cloud/account-management/enterprise-sso.md) so access follows your identity provider.\n*   **Connect your existing tools.** Wire up source control, issue tracking, and chat once at the org level so every project benefits from status checks, notifications, and linked tickets.\n*   **Understand cost and usage.** Track [billing and usage](/llm/markdown/cloud/account-management/billing-and-usage.md) across all projects so you can plan capacity and attribute spend.\n",
      "section": "cloud",
      "anchors": [
        "why-use-organizations"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 175
    },
    {
      "id": "cloud/account-management/organizations#whats-in-an-organization",
      "doc_id": "cloud/account-management/organizations",
      "heading": "What's in an organization",
      "heading_level": 2,
      "content_markdown": "## What's in an organization\n\nAn organization brings several areas of Cypress Cloud together. Each one has its own dedicated guide:\n\n*   **[Projects](/llm/markdown/cloud/account-management/projects.md)** organize your recorded runs. A new organization starts with a \"Default Project\" that you can rename and configure in [Project Settings](/llm/markdown/cloud/account-management/projects.md#Project-settings), and you can add as many projects as you need.\n*   **[Users](/llm/markdown/cloud/account-management/users.md)** and **[teams](/llm/markdown/cloud/account-management/teams.md)** control who can access what. Inviting users gives them shared visibility into test health, while [roles](/llm/markdown/cloud/account-management/users.md#User-roles) grant each person access to exactly the projects they need, no more, no less. This is what lets multiple business units share one organization, and lets you understand usage per team through [Enterprise Reporting](/llm/markdown/cloud/features/analytics/enterprise-reporting.md).\n*   **[Billing and usage](/llm/markdown/cloud/account-management/billing-and-usage.md)** rolls up across every project so you can review your plan, track usage, and attribute spend in one place.\n*   **[Integrations](#Integrations)** connect Cypress to the source control, issue tracking, and chat tools your team already uses, set up once and applied across every project.\n",
      "section": "cloud",
      "anchors": [
        "whats-in-an-organization"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 208
    },
    {
      "id": "cloud/account-management/organizations#manage-your-organization",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Manage your organization",
      "heading_level": 2,
      "content_markdown": "## Manage your organization\n\n### Create organization\n\nCreating an organization gives your team a shared, persistent place to record runs and review quality together, rather than scattering results across individual accounts. You can create an organization from within [Cypress Cloud](https://on.cypress.io/cloud) by opening the organization switcher and clicking **Create new organization**.\n\n### Organization ID\n\nEvery organization has a unique identifier. This ID is how Cypress teams reference your organization, so having it handy makes it faster to get help, report an issue, or discuss your plan.\n\nTo locate your Organization's ID, go to **Organization settings** then **Organization ID**. Click on the clipboard icon to copy the ID for easy sharing with Cypress teams.\n\n### Manage Cloud AI\n\nManaging AI at the organization level means you make one decision and it applies to everyone. This is useful both for teams that want AI assistance everywhere and for those with policies that require it to be off.\n\n[Cloud AI](/llm/markdown/cloud/faq.md#What-is-Cloud-AI) is enabled by default for all users on any Cloud plan, and powers [AI features](/llm/markdown/cloud/features/cypress-ai-features.md) like test authoring, error summaries, and test analysis. Organization admins and owners can enable or disable these AI capabilities for their entire organization from the organization settings.\n\n### Member privileges\n\nMember privileges let owners and admins decide how much non-admin members can do at the organization level, so you can keep sensitive actions with your administrators without restricting day-to-day work.\n\nToday this controls **public project creation**. [Public projects](/llm/markdown/cloud/account-management/projects.md#Public-vs-Private) are visible to anyone on the internet, so you may want to limit who can create them:\n\n*   **Only admins:** only organization admins and owners can create public projects. Members can still create private projects, but cannot expose runs publicly.\n*   **Any member:** anyone in the organization can create public projects. This is the default.\n\nAdjust this under **Organization settings > Member Privileges**, then click **Update** to save.\n\n### Transfer an organization to another owner\n\nThere is no single \"transfer organization\" button. Instead, you transfer ownership by giving the **Owner** role to another user in the organization. An organization can have more than one owner, so the new owner gains full control while you decide whether to keep or step back from your own access.\n\nOnly an existing [owner](/llm/markdown/cloud/account-management/users.md#User-roles) can grant the Owner role.\n\n1.  Make sure the person is already a [user in your organization](/llm/markdown/cloud/account-management/users.md#Invite-users). If they are not, invite them first.\n2.  Go to **Users & Teams** and select the **Users** tab.\n3.  Find the user, edit their role, and set it to **Owner**.\n4.  The user now has full owner permissions over the organization.\n\nIf you no longer want to be an owner after the transfer, the new owner (or you) can lower your role to **Admin** or remove you from the organization. At least one owner must always remain.\n\n### Delete organization\n\nWhen an organization is no longer needed, removing it keeps your Cypress Cloud account tidy and ensures projects live where they belong. You can delete organizations that you own as long as they do not have any projects or an active subscription. You must first [delete](/llm/markdown/cloud/account-management/projects.md#Delete-Project) or [transfer ownership](/llm/markdown/cloud/account-management/projects.md#Transfer-ownership) of your projects to another organization before you can delete the organization.\n\nAn organization with an active subscription cannot be deleted. If you need to delete an organization that still has an active subscription, contact [support@cypress.io](mailto:support@cypress.io).\n",
      "section": "cloud",
      "anchors": [
        "manage-your-organization"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 733
    },
    {
      "id": "cloud/account-management/organizations#create-organization",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Create organization",
      "heading_level": 3,
      "content_markdown": "### Create organization\n\nCreating an organization gives your team a shared, persistent place to record runs and review quality together, rather than scattering results across individual accounts. You can create an organization from within [Cypress Cloud](https://on.cypress.io/cloud) by opening the organization switcher and clicking **Create new organization**.\n",
      "section": "cloud",
      "anchors": [
        "create-organization"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 61
    },
    {
      "id": "cloud/account-management/organizations#organization-id",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Organization ID",
      "heading_level": 3,
      "content_markdown": "### Organization ID\n\nEvery organization has a unique identifier. This ID is how Cypress teams reference your organization, so having it handy makes it faster to get help, report an issue, or discuss your plan.\n\nTo locate your Organization's ID, go to **Organization settings** then **Organization ID**. Click on the clipboard icon to copy the ID for easy sharing with Cypress teams.\n",
      "section": "cloud",
      "anchors": [
        "organization-id"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 83
    },
    {
      "id": "cloud/account-management/organizations#manage-cloud-ai",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Manage Cloud AI",
      "heading_level": 3,
      "content_markdown": "### Manage Cloud AI\n\nManaging AI at the organization level means you make one decision and it applies to everyone. This is useful both for teams that want AI assistance everywhere and for those with policies that require it to be off.\n\n[Cloud AI](/llm/markdown/cloud/faq.md#What-is-Cloud-AI) is enabled by default for all users on any Cloud plan, and powers [AI features](/llm/markdown/cloud/features/cypress-ai-features.md) like test authoring, error summaries, and test analysis. Organization admins and owners can enable or disable these AI capabilities for their entire organization from the organization settings.\n",
      "section": "cloud",
      "anchors": [
        "manage-cloud-ai"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 115
    },
    {
      "id": "cloud/account-management/organizations#member-privileges",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Member privileges",
      "heading_level": 3,
      "content_markdown": "### Member privileges\n\nMember privileges let owners and admins decide how much non-admin members can do at the organization level, so you can keep sensitive actions with your administrators without restricting day-to-day work.\n\nToday this controls **public project creation**. [Public projects](/llm/markdown/cloud/account-management/projects.md#Public-vs-Private) are visible to anyone on the internet, so you may want to limit who can create them:\n\n*   **Only admins:** only organization admins and owners can create public projects. Members can still create private projects, but cannot expose runs publicly.\n*   **Any member:** anyone in the organization can create public projects. This is the default.\n\nAdjust this under **Organization settings > Member Privileges**, then click **Update** to save.\n",
      "section": "cloud",
      "anchors": [
        "member-privileges"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 145
    },
    {
      "id": "cloud/account-management/organizations#transfer-an-organization-to-another-owner",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Transfer an organization to another owner",
      "heading_level": 3,
      "content_markdown": "### Transfer an organization to another owner\n\nThere is no single \"transfer organization\" button. Instead, you transfer ownership by giving the **Owner** role to another user in the organization. An organization can have more than one owner, so the new owner gains full control while you decide whether to keep or step back from your own access.\n\nOnly an existing [owner](/llm/markdown/cloud/account-management/users.md#User-roles) can grant the Owner role.\n\n1.  Make sure the person is already a [user in your organization](/llm/markdown/cloud/account-management/users.md#Invite-users). If they are not, invite them first.\n2.  Go to **Users & Teams** and select the **Users** tab.\n3.  Find the user, edit their role, and set it to **Owner**.\n4.  The user now has full owner permissions over the organization.\n\nIf you no longer want to be an owner after the transfer, the new owner (or you) can lower your role to **Admin** or remove you from the organization. At least one owner must always remain.\n",
      "section": "cloud",
      "anchors": [
        "transfer-an-organization-to-another-owner"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 207
    },
    {
      "id": "cloud/account-management/organizations#delete-organization",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Delete organization",
      "heading_level": 3,
      "content_markdown": "### Delete organization\n\nWhen an organization is no longer needed, removing it keeps your Cypress Cloud account tidy and ensures projects live where they belong. You can delete organizations that you own as long as they do not have any projects or an active subscription. You must first [delete](/llm/markdown/cloud/account-management/projects.md#Delete-Project) or [transfer ownership](/llm/markdown/cloud/account-management/projects.md#Transfer-ownership) of your projects to another organization before you can delete the organization.\n\nAn organization with an active subscription cannot be deleted. If you need to delete an organization that still has an active subscription, contact [support@cypress.io](mailto:support@cypress.io).\n",
      "section": "cloud",
      "anchors": [
        "delete-organization"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 117
    },
    {
      "id": "cloud/account-management/organizations#integrations",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Integrations",
      "heading_level": 2,
      "content_markdown": "## Integrations\n\nIntegrations are where an organization delivers value beyond Cypress Cloud itself: by connecting the tools your team already uses, your test results, [flaky test insights](/llm/markdown/cloud/features/flaky-test-management.md), [UI Coverage](/llm/markdown/ui-coverage/get-started/introduction.md), and [Accessibility](/llm/markdown/accessibility/get-started/introduction.md) findings show up where work actually happens. Set integrations up once at the org level and every project benefits: failing code is kept out of your main branch, failures are linked to tickets, and the right people are notified automatically.\n\nOwner and admin roles can configure these under **Organization > Integrations**, and adjust the settings from within the **Project settings** page.\n\nCypress Cloud integrates with AI coding assistants, enterprise data and reporting, source control providers, issue management, team communication, and single sign-on (SSO). Explore the guides for each below to learn how to set them up.\n\n### AI coding assistants\n\nGive your AI coding assistants and agents real-time context on your application's health by connecting them to the [Cypress Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md) server, so they can query run results, analyze failures, and audit flaky tests without manual copy-paste.\n\n*   [Cypress Cloud MCP guide](/llm/markdown/cloud/integrations/cloud-mcp.md)\n\nPair Cloud MCP with [Cypress AI Skills](/llm/markdown/app/tooling/ai-skills.md), ready-made instruction sets that teach your AI tool common Cypress workflow patterns, so it writes and debugs tests the Cypress way.\n\n### Enterprise data and reporting\n\nGenerate an API key to pull your enterprise test data, such as run status, spec results, run durations, and flaky test rates, into your own reporting and business intelligence tools.\n\n*   [Data Extract API guide](/llm/markdown/cloud/integrations/data-extract-api.md)\n\n### Source control providers\n\nConnect your repository to surface test results directly in pull requests and block failing code from merging with status checks, so regressions are caught before they reach your main branch.\n\n*   [GitHub integration guide](/llm/markdown/cloud/integrations/github.md)\n*   [GitLab integration guide](/llm/markdown/cloud/integrations/gitlab.md)\n*   [Bitbucket integration guide](/llm/markdown/cloud/integrations/bitbucket.md)\n*   [GitHub Enterprise integration guide](/llm/markdown/cloud/integrations/github.md#GitHub-Enterprise)\n*   [GitLab for Enterprise integration guide](/llm/markdown/cloud/integrations/gitlab.md#GitLab-for-Enterprise-Self-managed)\n\n### Issue management\n\nTurn test failures into tracked, actionable work by creating bidirectionally linked tickets, so nothing slips through the cracks.\n\n*   [Jira integration guide](/llm/markdown/cloud/integrations/jira.md)\n\n### Team communication\n\nKeep your team informed in real time by sending run progress and results to the channels they already watch, so failures get attention without anyone refreshing a dashboard.\n\n*   [Slack integration guide](/llm/markdown/cloud/integrations/slack.md)\n*   [Microsoft Teams integration guide](/llm/markdown/cloud/integrations/microsoft-teams.md)\n\n### Single Sign-On (SSO) authentication\n\nEnforce access through your existing identity provider so the right people get in, offboarding is automatic, and you meet your organization's security requirements.\n\n*   [Okta integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#Okta)\n*   [SAML integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#SAML)\n*   [Azure AD integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#Azure-AD)\n*   [OneLogin integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#OneLogin)\n",
      "section": "cloud",
      "anchors": [
        "integrations"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 544
    },
    {
      "id": "cloud/account-management/organizations#ai-coding-assistants",
      "doc_id": "cloud/account-management/organizations",
      "heading": "AI coding assistants",
      "heading_level": 3,
      "content_markdown": "### AI coding assistants\n\nGive your AI coding assistants and agents real-time context on your application's health by connecting them to the [Cypress Cloud MCP](/llm/markdown/cloud/integrations/cloud-mcp.md) server, so they can query run results, analyze failures, and audit flaky tests without manual copy-paste.\n\n*   [Cypress Cloud MCP guide](/llm/markdown/cloud/integrations/cloud-mcp.md)\n\nPair Cloud MCP with [Cypress AI Skills](/llm/markdown/app/tooling/ai-skills.md), ready-made instruction sets that teach your AI tool common Cypress workflow patterns, so it writes and debugs tests the Cypress way.\n",
      "section": "cloud",
      "anchors": [
        "ai-coding-assistants"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 99
    },
    {
      "id": "cloud/account-management/organizations#enterprise-data-and-reporting",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Enterprise data and reporting",
      "heading_level": 3,
      "content_markdown": "### Enterprise data and reporting\n\nGenerate an API key to pull your enterprise test data, such as run status, spec results, run durations, and flaky test rates, into your own reporting and business intelligence tools.\n\n*   [Data Extract API guide](/llm/markdown/cloud/integrations/data-extract-api.md)\n",
      "section": "cloud",
      "anchors": [
        "enterprise-data-and-reporting"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 53
    },
    {
      "id": "cloud/account-management/organizations#source-control-providers",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Source control providers",
      "heading_level": 3,
      "content_markdown": "### Source control providers\n\nConnect your repository to surface test results directly in pull requests and block failing code from merging with status checks, so regressions are caught before they reach your main branch.\n\n*   [GitHub integration guide](/llm/markdown/cloud/integrations/github.md)\n*   [GitLab integration guide](/llm/markdown/cloud/integrations/gitlab.md)\n*   [Bitbucket integration guide](/llm/markdown/cloud/integrations/bitbucket.md)\n*   [GitHub Enterprise integration guide](/llm/markdown/cloud/integrations/github.md#GitHub-Enterprise)\n*   [GitLab for Enterprise integration guide](/llm/markdown/cloud/integrations/gitlab.md#GitLab-for-Enterprise-Self-managed)\n",
      "section": "cloud",
      "anchors": [
        "source-control-providers"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 76
    },
    {
      "id": "cloud/account-management/organizations#team-communication",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Team communication",
      "heading_level": 3,
      "content_markdown": "### Team communication\n\nKeep your team informed in real time by sending run progress and results to the channels they already watch, so failures get attention without anyone refreshing a dashboard.\n\n*   [Slack integration guide](/llm/markdown/cloud/integrations/slack.md)\n*   [Microsoft Teams integration guide](/llm/markdown/cloud/integrations/microsoft-teams.md)\n",
      "section": "cloud",
      "anchors": [
        "team-communication"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 53
    },
    {
      "id": "cloud/account-management/organizations#single-sign-on-sso-authentication",
      "doc_id": "cloud/account-management/organizations",
      "heading": "Single Sign-On (SSO) authentication",
      "heading_level": 3,
      "content_markdown": "### Single Sign-On (SSO) authentication\n\nEnforce access through your existing identity provider so the right people get in, offboarding is automatic, and you meet your organization's security requirements.\n\n*   [Okta integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#Okta)\n*   [SAML integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#SAML)\n*   [Azure AD integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#Azure-AD)\n*   [OneLogin integration guide](/llm/markdown/cloud/account-management/enterprise-sso.md#OneLogin)\n",
      "section": "cloud",
      "anchors": [
        "single-sign-on-sso-authentication"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 60
    },
    {
      "id": "cloud/account-management/organizations#see-also",
      "doc_id": "cloud/account-management/organizations",
      "heading": "See also",
      "heading_level": 2,
      "content_markdown": "## See also\n\n*   [Manage users](/llm/markdown/cloud/account-management/users.md) - invite users and configure roles and permissions\n*   [Manage teams](/llm/markdown/cloud/account-management/teams.md) - control which users can access which projects\n*   [Manage projects](/llm/markdown/cloud/account-management/projects.md) - configure project settings, record keys, and access\n*   [Billing & Usage](/llm/markdown/cloud/account-management/billing-and-usage.md) - review your plan, usage, and billing\n*   [Single Sign-On (SSO)](/llm/markdown/cloud/account-management/enterprise-sso.md) - configure single sign-on for your organization\n*   [Organization FAQ](/llm/markdown/cloud/faq.md#Cypress-Cloud-Account) - answers to common questions about organizations\n",
      "section": "cloud",
      "anchors": [
        "see-also"
      ],
      "path": "/llm/json/chunked/cloud/account-management/organizations.json",
      "token_estimate": 91
    }
  ]
}