Docs cleanup 2 (cube-js#10460)

* docs: add user attributes syncing via SCIM for Entra ID

Add section documenting how to sync user attributes from Microsoft
Entra to Cube via SCIM, including attribute creation, schema prefix,
and mapping configuration.

Made-with: Cursor

* docs: add Viewer role requirement for MCP server

Made-with: Cursor

* docs: move Chart Prototyping to Embedding, Data Model to Data Modeling

- Move Chart Prototyping (vizard) from workspace to embedding section
- Move Data Model page to data-modeling section, rename to Data Model IDE
- Update all references and add redirects for old paths

Made-with: Cursor

* docs: restructure pages, add scheduled refreshes and notifications docs

- Move API keys from workspace to administration
- Move Pricing from deployment to administration
- Hide CLI from workspace navigation
- Update scheduled refreshes page with full documentation
- Add notifications page for email and Slack delivery
- Update all references and add redirects for moved pages

Made-with: Cursor

Author: keydunov

docs/content/product/administration/_meta.js

@@ -3,6 +3,8 @@ export default {
   "sso": "SSO & identity providers",
   "ai": "AI",
   "workspace": "Workspace",
+  "api-keys": "API keys",
+  "pricing": "Pricing",
   "deployment": "Deployment",
   "distribution": "Distribution"
 }

…ct/administration/workspace/api-keys.mdx …tent/product/administration/api-keys.mdxdocs/content/product/administration/workspace/api-keys.mdx renamed to docs/content/product/administration/api-keys.mdx docs/content/product/administration/workspace/api-keys.mdx renamed to docs/content/product/administration/api-keys.mdx

@@ -10,7 +10,6 @@ export default {
   "warm-up": "Deployment warm-up",
   "auto-suspension": "Auto-suspension",
   "scalability": "Scalability",
-  "pricing": "Pricing",
   "support": "Support",
   "limits": "Limits",
   "core": "Cube Core"

docs/content/product/administration/deployment/_meta.js

@@ -117,7 +117,7 @@ response times to be significantly longer than usual.
 [ref-deployment-prod-cluster]:
   /product/deployment/cloud/deployment-types#production-cluster
 [ref-prod-multi-cluster]: /product/deployment/cloud/deployment-types#production-multi-cluster
-[ref-deployment-pricing]: /product/deployment/cloud/pricing
+[ref-deployment-pricing]: /product/administration/pricing
 [ref-monitoring]: /product/workspace/monitoring
 [ref-data-model]: /product/data-modeling/overview
 [ref-multitenancy]: /product/configuration/multitenancy

docs/content/product/administration/deployment/auto-suspension.mdx

@@ -54,7 +54,7 @@ You can try a Cube Cloud development instance by
 <InfoBox>
 
 Available on [all paid plans](https://cube.dev/pricing).
-You can also choose a [deployment tier](/product/deployment/cloud/pricing#deployment-tiers).
+You can also choose a [deployment tier](/product/administration/pricing#deployment-tiers).
 
 </InfoBox>
 

docs/content/product/administration/deployment/deployment-types.mdx

@@ -165,13 +165,13 @@ resource consumption in different scenarios.
 [ref-deployment-types]: /product/deployment/cloud/deployment-types
 [ref-dev-mode]: /product/workspace/dev-mode
 [ref-auto-sus]: /product/deployment/cloud/auto-suspension
-[ref-total-cost]: /product/deployment/cloud/pricing#total-cost-examples
+[ref-total-cost]: /product/administration/pricing#total-cost-examples
 [ref-data-source]: /product/configuration/data-sources
 [ref-duckdb]: /product/configuration/data-sources/duckdb
 [ref-data-model]: /product/data-modeling/overview
 [ref-dynamic-data-models]: /product/data-modeling/dynamic
 [ref-config-options]: /product/configuration#configuration-options
-[ref-data-model]: /product/workspace/data-model
+[ref-data-model]: /product/data-modeling/data-model-ide
 [ref-playground]: /product/workspace/playground
 [ref-environments]: /product/workspace/environments
 [ref-environments-prod]: /product/workspace/environments#production-environment

docs/content/product/administration/deployment/deployments.mdx

@@ -98,14 +98,14 @@ response.
 [ref-rest-api]: /product/apis-integrations/rest-api
 [ref-gql-api]: /product/apis-integrations/graphql-api
 [ref-deployment-types]: /product/deployment/cloud/deployment-types
-[ref-pricing]: /product/deployment/cloud/pricing
+[ref-pricing]: /product/administration/pricing
 [ref-query-history]: /product/workspace/query-history
 [ref-monitoring-integrations]: /product/workspace/monitoring
 [ref-dev-instance]:
   /product/deployment/cloud/deployment-types#development-instance
 [ref-prod-cluster]:
   /product/deployment/cloud/deployment-types#production-cluster
 [cube-contact-us]: https://cube.dev/contact
-[ref-query-history-tiers]: /product/deployment/cloud/pricing#query-history-tiers
+[ref-query-history-tiers]: /product/administration/pricing#query-history-tiers
 [ref-audit-log]: /product/workspace/audit-log
-[ref-monitoring-integrations-tiers]: /product/deployment/cloud/pricing#monitoring-integrations-tiers
+[ref-monitoring-integrations-tiers]: /product/administration/pricing#monitoring-integrations-tiers

docs/content/product/administration/deployment/limits.mdx

@@ -106,9 +106,9 @@ We prioritize support requests based on their severity, as follows:
 [ref-docs-intro]: /product/introduction
 [cube-webinars]: https://cube.dev/events
 [cube-slack]: https://slack.cube.dev
-[ref-cloud-pricing]: /product/deployment/cloud/pricing
-[ref-free-tier]: /product/deployment/cloud/pricing#free
-[ref-starter-tier]: /product/deployment/cloud/pricing#starter
-[ref-premium-tier]: /product/deployment/cloud/pricing#premium
-[ref-enterprise-tier]: /product/deployment/cloud/pricing#enterprise
-[ref-enterprise-premier-tier]: /product/deployment/cloud/pricing#enterprise-premier
+[ref-cloud-pricing]: /product/administration/pricing
+[ref-free-tier]: /product/administration/pricing#free
+[ref-starter-tier]: /product/administration/pricing#starter
+[ref-premium-tier]: /product/administration/pricing#premium
+[ref-enterprise-tier]: /product/administration/pricing#enterprise
+[ref-enterprise-premier-tier]: /product/administration/pricing#enterprise-premier

docs/content/product/administration/deployment/support.mdx

@@ -1,7 +1,7 @@
 # SCIM provisioning with Microsoft Entra ID
 
 With SCIM (System for Cross-domain Identity Management) enabled, you can
-automate user provisioning in Cube Cloud and keep user groups synchronized
+automate user provisioning in Cube and keep user groups synchronized
 with Microsoft Entra ID (formerly Azure Active Directory).
 
 <InfoBox>
@@ -16,49 +16,49 @@ Before proceeding, ensure you have the following:
 
 - Microsoft Entra SAML authentication already configured. If not, complete
   the [SAML setup][ref-saml] first.
-- Admin permissions in Cube Cloud.
+- Admin permissions in Cube.
 - Sufficient permissions in Microsoft Entra to manage Enterprise Applications.
 
-## Enable SCIM provisioning in Cube Cloud
+## Enable SCIM provisioning in Cube
 
 Before configuring SCIM in Microsoft Entra, you need to enable SCIM
-provisioning in Cube Cloud:
+provisioning in Cube:
 
 1. In Cube, navigate to <Btn>Admin → Settings</Btn>.
 2. In the <Btn>SAML</Btn> section, enable <Btn>SCIM Provisioning</Btn>.
 
-## Generate an API key in Cube Cloud
+## Generate an API key in Cube
 
-To allow Entra ID to communicate with Cube Cloud via SCIM, you'll need to
+To allow Entra ID to communicate with Cube via SCIM, you'll need to
 create a dedicated API key:
 
-1. In Cube Cloud, navigate to <Btn>Settings → API Keys</Btn>.
+1. In Cube, navigate to <Btn>Settings → API Keys</Btn>.
 2. Create a new API key. Give it a descriptive name such as **Entra SCIM**.
 3. Copy the generated key and store it securely — you'll need it in the
    next step.
 
 ## Set up provisioning in Microsoft Entra
 
-This section assumes you already have a Cube Cloud Enterprise Application
+This section assumes you already have a Cube Enterprise Application
 in Microsoft Entra. If you haven't created one yet, follow the
 [SAML setup guide][ref-saml] first.
 
 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).
 2. Go to <Btn>Applications → Enterprise Applications</Btn> and open your
-   Cube Cloud application.
+   Cube application.
 3. Navigate to <Btn>Manage → Provisioning</Btn>.
 4. Set the <Btn>Provisioning Mode</Btn> to **Automatic**.
 5. Under <Btn>Admin Credentials</Btn>, fill in the following:
-   - **Tenant URL** — Your Cube Cloud deployment URL with `/api/scim/v2`
+   - **Tenant URL** — Your Cube deployment URL with `/api/scim/v2`
      appended. For example: `https://your-deployment.cubecloud.dev/api/scim/v2`
    - **Secret Token** — The API key you generated in the previous step.
 6. Click <Btn>Test Connection</Btn> to verify that Entra ID can reach
-   Cube Cloud. Proceed once the test is successful.
+   Cube. Proceed once the test is successful.
 
 ## Configure attribute mappings
 
 Next, configure which user and group attributes are synchronized with
-Cube Cloud:
+Cube:
 
 1. In the <Btn>Mappings</Btn> section, select the object type you want to
    configure — either users or groups.
@@ -71,8 +71,49 @@ Cube Cloud:
 
 Users provisioned via SCIM will receive the Explorer role.
 To grant admin permissions, update the user's role manually in
-Cube Cloud under <Btn>Team & Security</Btn>.
+Cube under <Btn>Team & Security</Btn>.
 
 </InfoBox>
 
+## Syncing user attributes
+
+You can sync [user attributes][ref-user-attributes] from Microsoft Entra to
+Cube via SCIM, allowing you to centralize user management in Entra.
+
+### Create a user attribute in Cube
+
+In Cube, navigate to <Btn>Admin → Settings → User Attributes</Btn> and
+create a new attribute. Take note of the attribute **reference** name — you will
+need it when configuring Entra.
+
+### Create an Entra user attribute
+
+1. In the [Microsoft Entra admin center](https://entra.microsoft.com), navigate
+   to <Btn>Applications → Enterprise Applications</Btn> and open your Cube
+   application.
+2. Go to <Btn>Manage → Provisioning → Mappings</Btn>.
+3. Select the user mapping you want to add the attribute to.
+4. At the bottom of the page, select <Btn>Show advanced options</Btn>.
+5. Select <Btn>Edit attribute list for customappsso</Btn>.
+6. Add a new attribute with the following settings:
+   - **Name** — The reference of the attribute you created in Cube,
+     prefixed with `urn:cube:params:1.0:UserAttribute:`.
+     For example, for an attribute with the reference `country`, enter
+     `urn:cube:params:1.0:UserAttribute:country`.
+   - **Type** — Select the matching type (`string` or `integer`).
+7. Save the changes.
+
+### Create attribute mapping
+
+1. After saving, click <Btn>Yes</Btn> when prompted.
+2. In the <Btn>Attribute Mapping</Btn> page, click <Btn>Add New Mapping</Btn>.
+3. In the <Btn>Target attribute</Btn> dropdown, select the attribute you created
+   in the previous step.
+4. Configure the source mapping to the appropriate Entra field.
+5. Click <Btn>OK</Btn>, then <Btn>Save</Btn>.
+
+The next time the Entra application syncs, the attribute values will be
+provisioned as [user attributes][ref-user-attributes] in Cube.
+
 [ref-saml]: /product/administration/sso/microsoft-entra-id/saml
+[ref-user-attributes]: /product/administration/users-and-permissions/user-attributes