Salesforce · Agentforce HR Service

Employee Profile Management

A subagent of the Agentforce HR Service Agent template that handles employee conversational requests to update supported profile information (name, contact details, address, pronouns) through the Update Employee Profile action, which runs a Flow reference action and returns a status message and case number.

Recorded characteristics

Function
Salesforce documents the Employee Profile Management Subagent (API name EmployeeProfileManagement) as handling "employee actions related to updating profile information, such as address, phone number, email address, first name, and last name". Salesforce states subagents were "previously referred to as topics". The subagent page lists exactly one included agent tool: Update Employee Profile. The Update Employee Profile Action page documents API Name UpdateEmployeeProfile, Action Type Standard, Reference Action Type Flow, Reference Action "Update Employee Profile", inputs "First Name, Last Name, Mobile Number, Address, City, Country, Email Address, Province or State, Postal or Zip Code, Pronouns, Service Process Name", outputs "Status Message, Case Number", and answers "No" to whether the action executes prompt templates. Documented triggering utterances are employee-scoped, for example "Update my phone number to (780) 555-1234." and "Update my last name to Doe." Salesforce lists this subagent under "Standard Subagents Requiring Custom Integration", whose underlying tools "require a third-party system integration (such as Workday or SAP SuccessFactors) through a custom Mule application". Separately, Salesforce documents a MuleSoft Direct integration app, "Employee Profile Update", enabled from Setup > Integrations > MuleSoft Direct, which lets employees "update their profile details, such as name and contact information directly from Employee Portal by using the Agentforce or service process" and states "The changes automatically syncs with Workday." Salesforce does not describe a native Salesforce-only implementation of this subagent's update tool. The subagent setup requires substituting a service process ID for the <service_process_name> placeholder, and the HR Service agent template article instructs administrators to "Update the named credential when configuring these actions: Get Leave Balance, Submit Leave Request, Update Employee Profile, Get Direct Deposit Details, and Submit Direct Deposit Details."
Data access
Documented inputs to the action are the conversationally supplied profile values themselves (first name, last name, mobile number, address, city, country, email address, province or state, postal or zip code, pronouns) plus a Service Process Name. Salesforce does not document the Update Employee Profile action reading an existing employee record before writing. A separate action, Get Employee Profile (API name GetEmployeeProfile, inputs "User Input", outputs "User Details and User Details Output Map"), is documented with the note "This action queries Salesforce Core. You can use it if your employee data is stored in or synced with Salesforce Core", but it is not listed among the Employee Profile Management Subagent's included agent tools. All documented example utterances are first-person and employee-scoped; manager or third-party profile editing is not documented for this subagent. Salesforce does not enumerate what employee data the action can read beyond the supplied inputs.
Actions
Can take actions
External actions
Conditional
Human confirmation
Not established
Permission basis
Mixed
Administrative control
The subagent and its single action are part of the Agentforce HR Service Agent template, created in Setup > Agentforce Agents > New Agent > Create from a Template. The template list includes an "Employee Profile Management" template described as "Retrieves and updates employee profile details, such as: Contact info, Address, Emergency contact, Manager details, Job information". Salesforce documents these administrator steps: review and remove template topics that do not apply; define agent settings such as system messages and language settings; select a grounding data source or data library; configure topics, actions and other agent assets; update the named credential for listed actions including Update Employee Profile; test in Agentforce Builder; and activate the agent. The subagent page carries the notice "This topic contains potentially sensitive actions. To use this topic, customize this action according to your business's security requirements." Building and managing HR service agents requires Manage Agentforce Service Agents AND Manage AI Agents, OR Customize Application; enabling agents requires Manage AI Agents AND Employee Service: Agentforce, OR Customize Application. Enabling the MuleSoft Direct "Employee Profile Update" integration app requires a Salesforce Administrator profile with the SvcCloudEmpHubHrAddOn license AND a MuleSoft Administrator profile. Salesforce trust guidance recommends granting agents the minimum user permissions required and building identity confirmation and access control directly into the flow of sensitive actions. No per-action confirmation toggle specific to this action is documented.
Default state
Disabled
Availability
The Update Employee Profile Action page states "Available in: Lightning Experience" and "Available in: Unlimited Edition with Employee Service". The HR Service agent template "is available with Agentforce Employee Agent (AEA)", and prerequisites are to "set up Einstein Generative AI, enable Agentforce, and set up Einstein Trust Layer". The subagent is listed among standard subagents requiring third-party HCM integration (such as Workday or SAP SuccessFactors) through a custom Mule application; the MuleSoft Direct Employee Profile Update app documents Workday sync specifically. Salesforce states that "Multilingual support for the Get Leave Balance Action, Apply For Leave Action, Update Employee Profile Action, Get Enablement Program Action, Get Expense Items Action, Get Past Expense Reports Action, Submit Expense Report Action, and Create Confidential Complaint Action is generally available for Agentforce HR Service Agent actions", while multilingual support for the remaining HR Service actions is a pilot or beta service. This multilingual GA statement is specific to language support and is not a general-availability statement about the product. No beta, pilot or preview stage statement was found for the subagent or action themselves.
Licensing
Documented requirements: Unlimited Edition with Employee Service; Lightning Experience; Agentforce Employee Agent (AEA) for the HR Service agent template; Einstein Generative AI, Agentforce enablement and Einstein Trust Layer setup; for the MuleSoft Direct path, the SvcCloudEmpHubHrAddOn license and MuleSoft Administrator profile. No pricing is documented on the pages reviewed.
External model or provider
Not established
Limitations and uncertainty
Not established: whether the Update Employee Profile action itself persists changes in the external HCM, or whether it submits a request that an HR service process or integration completes. Salesforce documents the action's outputs as "Status Message, Case Number" but does not state whether each update creates a Salesforce case, references an existing case, or merely returns a workflow reference; the presence of a case number is therefore recorded as documented output only. Salesforce states the full address, "including Address Line, City, State, Country, and Zip Code, must be provided. Individual components of the address cannot be updated separately", but does not state whether that constraint originates in the action, the service process or the downstream HCM. The HR Service Agent template description for "Employee Profile Management" mentions retrieving and updating emergency contact, manager details and job information, while the subagent page lists only the Update Employee Profile tool and the action page enumerates a narrower field list; this discrepancy is unresolved. Whether the subagent can also run the separate Get Employee Profile action is not documented. Salesforce does not identify a model or provider for this action, does not document action-invocation history, before/after profile values, or AI-specific audit records for it, and does not document the runtime permissions held by the Agent User for this action or whether the action independently enforces employee scope. Human confirmation is recorded as not_established: Salesforce only recommends configuring the agent to confirm the requester's identity, which is a recommended safeguard rather than a documented mandatory runtime confirmation step.

Evidence