--- schema_version: "1" id: 5ea9a28c4c06d848a8385c13d915e472fb40fa3c5bec4f76c996840cb93d9dec title: Workflow for the User Object (Beta) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/workflow_user_object_limitations.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.workflow_user_object_limitations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: bb49d7b615bca2e0067d2bc794bc9e3c2a455d86d1550c06dd7667896c9368a8 description: You can create workflow rules and actions for the User object. You can, for example, send welcome emails to new employees or sync user data with a third-party service using outbound message actions. products: - Flow Builder - Salesforce Platform release: "264" --- # Workflow for the User Object (Beta) You can create workflow rules and actions for the User object. You can, for example, send welcome emails to new employees or sync user data with a third-party service using outbound message actions. ### Required Editions
Available in: Lightning Experience and Salesforce Classic
Available in: Enterprise, Performance, Unlimited, and Developer Editions
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png) Important Support and updates for Workflow Rules have ended as of December 31, 2025. This means that support won't be provided for any workflow rules and bugs in the Workflow Rules product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US). After December 31, 2025, existing workflow rules continue to run, and you can activate, deactivate, and edit them; however we recommend using Flow Builder. To migrate existing workflow rules, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules."). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note This release contains a beta version of workflow on the User object that is production quality but has known limitations. To provide feedback and suggestions, go to [IdeaExchange](http://success.salesforce.com/ideaView?id=08730000000Br80AAC). ## Example Use Cases For the User object, you can set up workflow rules to: - Send welcome email messages with training resources to newly created users by using email alert actions. - Send emails when users change roles or are deactivated by using email alert actions. - Deactivate temporary employees after a specified period by using field update actions. - Sync user data with third-party systems by using outbound messages actions. ## Merge Field Types for the User Object To use merge fields from user records in email templates, select from the following merge field types: - User Fields—Use these merge fields to represent the sending user. Merge fields named {!User.field\_name} return values from the user record of the person who created or updated the record that triggered the workflow rule. - Workflow Target User Fields—Use these merge fields only in email templates for workflow rules on the User object. Merge fields named {!Target\_User.field\_name} return values from the user record that was created or updated to trigger the workflow rule. ## Beta Limitations for Workflow on the User Object Understand these limitations before you create workflow rules or workflow actions for the User object. - Tasks aren’t supported as workflow actions for the User object. - When setting the workflow rule criteria, you can’t select Current User fields using the picklists. You can, however, use a formula to set the rule criteria and include fields from the current user. In the formula editor, click **Insert Field**, select $User, select the field, and click **Insert**. - Remember that custom validation rules run _before_ workflow rules are executed. Refer to [Triggers and Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) in the Apex Developer Guide. #### See Also - [Workflow Considerations](https://help.salesforce.com/s/articleView?id=platform.workflow_rules_considerations.htm&release=264.0.0&type=5 "Learn the intricacies of workflow rules and workflow actions before you begin working with them.")