User Management in Setup with Agentforce
Use Agentforce to clone users and manage their details, access assignments, and passwords.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Foundations or Agentforce 1 Editions |
| User Permissions Needed | |
|---|---|
| To use Setup with Agentforce: | The required permissions for Setup with Agentforce. See Grant Permissions to Use Setup with Agentforce. AND The required permissions for the task listed in the table. |
Agentforce can help you with these tasks and requests related to user management.
| Supported Task | Example Requests | Additional Required User Permissions |
|---|---|---|
| Get information on supported tasks for user management |
|
None |
| Clone a new user with or without access assignments |
|
Manage Users OR Manage Internal Users |
| Edit a user |
|
Manage Users OR Manage Internal Users |
| Add or remove users from permission sets, permission set groups, public groups, and queues |
|
Assign Permission Sets OR Manage Users |
| Freeze or unfreeze a user |
|
Manage Users OR Freeze Users |
| Reset a user’s password |
|
Manage Users OR Reset User Passwords and Unlock Users |
| Get user information |
|
None |
| Get a list of users matching specific criteria |
|
None |
| Get a list of active sessions |
|
None |
| Revoke sessions by user or app |
|
Manage Users |
| Compare two users |
|
None |
User Management Considerations
- Custom user fields are always displayed after the standard user fields in the User record.
- You only see the user fields that you have permission to view.
- You must have edit access to the User object to edit users via Setup with Agentforce.
- When you clone a user, only their direct public group and queue memberships are copied to the new user. Indirect memberships aren't included, such as when a user's group membership is via a nested public group.
Did this article solve your issue?
Let us know so we can improve!
