diff --git a/qdrant-landing/content/documentation/cloud/qdrant-cloud-setup.md b/qdrant-landing/content/documentation/cloud-account-setup.md
similarity index 83%
rename from qdrant-landing/content/documentation/cloud/qdrant-cloud-setup.md
rename to qdrant-landing/content/documentation/cloud-account-setup.md
index 78b0469fc..3848999ea 100644
--- a/qdrant-landing/content/documentation/cloud/qdrant-cloud-setup.md
+++ b/qdrant-landing/content/documentation/cloud-account-setup.md
@@ -1,7 +1,9 @@
---
title: Account Setup
-weight: 10
+weight: 13
+partition: cloud
aliases:
+ - /documentation/cloud/qdrant-cloud-setup/
---
# Setting up a Qdrant Cloud Account
@@ -23,7 +25,7 @@ Every account is tied to an email address. You can invite additional users to yo
## Inviting additional users to an account
-You can invite additional users to your account, and manage their permissions on the *Account Management* page in the Qdrant Cloud Console.
+You can invite additional users to your account, and manage their permissions on the *Account -> Access Management* page in the Qdrant Cloud Console.
@@ -37,9 +39,15 @@ If you have access to multiple accounts, you can switch between accounts with th
+## Light & Dark Mode
+
+The Qdrant Cloud Console supports light and dark mode. You can switch between the two modes in the *Settings* menu, by clicking on your account picture in the top right corner.
+
+
+
## Account settings
-You can configure your account settings in the Qdrant Cloud Console, by clicking on your account picture in the top right corner, and selecting *Profile*.
+You can configure your account settings in the Qdrant Cloud Console on the *Account -> Settings* page.
The following functionality is available.
@@ -53,6 +61,9 @@ If you use multiple accounts for different purposes, it is a good idea to give t
When you delete an account, all database clusters and associated data will be deleted.
+
+
+
## Enterprise Single-Sign-On (SSO)
Qdrant Cloud supports Enterprise Single-Sign-On for Premium Tier customers. The following providers are supported:
diff --git a/qdrant-landing/content/documentation/qdrant-cloud-api.md b/qdrant-landing/content/documentation/cloud-api.md
similarity index 98%
rename from qdrant-landing/content/documentation/qdrant-cloud-api.md
rename to qdrant-landing/content/documentation/cloud-api.md
index 08f23787a..386eaaded 100644
--- a/qdrant-landing/content/documentation/qdrant-cloud-api.md
+++ b/qdrant-landing/content/documentation/cloud-api.md
@@ -2,6 +2,8 @@
title: Qdrant Cloud API
weight: 27
partition: cloud
+aliases:
+ - /documentation/qdrant-cloud-api/
---
# Qdrant Cloud API
diff --git a/qdrant-landing/content/documentation/cloud/getting-started.md b/qdrant-landing/content/documentation/cloud-getting-started.md
similarity index 87%
rename from qdrant-landing/content/documentation/cloud/getting-started.md
rename to qdrant-landing/content/documentation/cloud-getting-started.md
index 746a358f2..dfc22d288 100644
--- a/qdrant-landing/content/documentation/cloud/getting-started.md
+++ b/qdrant-landing/content/documentation/cloud-getting-started.md
@@ -1,6 +1,9 @@
---
title: Getting Started
-weight: 1
+weight: 12
+partition: cloud
+aliases:
+ - /documentation/cloud/getting-started/
---
# Getting Started with Qdrant Managed Cloud
@@ -26,7 +29,3 @@ After setting up your account, you can create a Qdrant Cluster by following the
For a production-ready environment, consider deploying a multi-node Qdrant cluster (at least three nodes) with replication enabled. Instructions for configuring distributed clusters are available in the [Distributed Deployment](/documentation/guides/distributed_deployment/) guide.
If you are looking to optimize costs, you can reduce memory usage through [Quantization](/documentation/guides/quantization/) or by [offloading vectors to disk](/documentation/concepts/storage/#configuring-memmap-storage).
-
-## Support
-
-If you need assistance, you can reach our Support Team through the Qdrant Cloud UI or directly via [https://support.qdrant.io/](https://support.qdrant.io/). Information on service-level agreements is provided at [https://qdrant.to/sla](https://qdrant.to/sla).
diff --git a/qdrant-landing/content/documentation/cloud/premium.md b/qdrant-landing/content/documentation/cloud-premium.md
similarity index 94%
rename from qdrant-landing/content/documentation/cloud/premium.md
rename to qdrant-landing/content/documentation/cloud-premium.md
index 0828d20ce..8238765eb 100644
--- a/qdrant-landing/content/documentation/cloud/premium.md
+++ b/qdrant-landing/content/documentation/cloud-premium.md
@@ -1,6 +1,9 @@
---
title: Premium Tier
-weight: 66
+weight: 19
+partition: cloud
+aliases:
+ - /documentation/cloud/premium/
---
# Qdrant Cloud Premium Tier
diff --git a/qdrant-landing/content/documentation/cloud/pricing-payments.md b/qdrant-landing/content/documentation/cloud-pricing-payments.md
similarity index 98%
rename from qdrant-landing/content/documentation/cloud/pricing-payments.md
rename to qdrant-landing/content/documentation/cloud-pricing-payments.md
index 96783a120..bf4f57ded 100644
--- a/qdrant-landing/content/documentation/cloud/pricing-payments.md
+++ b/qdrant-landing/content/documentation/cloud-pricing-payments.md
@@ -1,10 +1,12 @@
---
title: Billing & Payments
-weight: 65
+weight: 18
+partition: cloud
aliases:
- aws-marketplace
- gcp-marketplace
- azure-marketplace
+ - /documentation/cloud/pricing-payments/
---
# Qdrant Cloud Billing & Payments
diff --git a/qdrant-landing/content/documentation/quickstart-cloud.md b/qdrant-landing/content/documentation/cloud-quickstart.md
similarity index 86%
rename from qdrant-landing/content/documentation/quickstart-cloud.md
rename to qdrant-landing/content/documentation/cloud-quickstart.md
index 6b01a1cc2..21eb1d75a 100644
--- a/qdrant-landing/content/documentation/quickstart-cloud.md
+++ b/qdrant-landing/content/documentation/cloud-quickstart.md
@@ -7,6 +7,7 @@ aliases:
- cloud-quick-start
- cloud-quickstart
- cloud/quickstart-cloud/
+ - /documentation/quickstart-cloud/
---
# How to Get Started With Qdrant Cloud
@@ -14,20 +15,22 @@ aliases:
You can try vector search on Qdrant Cloud in three steps.
Instructions are below, but the video is faster:
-## Setup a Qdrant Cloud cluster
+## Setup a Qdrant Cloud Cluster
1. Register for a [Cloud account](https://cloud.qdrant.io/signup) with your email, Google or Github credentials.
-2. Go to **Overview** and follow the onboarding instructions under **Create First Cluster**.
+2. Go to **Clusters** and follow the onboarding instructions under **Create First Cluster**.
-3. When you create it, you will receive an API key. You will need to copy and paste it soon.
-4. Your new cluster will be created under **Clusters**. Give it a few moments to provision.
+3. When you create it, you will receive an API key. You will need to copy it and store it somewhere self. It will not be displayed again. If you loose it, you can always create a new one on the **Cluster Detail Page** later.
-## Access the cluster dashboard
+
-1. Go to your **Clusters**. Under **Actions**, open the **Dashboard**.
-2. Paste your new API key here. You can revoke and create new API keys in **Access Management**.
+
+## Access the Cluster UI
+
+1. Click on **Cluster UI** on the **Cluster Detail Page** to access the cluster UI dashboard.
+2. Paste your new API key here. You can revoke and create new API keys in the **API Keys** tab on your **Cluster Detail Page**.
3. The key will grant you access to your Qdrant instance. Now you can see the cluster Dashboard.
@@ -108,7 +111,7 @@ client, err := qdrant.NewClient(&qdrant.Config{
})
```
-## Try the Tutorial sandbox
+## Try the Tutorial Sandbox
1. Open the interactive **Tutorial**. Here, you can test basic Qdrant API requests.
2. Using the **Quickstart** instructions, create a collection, add vectors and run a search.
@@ -116,11 +119,11 @@ client, err := qdrant.NewClient(&qdrant.Config{
-## That's vector search!
+## That's Vector Search!
You can stay in the sandbox and continue trying our different API calls.
When ready, use the Console and our complete REST API to try other operations.
-## What's next?
+## What's Next?
Now that you have a Qdrant Cloud cluster up and running, you should [test remote access](/documentation/cloud/authentication/#test-cluster-access) with a Qdrant Client.
diff --git a/qdrant-landing/content/documentation/cloud-rbac/_index.md b/qdrant-landing/content/documentation/cloud-rbac/_index.md
index c0f66ddb0..e6da3b3a3 100644
--- a/qdrant-landing/content/documentation/cloud-rbac/_index.md
+++ b/qdrant-landing/content/documentation/cloud-rbac/_index.md
@@ -1,6 +1,6 @@
---
title: Cloud RBAC
-weight: 16
+weight: 14
partition: cloud
---
diff --git a/qdrant-landing/content/documentation/cloud-rbac/role-management.md b/qdrant-landing/content/documentation/cloud-rbac/role-management.md
index 70c2986de..ba6c8bdbe 100644
--- a/qdrant-landing/content/documentation/cloud-rbac/role-management.md
+++ b/qdrant-landing/content/documentation/cloud-rbac/role-management.md
@@ -5,14 +5,10 @@ weight: 1
# Role Management
-
-
> š” You can access this in **Access Management > User & Role Management** *if available see [this page for details](/documentation/cloud-rbac/).*
-
A **Role** contains a set of **permissions** that define the ability to perform or control specific actions in Qdrant Cloud. Permissions are accessible through the Permissions tab in the Role Details page and offer fine-grained access control, logically grouped for easy identification.
-
## Built-In Roles
Qdrant Cloud includes some built-in roles for common use-cases. The permissions for these built-in roles cannot be changed.
@@ -29,7 +25,7 @@ There are three types:Ā
AnĀ authorized user can create their own custom roles with specific sets of permissions, giving them more control over who has what access to which resource.
-
+
### Creating a Custom Role
@@ -42,8 +38,6 @@ Once created, the new role will appear under the **Custom Roles** section in the
-
-
### Editing a Custom Role
To update a specific role's permissions, select it from the list and click on theĀ **Permissions**Ā tab. Here, you'll find logically grouped options that are easy to identify and edit as needed. Once you've made your changes, save them to apply the updated permissions to the role.
diff --git a/qdrant-landing/content/documentation/cloud-rbac/user-management.md b/qdrant-landing/content/documentation/cloud-rbac/user-management.md
index 62dd33b74..1d86d1354 100644
--- a/qdrant-landing/content/documentation/cloud-rbac/user-management.md
+++ b/qdrant-landing/content/documentation/cloud-rbac/user-management.md
@@ -3,27 +3,16 @@ title: User Management
weight: 2
---
-
# User Management
-
-
> š” You can access this in **Access Management > User & Role Management** *if available see [this page for details](/documentation/cloud-rbac/).*
-
-
-
## Inviting Users to an Account
-
Users can be invited via the **User Management** section, where they are assigned the **Base role** by default. Additionally, users have the option to select a specific role when inviting another user. The **Base role** is a predefined role with minimal permissions, granting users access to the platform while restricting them to viewing only their own profile.
-
-
-
-
### Inviting Users from a Role
Users can be invited attached to a specific role by inviting them through theĀ **Role Details**Ā page - just click on the Users tab and follow the prompts.
@@ -34,7 +23,8 @@ Once accepted, they'll be assigned that role's permissions, along with the base
### Revoking an Invitation
-Before being accepted, an Admin/Owner can cancel a pending invite directly on either theĀ **User Management**Ā orĀ **Role Details**Ā page.
+Before being accepted, an A
+dmin/Owner can cancel a pending invite directly on either theĀ **User Management**Ā orĀ **Role Details**Ā page.
diff --git a/qdrant-landing/content/documentation/cloud-tab.md b/qdrant-landing/content/documentation/cloud-tab.md
index 3609c6ee3..869a640dc 100644
--- a/qdrant-landing/content/documentation/cloud-tab.md
+++ b/qdrant-landing/content/documentation/cloud-tab.md
@@ -20,8 +20,8 @@ content:
- id: 1
image:
src: /img/dev-portal-cloud/managed-cloud.png
- alt: Qdrant Cloud
- title: Qdrant Cloud
+ alt: Managed Cloud
+ title: Managed Cloud
description: Qdrant Managed Cloud is our SaaS solution, providing managed Qdrant database clusters on the cloud.
link:
url: /documentation/cloud/
diff --git a/qdrant-landing/content/documentation/cloud/_index.md b/qdrant-landing/content/documentation/cloud/_index.md
index bbb9b719b..7271f4c67 100644
--- a/qdrant-landing/content/documentation/cloud/_index.md
+++ b/qdrant-landing/content/documentation/cloud/_index.md
@@ -1,6 +1,6 @@
---
title: Managed Cloud
-weight: 12
+weight: 15
aliases:
- /documentation/overview/qdrant-alternatives/documentation/cloud/
partition: cloud
@@ -14,7 +14,7 @@ Transitioning to the Managed Cloud version of Qdrant does not change how you int
You can also attach your own infrastructure as a Hybrid Cloud Environment. For details, see our [Hybrid Cloud](/documentation/hybrid-cloud/) documentation.
-## Cluster configuration
+## Cluster Configuration
Each database cluster comes pre-configured with the following tools, features, and support services:
@@ -26,4 +26,3 @@ Each database cluster comes pre-configured with the following tools, features, a
- Available natively on AWS and GCP, and Azure.
- Available on your own infrastructure and other providers if you use the Hybrid Cloud.
-## Ready? [**Click here to get started!**](/documentation/cloud/getting-started/)
diff --git a/qdrant-landing/content/documentation/cloud/authentication.md b/qdrant-landing/content/documentation/cloud/authentication.md
index 8cebc7030..85c1ac5ce 100644
--- a/qdrant-landing/content/documentation/cloud/authentication.md
+++ b/qdrant-landing/content/documentation/cloud/authentication.md
@@ -11,26 +11,30 @@ Database API keys can be configured with granular access control. Database API k
Database API keys with granular access control are available for clusters using version **v1.11.0** and above.
-## Create Database API keys
+## Create Database API Keys
+
+
1. Go to the [Cloud Dashboard](https://qdrant.to/cloud).
-2. Go to the **API Keys** section of the Cluster detail page.
+2. Go to the **API Keys** section of the **Cluster Detail Page**.
3. Click **Create**.
4. Choose a name and an optional expiration (in days, the default is 90 days) for your API key. An empty expiration will result in no expiration.
5. By default, tokens are given cluster-wide permissions, with a choice between manage/write permissions (default) or read-only.
To restrict a token to a subset of collections, you can select the Collections tab and choose from the collections available in your cluster.
6. Click **Create** and retrieve your API key.
+
+
We recommend configuring an expiration and rotating your API keys regularly as a security best practice.
-## Admin Database API keys
+## Admin Database API Keys
-The previous iteration of Database API keys, called Admin Database API keys, do not have granular access control. Clusters created before January 27, 2025 will still see the option to create Admin Database API keys. Older Admin Database API keys will continue to work but we do recommend switching to Database API keys with granular access control to take advantage of better security controls.
+The previous iteration of Database API keys, called Admin Database API keys, do not have granular access control. Clusters created before January 27, 2025 will still see the option to create Admin Database API keys. Older Admin Database API keys will continue to work, but we do recommend switching to Database API keys with granular access control to take advantage of better security controls.