patch(docs): Change plans in docs (#637)

VeljkoMaksimovic · web-flow · commit a57dc42adebc · 2025-10-09T23:52:38.000+02:00
## 📝 Description https://github.com/renderedtext/tasks/issues/8713 ## ✅ Checklist - [x] I have tested this change - [ ] This change requires documentation update
diff --git a/docs/docs-contributing/STYLE_GUIDE.md b/docs/docs-contributing/STYLE_GUIDE.md
@@ -299,7 +299,7 @@ You can pass an array of plans instead.
 
 ```js
 // Renders as: Available on Semaphore Cloud: Startup Scalup
-<Available  plans={['Startup','Scaleup']}/>
+<Available  plans={['Cloud','Enterprise']}/>
 ```
 
 ### Toggleable content
diff --git a/docs/docs/reference/agent-aws-stack.md b/docs/docs/reference/agent-aws-stack.md
@@ -4,7 +4,7 @@ description: AWS Autoscaler for self-hosted reference
 
 # AWS Autoscaler Settings
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 This page describes all the settings available to configure [AWS Autoscaler Stack](../using-semaphore/self-hosted-aws).
 
diff --git a/docs/docs/reference/audit-events.md b/docs/docs/reference/audit-events.md
@@ -4,7 +4,7 @@ description: Audit log events reference
 
 # Audit Log Events Reference
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Each audit log entry shows applicable information about an event, such as:
 
diff --git a/docs/docs/reference/openid.md b/docs/docs/reference/openid.md
@@ -6,7 +6,7 @@ description: OpenID Connect (OIDC) token reference
 
 This page describes how [OpenID Connect (OIDC)](../using-semaphore/openid) tokens are generated.
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 ## Reference
 
diff --git a/docs/docs/reference/secret-yaml.md b/docs/docs/reference/secret-yaml.md
@@ -51,9 +51,9 @@ This is a required field for project-level secrets. It must contain either the p
 
 ## org_config {#org-config}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
-The `org_config` property holds organization access policy fields, which are enabled for organizations on a Startup plan or higher. 
+The `org_config` property holds organization access policy fields, which are enabled for organizations on a Cloud plan or higher. 
 
 This property can contain the following:
 
diff --git a/docs/docs/reference/self-hosted-config.md b/docs/docs/reference/self-hosted-config.md
@@ -4,7 +4,7 @@ description: Self-hosted agents configuration reference
 
 # Self-hosted Agents Settings
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 This page describes all the settings available to configure [self-hosted agents](../using-semaphore/self-hosted).
 
diff --git a/docs/docs/using-semaphore/okta.md b/docs/docs/using-semaphore/okta.md
@@ -10,7 +10,7 @@ Use Okta to provision, manage your user, and provide Single Sign On (SSO) to you
 
 ## Overview
 
-<Available plans={['Scaleup']} />
+<Available plans={['Enterprise']} />
 
 [Okta](https://okta.com) is an enterprise identity management platform. It provides a centralized place to manage your users and groups across different products. You can integrate Okta with Semaphore to manage your users from the Okta application.
 
diff --git a/docs/docs/using-semaphore/openid.md b/docs/docs/using-semaphore/openid.md
@@ -8,7 +8,7 @@ OpenID Connect (OIDC) allows you to establish a more secure trust relationship b
 
 ## Overview
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Semaphore users traditionally use [secrets](./secrets) to inject credentials or API keys in jobs that need to interact with cloud providers. Every time the CI pipeline needs to deploy an application or fetch resources from a Docker registry or S3 bucket, we need to supply a secret to authorize Semaphore to access your cloud.
 
diff --git a/docs/docs/using-semaphore/org-health.md b/docs/docs/using-semaphore/org-health.md
@@ -6,7 +6,7 @@ description: Overview of all your projects
 
 <VideoTutorial title="How to use Organization Health dashboard" src="https://www.youtube.com/embed/2JVsH3DJccE?si=Xq_U0yWhryBsioDv" />
 
-<Available plans={['ScaleUp']} />
+<Available plans={['Enterprise']} />
 
 The Organization Health dashboard summarizes all your [Project Insights](./insights) in a single place.
 
diff --git a/docs/docs/using-semaphore/org-preflight.md b/docs/docs/using-semaphore/org-preflight.md
@@ -5,7 +5,7 @@ title: Preflight Checks
 
 # Preflight Checks for Organizations
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Pre-flight checks are user-defined commands executed before the pipeline begins as part of the [pipeline initialization job](./pipelines#init-job). This page explains how to use this feature and shows some examples.
 
diff --git a/docs/docs/using-semaphore/organizations.md b/docs/docs/using-semaphore/organizations.md
@@ -127,7 +127,7 @@ See [organization roles](./rbac#org) to learn what roles are available.
 
 ### How to create groups {#add-groups}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 User groups streamline user management by allowing bulk actions. After creating a group, you can:
 
@@ -196,7 +196,7 @@ The actions with enabled checkbox are allowed for that role.
 
 ### How to create custom roles {#custom}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Create custom roles to give your users the precise permissions they need. 
 
@@ -269,7 +269,7 @@ If you experience errors during initialization, see the [initialization job logs
 
 ### Okta integration {#okta-integration}
 
-<Available plans={['Scaleup']} />
+<Available plans={['Enterprise']} />
 
 Integration with Okta allows you to automate user management within your Semaphore organization, as well as to use Okta apps for Single Sign On.
 
@@ -289,7 +289,7 @@ In this section, you can add contact details in case the Semaphore Support Team
 
 <VideoTutorial title="How to view audit logs" src="https://www.youtube.com/embed/o5yXSvjcz7s"/>
 
-<Available plans={['Scaleup']} />
+<Available plans={['Enterprise']} />
 
 To support compliance, accountability, and security, Semaphore provides logs of audited events. Audit Log events are events that affect your organization, projects, users, or any other resources in Semaphore. Events contain information about when who and what was the performed activity.
 
@@ -303,7 +303,7 @@ The audit logs shows all the [audited events](../reference/audit-events) in reve
 
 ### How to export audit logs {#audit-export}
 
-<Available plans={['Scaleup']} />
+<Available plans={['Enterprise']} />
 
 Audit logs can be exported in two ways:
 
diff --git a/docs/docs/using-semaphore/projects.md b/docs/docs/using-semaphore/projects.md
@@ -193,9 +193,9 @@ Users can be granted access and permissions on a project by different means:
 
 ### How to manually add/remove members to projects {#manual}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
-Scaleup plan users can manually add and remove people from a project. To manage users, open your project and go to the **People** tab
+Enterprise plan users can manually add and remove people from a project. To manage users, open your project and go to the **People** tab
 
 <Steps>
 
@@ -212,7 +212,7 @@ See [project roles](./rbac#project) for more information on what actions can eac
 
 ### How to change permissions {#people-roles}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Open your project and go to the **People** tab
 
@@ -243,7 +243,7 @@ The actions with enabled checkbox are allowed for that role.
 
 ### How to create custom roles {#custom-roles}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Create custom roles to give your users the precise permissions they need. 
 
@@ -387,7 +387,7 @@ To learn more, see the [artifacts retention page](./artifacts#retention)
 
 ## Pre-flight checks {#preflight}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Pre-flight checks are user-defined commands executed before the pipeline begins as part of the pipeline [initialization job](./pipelines#init-job). These checks allow you to define the type of agent running the initialization job and to manually run commands before a pipeline starts.
 
diff --git a/docs/docs/using-semaphore/promotions.md b/docs/docs/using-semaphore/promotions.md
@@ -555,7 +555,7 @@ Credentials are optional. Go to the next step if you don't need them.
 
 ### Granular permissions {#granular-permissions}
 
-<Available plans={['Scaleup']} />
+<Available plans={['Enterprise']} />
 
 In the "Who can deploy?" section, you can define the users and roles that can manually start the promotion. Granular permissions are optional. You can go to the next section if you don't need to restrict access to the promotion.
 
diff --git a/docs/docs/using-semaphore/rbac.md b/docs/docs/using-semaphore/rbac.md
@@ -86,7 +86,7 @@ To remove an owner, see [how to remove an owner](https://docs.semaphore.io/using
 
 ### Organization groups {#org-groups}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Your organization can have any number of groups. A group can have exactly one role directly assigned.
 
@@ -145,7 +145,7 @@ Admins have the authority to modify any setting within the projects, including t
 
 ## Custom roles {#custom-roles}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 In addition to the pre-defined roles provided by Semaphore, you can create your own custom roles. Custom roles let you follow the principle of least privilege when managing using permissions.
 
diff --git a/docs/docs/using-semaphore/secrets.md b/docs/docs/using-semaphore/secrets.md
@@ -144,7 +144,7 @@ To create secrets with the Semaphore API, see the [API reference](../reference/a
 
 <VideoTutorial title="How to configure secret access policy" src="https://www.youtube.com/embed/gB1Oat4HwTo?si=_dvCKllE0bPgtDFe" />
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Access policies allow you to control how and who can use [organization secrets](#org-secrets). 
 
@@ -163,7 +163,7 @@ You can apply a policy at three levels:
 
 ## How to create project secrets {#create-project-secrets}
 
-<Available plans={['Startup']}/>
+<Available plans={['Cloud']}/>
 
 Project secrets are only available to the [project](./projects) they are tied to.
 
diff --git a/docs/docs/using-semaphore/self-hosted-aws.md b/docs/docs/using-semaphore/self-hosted-aws.md
@@ -4,7 +4,7 @@ description: Deploy an autoscaling fleet of self-hosted agents in AWS
 
 # Autoscaling with AWS
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 Semaphore provides the open-source [AWS agent stack](https://github.com/renderedtext/agent-aws-stack) to help you deploy an autoscaling fleet of self-hosted agents in AWS.
 
diff --git a/docs/docs/using-semaphore/self-hosted-configure.md b/docs/docs/using-semaphore/self-hosted-configure.md
@@ -4,7 +4,7 @@ description: Configure self-hosted agents
 
 # Configure Agents
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 Self-hosted agents allow you to run Semaphore jobs on your own hardware. This page explains the configuration settings available and how to enable additional features.
 
diff --git a/docs/docs/using-semaphore/self-hosted-install.md b/docs/docs/using-semaphore/self-hosted-install.md
@@ -4,7 +4,7 @@ description: Install self-hosted agent stack in your machines
 
 # Install Agents
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 ## Overview
 
diff --git a/docs/docs/using-semaphore/self-hosted.md b/docs/docs/using-semaphore/self-hosted.md
@@ -8,7 +8,7 @@ description: Run jobs on your hardware
 
 ## Overview {#overview}
 
-<Available plans={['Startup (Hybrid)', 'Scaleup (Hybrid)']}/>
+<Available plans={['Hybrid', 'Enterprise']}/>
 
 An [agent](./pipelines#agents) is a physical or virtual machine you own that can be dedicated to running Semaphore [jobs](./jobs). You can mix and match your own agents with the [machines provided by Semaphore](../reference/machine-types).
 
diff --git a/docs/versioned_docs/version-CE-1.3/reference/secret-yaml.md b/docs/versioned_docs/version-CE-1.3/reference/secret-yaml.md
@@ -56,9 +56,9 @@ This is a required field for project-level secrets. It must contain either the p
 
 ## org_config {#org-config}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
-The `org_config` property holds server access policy fields, which are enabled for server on a Startup plan or higher. 
+The `org_config` property holds server access policy fields, which are enabled for server on a Cloud plan or higher. 
 
 This property can contain the following:
 
diff --git a/docs/versioned_docs/version-CE-1.3/using-semaphore/secrets.md b/docs/versioned_docs/version-CE-1.3/using-semaphore/secrets.md
@@ -144,7 +144,7 @@ To create secrets with the Semaphore API, see the [API reference](../reference/a
 
 ## How to create project secrets {#create-project-secrets}
 
-<Available plans={['Startup']}/>
+<Available plans={['Cloud']}/>
 
 Project secrets are only available to the [project](./projects) they are tied to.
 
diff --git a/docs/versioned_docs/version-CE/reference/secret-yaml.md b/docs/versioned_docs/version-CE/reference/secret-yaml.md
@@ -56,9 +56,9 @@ This is a required field for project-level secrets. It must contain either the p
 
 ## org_config {#org-config}
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
-The `org_config` property holds server access policy fields, which are enabled for server on a Startup plan or higher. 
+The `org_config` property holds server access policy fields, which are enabled for server on a Cloud plan or higher. 
 
 This property can contain the following:
 
diff --git a/docs/versioned_docs/version-EE-1.3/reference/openid.md b/docs/versioned_docs/version-EE-1.3/reference/openid.md
@@ -11,7 +11,7 @@ description: OpenID Connect (OIDC) token reference
 
 This page describes how [OpenID Connect (OIDC)](../using-semaphore/openid) tokens are generated.
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 ## Reference
 
diff --git a/docs/versioned_docs/version-EE-1.3/reference/secret-yaml.md b/docs/versioned_docs/version-EE-1.3/reference/secret-yaml.md
@@ -56,7 +56,7 @@ This is a required field for project-level secrets. It must contain either the p
 
 ## org_config {#org-config}
 
-The `org_config` property holds server access policy fields, which are enabled for server on a Startup plan or higher. 
+The `org_config` property holds server access policy fields, which are enabled for server on a Cloud plan or higher. 
 
 This property can contain the following:
 
diff --git a/docs/versioned_docs/version-EE-1.3/using-semaphore/openid.md b/docs/versioned_docs/version-EE-1.3/using-semaphore/openid.md
@@ -14,7 +14,7 @@ OpenID Connect (OIDC) allows you to establish a more secure trust relationship b
 
 ## Overview
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Semaphore users traditionally use [secrets](./secrets) to inject credentials or API keys in jobs that need to interact with cloud providers. Every time the CI pipeline needs to deploy an application or fetch resources from a Docker registry or S3 bucket, we need to supply a secret to authorize Semaphore to access your cloud.
 
diff --git a/docs/versioned_docs/version-EE/reference/openid.md b/docs/versioned_docs/version-EE/reference/openid.md
@@ -11,7 +11,7 @@ description: OpenID Connect (OIDC) token reference
 
 This page describes how [OpenID Connect (OIDC)](../using-semaphore/openid) tokens are generated.
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 ## Reference
 
diff --git a/docs/versioned_docs/version-EE/reference/secret-yaml.md b/docs/versioned_docs/version-EE/reference/secret-yaml.md
@@ -56,7 +56,7 @@ This is a required field for project-level secrets. It must contain either the p
 
 ## org_config {#org-config}
 
-The `org_config` property holds server access policy fields, which are enabled for server on a Startup plan or higher. 
+The `org_config` property holds server access policy fields, which are enabled for server on Cloud plan or higher. 
 
 This property can contain the following:
 
diff --git a/docs/versioned_docs/version-EE/using-semaphore/openid.md b/docs/versioned_docs/version-EE/using-semaphore/openid.md
@@ -14,7 +14,7 @@ OpenID Connect (OIDC) allows you to establish a more secure trust relationship b
 
 ## Overview
 
-<Available plans={['Scaleup']}/>
+<Available plans={['Enterprise']}/>
 
 Semaphore users traditionally use [secrets](./secrets) to inject credentials or API keys in jobs that need to interact with cloud providers. Every time the CI pipeline needs to deploy an application or fetch resources from a Docker registry or S3 bucket, we need to supply a secret to authorize Semaphore to access your cloud.
 
