Skip to content

Commit a6cd712

Browse files
docs: fix typo
1 parent 26766b8 commit a6cd712

1 file changed

Lines changed: 16 additions & 7 deletions

File tree

messages/create_agent_user.md

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,26 +11,33 @@ By default, this command:
1111
- Generates a user called "Agent User" with a globally unique username. Use flags to change these default names.
1212
- Sets the user's email to the new username.
1313
- Assigns the user the "Einstein Agent User" profile.
14-
- Assigns the user these required permission sets: AgentforceServiceAgentBase, AgentforceServiceAgentUser, EinsteinGPTPromptTemplateUser
14+
- Assigns the user these required permission sets: AgentforceServiceAgentBase, AgentforceServiceAgentUser,
15+
EinsteinGPTPromptTemplateUser
1516
- Checks that the user licenses required by the profile and permission sets are available in your org.
1617

17-
The generated user doesn't have a password. You can’t log into Salesforce using the agent user's username. Only Salesforce users with admin permissions can view or edit an agent user in Setup.
18+
The generated user doesn't have a password. You can’t log into Salesforce using the agent user's username. Only
19+
Salesforce users with admin permissions can view or edit an agent user in Setup.
1820

19-
To assign additional permission sets or licenses after the user was created, use the "org assign permset" or "org assign permsetlicense" commands.
21+
To assign additional permission sets or licenses after the user was created, use the "org assign permset" or "org assign
22+
permsetlicense" commands.
2023

21-
When the command completes, it displays a summary of what it did, including the new agent user's username and ID, the available licenses associated with the Einstein Agent User profile, and the profile and permission sets assigned to the agent user.
24+
When the command completes, it displays a summary of what it did, including the new agent user's username and ID, the
25+
available licenses associated with the Einstein Agent User profile, and the profile and permission sets assigned to the
26+
agent user.
2227

2328
# examples
2429

2530
- Create an agent user with an auto-generated username; create the user in the org with alias "myorg":
2631

2732
<%= config.bin %> <%= command.id %> --target-org myorg
2833

29-
- Create an agent user by specifying a base usernmane pattern; to make the username unique, the command appends a unique identifier:
34+
- Create an agent user by specifying a base username pattern; to make the username unique, the command appends a unique
35+
identifier:
3036

3137
<%= config.bin %> <%= command.id %> --base-username service-agent@corp.com --target-org myorg
3238

33-
- Create an agent user with an auto-generated username but the custom name "Service Agent"; create the user in your default org:
39+
- Create an agent user with an auto-generated username but the custom name "Service Agent"; create the user in your
40+
default org:
3441

3542
<%= config.bin %> <%= command.id %> --first-name Service --last-name Agent
3643

@@ -44,7 +51,9 @@ Base username pattern. A unique ID is appended to ensure global uniqueness of th
4451

4552
# flags.base-username.description
4653

47-
Specify a base username in email format, such as "service-agent@corp.com". The command then appends a 12-character globally unique ID (GUID) to the name before the "@" sign, which ensures that the username is globally unique across all Salesforce orgs and sandboxes.
54+
Specify a base username in email format, such as "service-agent@corp.com". The command then appends a 12-character
55+
globally unique ID (GUID) to the name before the "@" sign, which ensures that the username is globally unique across all
56+
Salesforce orgs and sandboxes.
4857

4958
For example, if you specify "service-agent@corp.com", then the username might be "service-agent.a1b2c3d4e5f6@corp.com".
5059

0 commit comments

Comments
 (0)