diff --git a/images/managed-postgres/rbac/newpostgresperms.png b/images/managed-postgres/rbac/newpostgresperms.png
new file mode 100644
index 00000000..518431ac
Binary files /dev/null and b/images/managed-postgres/rbac/newpostgresperms.png differ
diff --git a/images/managed-postgres/rbac/postgresentity.png b/images/managed-postgres/rbac/postgresentity.png
new file mode 100644
index 00000000..2acf9565
Binary files /dev/null and b/images/managed-postgres/rbac/postgresentity.png differ
diff --git a/images/managed-postgres/rbac/usersandroles.png b/images/managed-postgres/rbac/usersandroles.png
new file mode 100644
index 00000000..d78bf023
Binary files /dev/null and b/images/managed-postgres/rbac/usersandroles.png differ
diff --git a/products/managed-postgres/navigation.json b/products/managed-postgres/navigation.json
index d9dd09d2..a7e1e090 100644
--- a/products/managed-postgres/navigation.json
+++ b/products/managed-postgres/navigation.json
@@ -16,6 +16,7 @@
"products/managed-postgres/settings",
"products/managed-postgres/scaling",
"products/managed-postgres/security",
+ "products/managed-postgres/rbac",
"products/managed-postgres/high-availability",
"products/managed-postgres/read-replicas",
"products/managed-postgres/backup-and-restore",
diff --git a/products/managed-postgres/rbac.mdx b/products/managed-postgres/rbac.mdx
new file mode 100644
index 00000000..868a89d2
--- /dev/null
+++ b/products/managed-postgres/rbac.mdx
@@ -0,0 +1,51 @@
+---
+slug: /cloud/managed-postgres/rbac
+sidebarTitle: 'RBAC'
+title: 'Managed Postgres RBAC'
+description: 'Learn about role-based access control (RBAC) in ClickHouse Managed Postgres'
+keywords: ['managed postgres RBAC', 'access control', 'roles', 'privileges', 'permissions']
+doc_type: 'reference'
+---
+
+import BetaBadge from "/snippets/components/BetaBadge/BetaBadge.jsx";
+import { Image } from "/snippets/components/Image.jsx";
+
+
+
+ClickHouse Cloud supports role-based access control (RBAC) for Managed Postgres services. You can create custom roles with specific permissions and assign them to organization members to control who can view or manage your Postgres services.
+
+## Available permissions {#available-permissions}
+
+Managed Postgres currently supports two permissions:
+
+| Permission | Description |
+|------------------------------|----------------------------------------------------------------------|
+| **View Postgres services** | Allows a user to see the Postgres service and its details. |
+| **Manage Postgres services** | Allows a user to modify, scale, and configure the Postgres service. |
+
+Creating a new Postgres service requires the existing **Organization manage** permission. The permissions above apply only to existing services.
+
+
+More granular permissions will be available in a future release.
+
+
+## Creating a custom role {#creating-a-custom-role}
+
+1. Click your organization name in the left sidebar and select **Users and roles**.
+
+
+
+2. Switch to the **Roles** tab and click **Create role**.
+3. Enter a name for the role, then click **+ Allow** and select **Postgres Service** from the entity list.
+
+
+
+4. Choose the Postgres service to scope the role to, then select the permissions to grant.
+
+
+
+5. Click **Create role** to save.
+
+## Assigning a role {#assigning-a-role}
+
+Once the role is created, assign it to users from the **Users** tab on the same **Users and roles** page. A user can have multiple roles, and roles can be combined to build the exact access profile you need.