diff --git a/product/admin/applications.mdx b/product/admin/applications.mdx index 1976405f..601191c6 100644 --- a/product/admin/applications.mdx +++ b/product/admin/applications.mdx @@ -27,7 +27,7 @@ All newly created tenants start with a single managed app: the [C1 app](/product Use **Configure columns** in the table header to adjust which columns are visible — toggle columns on or off and drag to reorder. Your layout is saved automatically. -To export apps data to CSV, click **Generate CSV** above the **Apps** table. The **Download to CSV** drawer opens where you can choose which columns to include before generating the file. +To export apps data to CSV, click **Generate CSV** above the **Apps** table. The **Download as CSV** drawer opens where you can choose which columns to include before generating the file. ## Create a new application diff --git a/product/admin/attributes.mdx b/product/admin/attributes.mdx index a6e207bb..22906d24 100644 --- a/product/admin/attributes.mdx +++ b/product/admin/attributes.mdx @@ -80,7 +80,7 @@ Select how you'll tell C1 where to find the source (or sources) of data for this **Don't see the attribute you need?** Check to make sure that the application you've selected is connected and syncing data correctly. A sync error might be the cause of missing attributes. - 3. **Optional.** Click **Add fallback source** or **Add additional source** (for manager email, additional username, and additional email) and add additional mappings as fallback or additional sources of the user attribute data. + 3. **Optional.** Click **Add fallback source** or **Add another source** (for manager email, additional username, and additional email) and add additional mappings as fallback or additional sources of the user attribute data. In the case of fallback sources, C1 will iterate through the list you create here until it finds a source with the data it's looking for. diff --git a/product/admin/automations.mdx b/product/admin/automations.mdx index 95179482..3d2d3a02 100644 --- a/product/admin/automations.mdx +++ b/product/admin/automations.mdx @@ -55,7 +55,7 @@ Let's break down the structure: Fill out the automation step form and click **Save**. - Click **+ Add step** again and repeat the process to add additional steps, as needed. + Click **Add step** again and repeat the process to add additional steps, as needed. If you need to reorder the automation steps, hover over the step and use the arrow keys. diff --git a/product/admin/campaigns.mdx b/product/admin/campaigns.mdx index a92b3b71..4bce0d91 100644 --- a/product/admin/campaigns.mdx +++ b/product/admin/campaigns.mdx @@ -153,7 +153,7 @@ If you want to use a Slack channel for communication about this campaign, click -**Optional.** To surface app user profile attributes to reviewers during access reviews, find the **Attribute visibility** section and click **+ Add attribute**. For each attribute you want to show, select an app and the attribute key — for example, **department** on AWS PROD. Each app-attribute combination is configured as a separate entry. Reviewers see no attributes by default; only those you configure here will be visible. +**Optional.** To surface app user profile attributes to reviewers during access reviews, find the **Attribute visibility** section and click **Add attribute**. For each attribute you want to show, select an app and the attribute key — for example, **department** on AWS PROD. Each app-attribute combination is configured as a separate entry. Reviewers see no attributes by default; only those you configure here will be visible. See [Map user attributes](/product/admin/attributes) to learn how attributes are defined in C1. @@ -165,7 +165,7 @@ Next, build a list of the resources that your campaign will review. -On the **Scope** tab of your campaign, find the **Grant types** section. By default, campaigns review grants held by users. Click **Change selection** if you want to review grants held by other kinds of principals instead: +On the **Scope** tab of your campaign, find the **Grant type** section. By default, campaigns review grants held by users. Click **Change selection** if you want to review grants held by other kinds of principals instead: - **Users only** *(default)* — Review access grants held directly by users. - **Resources only** — Review access grants held by groups or roles instead of users. @@ -234,7 +234,7 @@ If you're building a UAR reviewing specific resources, click the pencil icon to -**Optional.** Find the **Account parameters** section of the page and click **Make selections**. +**Optional.** Find the **Account selection** section of the page and click **Make selections**. If you don't make any selections here, all accounts with access to the apps or resources you selected above will be added to the campaign. If you want to narrow the focus of the UAR: @@ -256,7 +256,7 @@ If you're building a UAR reviewing specific resources, click the pencil icon to -**Optional.** Find the **Grant parameters** section of the page and click **Make selections**. +**Optional.** Find the **Grant selection** section of the page and click **Make selections**. If you don't make any selections here, all access grants of the apps or resources you selected above will be added to the campaign. If you want to narrow the focus of the UAR: @@ -492,7 +492,7 @@ If you want to use a Slack channel for communication about this campaign, click -**Optional.** To surface app user profile attributes to reviewers during access reviews, find the **Attribute visibility** section and click **+ Add attribute**. For each attribute you want to show, select an app and the attribute key — for example, **department** on AWS PROD. Each app-attribute combination is configured as a separate entry. Reviewers see no attributes by default; only those you configure here will be visible. +**Optional.** To surface app user profile attributes to reviewers during access reviews, find the **Attribute visibility** section and click **Add attribute**. For each attribute you want to show, select an app and the attribute key — for example, **department** on AWS PROD. Each app-attribute combination is configured as a separate entry. Reviewers see no attributes by default; only those you configure here will be visible. See [Map user attributes](/product/admin/attributes) to learn how attributes are defined in C1. @@ -504,7 +504,7 @@ Next, build a list of the resources that campaigns made from this template will -On the **Scope** tab of your template, find the **Grant types** section. By default, campaigns review grants held by users. Click **Change selection** if you want campaigns made from this template to review grants held by other kinds of principals instead: +On the **Scope** tab of your template, find the **Grant type** section. By default, campaigns review grants held by users. Click **Change selection** if you want campaigns made from this template to review grants held by other kinds of principals instead: - **Users only** *(default)* — Review access grants held directly by users. - **Resources only** — Review access grants held by groups or roles instead of users. @@ -566,7 +566,7 @@ If you're building a UAR reviewing specific resources, click the pencil icon to - [User profile attributes](/product/admin/attributes). For example, to run an access review campaign on all the AcmeApp users in your company with the job title "Engineer", create the parameter **User AcmeJob is Engineer**. -**Optional.** Find the **Account parameters** section of the page and click **Make selections**. +**Optional.** Find the **Account selection** section of the page and click **Make selections**. If you don't make any selections here, all accounts with access to the apps or resources you selected above will be added to the campaign. If you want to narrow the focus of the UAR: @@ -584,7 +584,7 @@ If you're building a UAR reviewing specific resources, click the pencil icon to -**Optional.** Find the **Grant parameters** section of the page and click **Make selections**. +**Optional.** Find the **Grant selection** section of the page and click **Make selections**. If you don't make any selections here, all access grants of the apps or resources you selected above will be added to the campaign. If you want to narrow the focus of the UAR: diff --git a/product/admin/customize-requests.mdx b/product/admin/customize-requests.mdx index d139c2ff..a2e42f00 100644 --- a/product/admin/customize-requests.mdx +++ b/product/admin/customize-requests.mdx @@ -101,7 +101,7 @@ When you're ready, click **Save** to apply your chosen form to access requests f -**Done.** The request form will now be shown whenever a user requests this entitlement via the **Requests** page or the **+ New request** form. +**Done.** The request form will now be shown whenever a user requests this entitlement via the **Requests** page or the **New request** form. ### Add a request form to several entitlements in an app @@ -124,7 +124,7 @@ Find the **Request form** area at the bottom of the configuration drawer and sel Click **Submit**. -**Done.** The request form will now be shown whenever a user requests one of the selected entitlement via the **Requests** page or the **+ New request** page. +**Done.** The request form will now be shown whenever a user requests one of the selected entitlement via the **Requests** page or the **New request** page. ### Create a new request form diff --git a/product/admin/enable-ai-access-management.mdx b/product/admin/enable-ai-access-management.mdx index fe25c74f..2281bb9a 100644 --- a/product/admin/enable-ai-access-management.mdx +++ b/product/admin/enable-ai-access-management.mdx @@ -37,7 +37,7 @@ Click **Save** to confirm. -Once enabled, **MCP servers**, **AI clients**, and the **AIAM audit log** appear in the tenant. +Once enabled, **MCP servers**, **MCP clients**, and the **AIAM audit log** appear in the tenant. ## Configure tenant defaults @@ -141,10 +141,10 @@ The kill switch immediately revokes every AI client's access to every tool, acro -In **Settings > System management**, find **Emergency kill switch**. +In **Settings > System management**, find **Disable system features**. -Click **Disable all AI access**. +Toggle **Disable MCP traffic**. diff --git a/product/admin/managing-accounts.mdx b/product/admin/managing-accounts.mdx index 81d3cd46..edfa03a5 100644 --- a/product/admin/managing-accounts.mdx +++ b/product/admin/managing-accounts.mdx @@ -120,7 +120,7 @@ The updated account type is now shown in the **Account type** column. Use **Configure columns** in the **Accounts** table header to adjust which columns are visible — toggle columns on or off and drag to reorder. Your layout is saved automatically. -To export accounts data to CSV, click **Generate CSV** above the **Accounts** table. The **Download to CSV** drawer opens where you can choose which columns to include before generating the file. +To export accounts data to CSV, click **Generate CSV** above the **Accounts** table. The **Download as CSV** drawer opens where you can choose which columns to include before generating the file. ![A screenshot of a Slack application's Accounts tab in C1.](/images/product/assets/apps-accounts-3.png) diff --git a/product/admin/managing-entitlements.mdx b/product/admin/managing-entitlements.mdx index 011741fe..f11f162b 100644 --- a/product/admin/managing-entitlements.mdx +++ b/product/admin/managing-entitlements.mdx @@ -54,7 +54,7 @@ Click **Create**. Use **Configure columns** in the **Entitlements** table header to adjust which columns are visible — toggle columns on or off and drag to reorder. Your layout is saved automatically. The table includes an **Owners** column showing the users responsible for each entitlement. -To export entitlements data to CSV, click **Generate CSV** above the **Entitlements** table. The **Download to CSV** drawer opens where you can choose which columns to include before generating the file. +To export entitlements data to CSV, click **Generate CSV** above the **Entitlements** table. The **Download as CSV** drawer opens where you can choose which columns to include before generating the file. ## Managing entitlements diff --git a/product/admin/managing-resources.mdx b/product/admin/managing-resources.mdx index cce84737..0191c38d 100644 --- a/product/admin/managing-resources.mdx +++ b/product/admin/managing-resources.mdx @@ -51,7 +51,7 @@ In specific scenarios where a resource cannot be automatically ingested (such as Use **Configure columns** in the **Resources** table header to adjust which columns are visible — toggle columns on or off and drag to reorder. Your layout is saved automatically. -To export resources data to CSV, click **Generate CSV** above the **Resources** table. The **Download to CSV** drawer opens where you can choose which columns to include before generating the file. +To export resources data to CSV, click **Generate CSV** above the **Resources** table. The **Download as CSV** drawer opens where you can choose which columns to include before generating the file. ## Managing resources diff --git a/product/admin/mcp-server/google-analytics-admin.mdx b/product/admin/mcp-server/google-analytics-admin.mdx index 548c3000..d4aae60e 100644 --- a/product/admin/mcp-server/google-analytics-admin.mdx +++ b/product/admin/mcp-server/google-analytics-admin.mdx @@ -117,7 +117,7 @@ With your service account key ready, register the server and provide it as the c Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-server) and select **Google Analytics Admin** from the catalog. -When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **OAuth2 — JWT bearer** and provide the service account's JSON key and the scopes you need, such as `analytics.readonly` and `analytics.edit`. +When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **JWT Bearer (RFC 7523)** and provide the service account's JSON key and the scopes you need, such as `analytics.readonly` and `analytics.edit`. Save your changes. C1 starts a sync that discovers the tools the Google Analytics Admin server exposes. diff --git a/product/admin/mcp-server/google-drive.mdx b/product/admin/mcp-server/google-drive.mdx index 6baad64f..e7dfb5aa 100644 --- a/product/admin/mcp-server/google-drive.mdx +++ b/product/admin/mcp-server/google-drive.mdx @@ -116,7 +116,7 @@ With your service account ready, register the server and provide its key. Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-server) and select **Google Drive** from the catalog. -When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **OAuth2 — JWT bearer** and provide the service account's JSON key and the scopes you delegated. +When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **JWT Bearer (RFC 7523)** and provide the service account's JSON key and the scopes you delegated. Save your changes. C1 starts a sync that discovers the tools the Google Drive server exposes. diff --git a/product/admin/mcp-server/looker.mdx b/product/admin/mcp-server/looker.mdx index a6a508b6..5197fbca 100644 --- a/product/admin/mcp-server/looker.mdx +++ b/product/admin/mcp-server/looker.mdx @@ -67,7 +67,7 @@ Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-serve Enter your Looker instance URL when prompted. -When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **OAuth2 — client credentials** and enter your Looker **client ID** and **client secret**. +When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **Client credentials** and enter your Looker **client ID** and **client secret**. Save your changes. C1 starts a sync that discovers the tools the Looker server exposes. diff --git a/product/admin/mcp-server/wiz.mdx b/product/admin/mcp-server/wiz.mdx index d1a36028..a3c5728a 100644 --- a/product/admin/mcp-server/wiz.mdx +++ b/product/admin/mcp-server/wiz.mdx @@ -69,7 +69,7 @@ Follow [Register an MCP server](/product/admin/mcp-servers#register-an-mcp-serve Enter your regional Wiz API endpoint, such as `https://api.us1.app.wiz.io`. -When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **OAuth2 — client credentials** and enter the service account's **client ID** and **client secret**. +When you [configure authentication](/product/admin/mcp-servers#configure-authentication), choose **Client credentials** and enter the service account's **client ID** and **client secret**. Save your changes. C1 starts a sync that discovers the tools the Wiz server exposes. diff --git a/product/admin/mcp-servers.mdx b/product/admin/mcp-servers.mdx index af20dfce..e64e529c 100644 --- a/product/admin/mcp-servers.mdx +++ b/product/admin/mcp-servers.mdx @@ -53,10 +53,10 @@ C1 supports multiple auth methods for downstream MCP servers. Admins can select | **Bearer token** | A single shared service account | Simple integrations where per-user attribution downstream isn't required | | **Custom header** | A single shared identity via a custom HTTP header (for example, an API key) | Services that authenticate via a non-standard header or API key | | **Basic auth** | A single shared identity via username and password | Services that use HTTP Basic authentication | -| **OAuth2 — client credentials** | A single shared OAuth client | Machine-to-machine OAuth where per-user identity isn't needed | +| **Client credentials** | A single shared OAuth client | Machine-to-machine OAuth where per-user identity isn't needed | | **OAuth2 — service mode** | A single shared identity (admin authenticates once) | When the downstream requires an OAuth auth code flow but a single shared credential is acceptable | | **OAuth2 — per-user passthrough** | Each end user, with their own credentials | When the downstream needs per-user identity (Google Workspace, GitHub, Salesforce, and so on) | -| **OAuth2 — JWT bearer** | A service identity via signed JWT | Services that support certificate-based or JWT-based auth (for example, Tableau or Google service accounts) | +| **JWT Bearer (RFC 7523)** | A service identity via signed JWT | Services that support certificate-based or JWT-based auth (for example, Tableau or Google service accounts) | For per-user OAuth passthrough, C1 vaults each user's downstream tokens and auto-refreshes them so end users don't hit token expiry mid-session. diff --git a/product/admin/policies.mdx b/product/admin/policies.mdx index b51eb43b..ba3cd3b6 100644 --- a/product/admin/policies.mdx +++ b/product/admin/policies.mdx @@ -137,7 +137,7 @@ In the **Then perform this action:** section of the rule, select an automatic ac If necessary, click **Add step** to add additional actions or workflows to the rule. -Repeat the **Add another rule** process, adding as many conditional rules as needed. If necessary, you can use the arrow keys to change the order of your rules. +Repeat the **Add rule** process, adding as many conditional rules as needed. If necessary, you can use the arrow keys to change the order of your rules. Remember, for best results place more specific rules before less specific rules. diff --git a/product/admin/provisioning.mdx b/product/admin/provisioning.mdx index 8a9f9d01..245ad4cd 100644 --- a/product/admin/provisioning.mdx +++ b/product/admin/provisioning.mdx @@ -95,7 +95,7 @@ Manual provisioning can be configured by clicking the provisioning settings on a If there is an error or issue in provisioning, manual provisioning is used as the fallback method. In this scenario, the request is assigned to the application owner to resolve the issue. -## Method 4: Ticket-based provisioning +## Method 4: External ticketing **When to use?** @@ -184,7 +184,7 @@ By **default**, C1 attempts to infer and perform the **inverse action** of the c * If the provisioning method is **Linked entitlements**, the system will remove the linked entitlement in the SSO directory or identity provider. -* If the provisioning method is **Ticket-based provisioning**, a helpdesk ticket will be created to initiate the removal of access. +* If the provisioning method is **External ticketing**, a helpdesk ticket will be created to initiate the removal of access. ### Set a custom deprovisioning flow for an entitlement diff --git a/product/admin/role-mining.mdx b/product/admin/role-mining.mdx index 2f900f73..c56406ab 100644 --- a/product/admin/role-mining.mdx +++ b/product/admin/role-mining.mdx @@ -29,10 +29,10 @@ If you're starting from a specific entitlement and want to know who should have Navigate to **Governance** > **Role mining**. - In the **Filter** section, click **+ Add filter**. Select a user attribute — such as Department, Job title, Manager, or Employment status — then select one or more values. + In the **Filter** section, click **Add filter**. Select a user attribute — such as Department, Job title, Manager, or Employment status — then select one or more values. - Add more filters as needed with **+ Add filter**. C1 updates the results as you build your cohort. + Add more filters as needed with **Add filter**. C1 updates the results as you build your cohort. diff --git a/product/admin/secret-sharing.mdx b/product/admin/secret-sharing.mdx index 8ce61544..b77f38d3 100644 --- a/product/admin/secret-sharing.mdx +++ b/product/admin/secret-sharing.mdx @@ -80,7 +80,7 @@ Click the share URL. Authenticate with your organization's SSO if you're not already signed in. -Click **Reveal content** or **Download file**. +Click **Reveal secret** or **Download file**. @@ -96,7 +96,7 @@ Enter your email address and click **Send magic link**. Click the magic link in your inbox. The link expires in 15 minutes and can only be used once. -Click **Reveal content** or **Download file**. +Click **Reveal secret** or **Download file**. diff --git a/product/admin/service-principals/custom-oidc.mdx b/product/admin/service-principals/custom-oidc.mdx index d9045ea1..4f9af543 100644 --- a/product/admin/service-principals/custom-oidc.mdx +++ b/product/admin/service-principals/custom-oidc.mdx @@ -81,7 +81,7 @@ claims.sub == "expected-subject" && claims.custom_claim == "expected-value" - Expressions are limited to 1,024 bytes {/* -Use the **Test CEL** tool at **Settings** > **Workload Federation** to validate your expressions against sample claims before deploying. +Use the **Test expression** tool at **Settings** > **Workload Federation** to validate your expressions against sample claims before deploying. */} ## Using with C1 tools diff --git a/product/admin/service-principals/federation-setup.mdx b/product/admin/service-principals/federation-setup.mdx index d7ff323f..c0018961 100644 --- a/product/admin/service-principals/federation-setup.mdx +++ b/product/admin/service-principals/federation-setup.mdx @@ -77,7 +77,7 @@ Before deploying to production, test the federation trust to make sure your CEL {/* -You can also use the **Test CEL** tool at **Settings** > **Workload Federation** to test expressions against sample claims without a real JWT. This is useful for iterating on your CEL expression before creating a trust. +You can also use the **Test expression** tool at **Settings** > **Workload Federation** to test expressions against sample claims without a real JWT. This is useful for iterating on your CEL expression before creating a trust. */} ## Platform-specific guides diff --git a/product/admin/service-principals/security.mdx b/product/admin/service-principals/security.mdx index 859f9e18..1ed4bef7 100644 --- a/product/admin/service-principals/security.mdx +++ b/product/admin/service-principals/security.mdx @@ -113,7 +113,7 @@ Token operations are logged as OCSF Authentication events (class 3002). The `act | Event | Activity name | Description | | :--- | :--- | :--- | -| **Client credential grant** | `client_credentials` | Service principal authenticated with client ID + secret or client assertion | +| **Client credentials** | `client_credentials` | Service principal authenticated with client ID + secret or client assertion | | **Token exchange** | `token_exchange` | Workload federation token exchange attempt (success or failure) | Each authentication event includes: diff --git a/product/admin/step-up-auth.mdx b/product/admin/step-up-auth.mdx index 7793ccfb..98d7502c 100644 --- a/product/admin/step-up-auth.mdx +++ b/product/admin/step-up-auth.mdx @@ -119,7 +119,7 @@ In C1, navigate to **Admin** > **Integrations** > **Step up auth**. Click **Add step-up provider**. -Select **OAuth2 (RFC 9470 compliant)**. +Select **OAuth2**. Enter the following details: @@ -480,8 +480,8 @@ Save the policy. When a task requires step-up authentication for approval: -1. The task displays a "Requires Step Up Authentication" indicator. -2. Instead of a standard **Approve** button, users see **Approve with Step Up**. +1. The task displays a "(step-up required)" indicator. +2. Instead of a standard **Approve** button, users see **Approve (step-up required)**. 3. Clicking this button redirects the user to the configured identity provider. 4. The user completes the required authentication steps (such as MFA). 5. Upon successful authentication, the user is returned to C1. diff --git a/product/admin/tool-call-hooks.mdx b/product/admin/tool-call-hooks.mdx index f539a014..92c70550 100644 --- a/product/admin/tool-call-hooks.mdx +++ b/product/admin/tool-call-hooks.mdx @@ -35,7 +35,7 @@ Every hook execution is recorded in the [audit log](/product/admin/audit-ai-tool Go to **AI > C1 Gateway > Settings** and find the **Hooks** section. -Click **Add hook**. +Click **New hook**. Fill out the form: diff --git a/product/admin/tools-and-toolsets.mdx b/product/admin/tools-and-toolsets.mdx index b03dfac3..de324870 100644 --- a/product/admin/tools-and-toolsets.mdx +++ b/product/admin/tools-and-toolsets.mdx @@ -101,8 +101,8 @@ A **toolset** is a named bundle of approved tools. C1 ships and auto-maintains two toolsets per tenant: -- **All approved tools** — every tool in **Approved** state across the server. -- **All read tools** — every **Approved** tool with Action = Read. +- **All approved** — every tool in **Approved** state across the server. +- **Read-only** — every **Approved** tool with Action = Read. Both update automatically as tools are approved or disabled. They are read-only — admins can bind them to access profiles but cannot edit their contents. @@ -115,7 +115,7 @@ Custom toolsets are manually curated — they do **not** auto-populate based on Go to **AI access management > Toolsets**. -Click **Add toolset**. +Click **Create toolset**. Enter a **name**. **Optional.** Enter a **description**. @@ -158,7 +158,7 @@ You can also start from the access profile side and add toolsets as entitlements Go to **Access profiles** and either create a new profile or open an existing one. -Add the toolset as an entitlement — both C1-maintained toolsets (**All approved tools**, **All read tools**) and custom toolsets appear as options. +Add the toolset as an entitlement — both C1-maintained toolsets (**All approved**, **Read-only**) and custom toolsets appear as options. Set the access policy on the profile (auto-approve, JIT with expiry, or approval required). diff --git a/product/how-to/create-requests.mdx b/product/how-to/create-requests.mdx index be346d4d..33308c46 100644 --- a/product/how-to/create-requests.mdx +++ b/product/how-to/create-requests.mdx @@ -158,7 +158,7 @@ If you already know what access you need, use the **New request** page to quickl -In C1, click **+ New request** and select the **Access profiles** tab. +In C1, click **New request** and select the **Access profiles** tab. @@ -187,7 +187,7 @@ C1 will send you an email when your requests are approved or rejected, and anoth -In C1, click **+ New request** and select the **Apps** tab. +In C1, click **New request** and select the **Apps** tab. diff --git a/product/how-to/qs-on-call-access-control.mdx b/product/how-to/qs-on-call-access-control.mdx index ab825acf..81e24225 100644 --- a/product/how-to/qs-on-call-access-control.mdx +++ b/product/how-to/qs-on-call-access-control.mdx @@ -95,7 +95,7 @@ Go to the access profile's **JML** page. Find the **Joiner** section of the page and click **Edit**. -Use the **Approval policy** dropdown to select **Auto approval**. +Use the **Approval policy** dropdown to select **Auto-approve**. Click **Save**. diff --git a/product/how-to/qs-self-service-requests.mdx b/product/how-to/qs-self-service-requests.mdx index 02da3700..b3d7a97c 100644 --- a/product/how-to/qs-self-service-requests.mdx +++ b/product/how-to/qs-self-service-requests.mdx @@ -63,7 +63,7 @@ Let's walk through the experience of a C1 end user requesting the **Connector Ad -Click **+ New request**. +Click **New request**. In the **Who needs this access?** field, your name is pre-populated. Leave this as-is. diff --git a/product/how-to/request-actions.mdx b/product/how-to/request-actions.mdx index b161b63b..89accd2a 100644 --- a/product/how-to/request-actions.mdx +++ b/product/how-to/request-actions.mdx @@ -23,7 +23,7 @@ You can find and request actions in three places: 1. **Actions catalog**: Navigate to **Requests** > **Actions** to see all the actions available to you. -2. **New request form**: Click **+ New request** and select the **Actions** tab. +2. **New request form**: Click **New request** and select the **Actions** tab. 3. **AI assistant**: Ask the C1 AI assistant in the C1 app for Slack what actions are available to you. @@ -35,7 +35,7 @@ You'll only see actions that you have permission to request. If you don't see an -Navigate to **Browse** > **Actions** or click **+ New request** and select the **Actions** tab. +Navigate to **Browse** > **Actions** or click **New request** and select the **Actions** tab. Browse or search for the action you need and click on it.