From 19d27c9e477ea0fed9e25abb1b40f04cfa9af87e Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 6 Feb 2026 22:20:41 +0000 Subject: [PATCH 1/3] Add user attribute push rules documentation --- product/admin/attribute-push-rules.mdx | 113 +++++++++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 product/admin/attribute-push-rules.mdx diff --git a/product/admin/attribute-push-rules.mdx b/product/admin/attribute-push-rules.mdx new file mode 100644 index 0000000..729e0a6 --- /dev/null +++ b/product/admin/attribute-push-rules.mdx @@ -0,0 +1,113 @@ +--- +title: "User attribute push rules" +description: "User attribute push rules allow you to automatically sync user attributes from ConductorOne to your connected applications. This ensures that user data stays consistent across your integrated systems." +--- + +## Overview + +Attribute push rules give you control over which user attributes are synchronized to specific applications and how they're mapped. With these rules, you can sync ConductorOne attributes to application user profiles and transform attribute values using expressions. You can also target specific users based on conditions and map to both standard and custom attributes when supported by the connector. + +## When to use attribute push rules + +Use attribute push rules when you need to keep user profile data synchronized across applications or populate custom user fields in connected applications. They're also helpful for maintaining consistent user attributes for compliance or operational purposes, as well as transforming or deriving attribute values before syncing to applications. + +## How attribute push works + +When you create a push rule configuration: + +1. Select the connector you want to push attributes to +2. Map ConductorOne attributes to the target application's user attributes +3. Optionally, use CEL expressions to transform values +4. Choose which users to target (all users or specific users) +5. Enable the configuration to begin syncing + +Attributes are pushed to the connected application automatically when: + +- The push configuration is created or updated +- A user's attribute values change in ConductorOne +- You manually trigger a push + +## Configure attribute push rules + +### Prerequisites + +- Admin permissions in ConductorOne +- A configured connector for the target application +- User attribute mappings defined in ConductorOne (Admin \> Settings \> User data sources) + +### Create a push rule + +1. Navigate to **Admin \> Settings \> User data sources** +2. Select the **Push rules** tab +3. Click **Add push rule** +4. Select the connector you want to push attributes to +5. For each attribute you want to sync: + - Choose the target attribute name from the connector's available attributes + - Select a ConductorOne attribute to map, or write a CEL expression for custom logic + - If the connector supports custom attributes, you can specify a custom name +6. Under **User targeting**, choose: + - **All users**: Push attributes for all users in your tenant + - **Specific users**: Use a CEL expression to target users matching specific criteria +7. Enable the push rule +8. Click **Save** + +### Edit or disable a push rule + +1. Navigate to **Admin \> Settings \> User data sources \> Push rules** +2. Find the push rule in the list +3. Click the menu button (...) and select: + - **Edit**: Modify attribute mappings or user targeting + - **Enable** or **Disable**: Turn the push rule on or off + - **Delete**: Remove the push rule completely + +## Attribute mappings + +### Map to ConductorOne attributes + +Select a ConductorOne attribute from the dropdown to sync its value directly to the target application. + +**Example**: Map the `Department` attribute in ConductorOne to the `department` field in the target application. + +### Use CEL expressions + +For more advanced scenarios, you can use CEL (Common Expression Language) expressions to transform or derive attribute values. + +**Example**: Combine first and last name into a display name + +```cel +user.first_name + " " + user.last_name +``` + +**Example**: Set a value based on a condition + +```cel +user.department == "Engineering" ? "tech@company.com" : "general@company.com" +``` + +## User targeting + +### All users + +Syncs attributes for all users in your ConductorOne tenant. + +### Specific users (CEL expression) + +Use a CEL expression to target specific users based on their attributes. + +**Example**: Target only active employees + +```cel +user.status == "active" && user.employment_type == "full_time" +``` + +**Example**: Target users in specific departments + +```cel +user.department in ["Engineering", "Product", "Design"] +``` + +## Custom attributes + +Some connectors support pushing to custom attributes that aren't part of the standard user schema. When configuring a push rule for these connectors, you can specify custom attribute names. + +Check the connector's schema to see if custom attributes are supported. \ No newline at end of file From ca3d080e47bd364be4f872df15b16560bf0f591a Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Mon, 9 Feb 2026 14:23:22 -0800 Subject: [PATCH 2/3] Improve structure and tone of attribute push rules doc - Add complete frontmatter (og:title, og:description, sidebarTitle) - Convert procedural steps to components - Tighten intro into scannable bullet list - Convert "when to use" section to bullet list - Fix navigation path formatting (> instead of \>) - Rename "Map to ConductorOne attributes" to "Direct attribute mapping" - Rename "Use CEL expressions" to "CEL expressions" - Remove redundant "(CEL expression)" from heading - Minor copy edits for conciseness Co-Authored-By: Claude Opus 4.5 --- product/admin/attribute-push-rules.mdx | 88 +++++++++++++++++++------- 1 file changed, 64 insertions(+), 24 deletions(-) diff --git a/product/admin/attribute-push-rules.mdx b/product/admin/attribute-push-rules.mdx index 729e0a6..2661558 100644 --- a/product/admin/attribute-push-rules.mdx +++ b/product/admin/attribute-push-rules.mdx @@ -1,23 +1,34 @@ --- -title: "User attribute push rules" -description: "User attribute push rules allow you to automatically sync user attributes from ConductorOne to your connected applications. This ensures that user data stays consistent across your integrated systems." +title: "Attribute push rules" +og:title: "Attribute push rules" +description: "Automatically sync user attributes from ConductorOne to connected applications to keep user data consistent across your integrated systems." +og:description: "Automatically sync user attributes from ConductorOne to connected applications to keep user data consistent across your integrated systems." +sidebarTitle: "Attribute push rules" --- -## Overview +Attribute push rules let you control which user attributes are synchronized to specific applications and how they're mapped. You can: -Attribute push rules give you control over which user attributes are synchronized to specific applications and how they're mapped. With these rules, you can sync ConductorOne attributes to application user profiles and transform attribute values using expressions. You can also target specific users based on conditions and map to both standard and custom attributes when supported by the connector. +- Sync ConductorOne attributes to application user profiles +- Transform attribute values using CEL expressions +- Target specific users based on conditions +- Map to both standard and custom attributes (when supported by the connector) ## When to use attribute push rules -Use attribute push rules when you need to keep user profile data synchronized across applications or populate custom user fields in connected applications. They're also helpful for maintaining consistent user attributes for compliance or operational purposes, as well as transforming or deriving attribute values before syncing to applications. +Use attribute push rules when you need to: + +- Keep user profile data synchronized across applications +- Populate custom user fields in connected applications +- Maintain consistent user attributes for compliance or operational purposes +- Transform or derive attribute values before syncing ## How attribute push works -When you create a push rule configuration: +When you create a push rule: 1. Select the connector you want to push attributes to 2. Map ConductorOne attributes to the target application's user attributes -3. Optionally, use CEL expressions to transform values +3. Optionally use CEL expressions to transform values 4. Choose which users to target (all users or specific users) 5. Enable the configuration to begin syncing @@ -33,44 +44,73 @@ Attributes are pushed to the connected application automatically when: - Admin permissions in ConductorOne - A configured connector for the target application -- User attribute mappings defined in ConductorOne (Admin \> Settings \> User data sources) +- User attribute mappings defined in ConductorOne (**Admin** > **Settings** > **User data sources**) ### Create a push rule -1. Navigate to **Admin \> Settings \> User data sources** -2. Select the **Push rules** tab -3. Click **Add push rule** -4. Select the connector you want to push attributes to -5. For each attribute you want to sync: + + +Navigate to **Admin** > **Settings** > **User data sources**. + + +Select the **Push rules** tab. + + +Click **Add push rule**. + + +Select the connector you want to push attributes to. + + +For each attribute you want to sync: + - Choose the target attribute name from the connector's available attributes - Select a ConductorOne attribute to map, or write a CEL expression for custom logic - If the connector supports custom attributes, you can specify a custom name -6. Under **User targeting**, choose: + + +Under **User targeting**, choose: + - **All users**: Push attributes for all users in your tenant - **Specific users**: Use a CEL expression to target users matching specific criteria -7. Enable the push rule -8. Click **Save** + + +Enable the push rule. + + +Click **Save**. + + ### Edit or disable a push rule -1. Navigate to **Admin \> Settings \> User data sources \> Push rules** -2. Find the push rule in the list -3. Click the menu button (...) and select: + + +Navigate to **Admin** > **Settings** > **User data sources** > **Push rules**. + + +Find the push rule in the list. + + +Click the menu button (...) and select: + - **Edit**: Modify attribute mappings or user targeting - **Enable** or **Disable**: Turn the push rule on or off - **Delete**: Remove the push rule completely + + ## Attribute mappings -### Map to ConductorOne attributes +### Direct attribute mapping Select a ConductorOne attribute from the dropdown to sync its value directly to the target application. **Example**: Map the `Department` attribute in ConductorOne to the `department` field in the target application. -### Use CEL expressions +### CEL expressions -For more advanced scenarios, you can use CEL (Common Expression Language) expressions to transform or derive attribute values. +For more advanced scenarios, use CEL (Common Expression Language) expressions to transform or derive attribute values. **Example**: Combine first and last name into a display name @@ -90,7 +130,7 @@ user.department == "Engineering" ? "tech@company.com" : "general@company.com" Syncs attributes for all users in your ConductorOne tenant. -### Specific users (CEL expression) +### Specific users Use a CEL expression to target specific users based on their attributes. @@ -110,4 +150,4 @@ user.department in ["Engineering", "Product", "Design"] Some connectors support pushing to custom attributes that aren't part of the standard user schema. When configuring a push rule for these connectors, you can specify custom attribute names. -Check the connector's schema to see if custom attributes are supported. \ No newline at end of file +Check the connector's documentation to see if custom attributes are supported. From 7e621b53660705f944d0803118b586b8dbf59bfc Mon Sep 17 00:00:00 2001 From: Mindy Moreland Date: Mon, 9 Feb 2026 14:26:58 -0800 Subject: [PATCH 3/3] Add CEL code block guidance and fix syntax highlighting - Add note to docs-writing skill: use `go` for CEL expressions (CEL not recognized) - Update attribute-push-rules.mdx code blocks from `cel` to `go` Co-Authored-By: Claude Opus 4.5 --- .claude/skills/docs-writing.md | 1 + product/admin/attribute-push-rules.mdx | 8 ++++---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/.claude/skills/docs-writing.md b/.claude/skills/docs-writing.md index 6f6d985..01327e4 100644 --- a/.claude/skills/docs-writing.md +++ b/.claude/skills/docs-writing.md @@ -77,6 +77,7 @@ Follow this process when creating ConductorOne documentation: ## Technical Standards - Add language tags to all code blocks +- For CEL expressions, use `go` as the language tag (CEL isn't recognized for syntax highlighting) - Use relative paths for internal links - Include alt text on all images - List prerequisites at the start of procedural content diff --git a/product/admin/attribute-push-rules.mdx b/product/admin/attribute-push-rules.mdx index 2661558..42d9aef 100644 --- a/product/admin/attribute-push-rules.mdx +++ b/product/admin/attribute-push-rules.mdx @@ -114,13 +114,13 @@ For more advanced scenarios, use CEL (Common Expression Language) expressions to **Example**: Combine first and last name into a display name -```cel +```go user.first_name + " " + user.last_name ``` **Example**: Set a value based on a condition -```cel +```go user.department == "Engineering" ? "tech@company.com" : "general@company.com" ``` @@ -136,13 +136,13 @@ Use a CEL expression to target specific users based on their attributes. **Example**: Target only active employees -```cel +```go user.status == "active" && user.employment_type == "full_time" ``` **Example**: Target users in specific departments -```cel +```go user.department in ["Engineering", "Product", "Design"] ```