You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docusaurus/docs/cloud/projects/settings.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,6 @@ The <Icon name="faders" /> *General* tab for the project-level settings enables
39
39
- the app's internal name for the project, which can be useful for debug & support purposes.
40
40
-*Strapi CMS license key*: to enable and use some CMS features directly on your Cloud project (see [Pricing page](https://strapi.io/pricing-self-hosted) to purchase a license).
41
41
42
-
:::note
43
-
If you don't see the Strapi CMS license key area, then it probably means that your subscription is a legacy one and does not support custom CMS license. Instead you already have one that is automatically included on your project.
44
-
:::
45
-
46
42
-*Connected Git repository*: to change the repository and branch used for your project (see [Modifying git repository & branch](#modifying-git-repository--branch)). Also allows to enable/disable the "deploy on push" option.
47
43
-*Delete project*: to permanently delete your Strapi Cloud project (see [Deleting Strapi Cloud project](#deleting-strapi-cloud-project)).
48
44
@@ -62,6 +58,20 @@ The project name is set at project creation (see [Project creation](/cloud/getti
62
58
2. In the dialog, write the new project name of your choice in the *Project name* textbox.
63
59
3. Click on the **Rename** button to confirm the project name modification.
64
60
61
+
#### Adding CMS license key
62
+
63
+
A CMS license key can be added and connected to a Strapi Cloud project to be able to use some features of Strapi CMS. The CMS features that will be accessible via the license key depend on the type of license that was purchases: please refer to the <ExternalLinktext="Strapi Pricing page"to="https://strapi.io/pricing-self-hosted"/> for more information and/or to purchase a license.
64
+
65
+
:::note
66
+
If you don't see the *Strapi CMS license key* section, it probably means that your subscription is a legacy one and does not support custom CMS licenses. It means that you already have one that is automatically included on your project.
67
+
:::
68
+
69
+
1. In the *Strapi CMS license key* section, click on the **Add license** button.
70
+
2. In the dialog, paste your license key in the field.
71
+
3. Click on **Save**.
72
+
73
+
To remove the Strapi CMS license from your Strapi Cloud project, you can click on the **Unlink license** button. This will also remove access and usage to the CMS features included in the previously added license.
74
+
65
75
#### Modifying git repository & branch
66
76
67
77
The GitHub or GitLab repository, branch and base directory for a Strapi Cloud project are by default chosen at the creation of the project (see [Creating a project](/cloud/getting-started/deployment)). After the project's creation, via the project's settings, it is possible to update the project's repository or switch to another git provider.
0 commit comments