# How do I keep human and Agent CLI identities separate?

Company: Socra — Multiply Your Judgment
Canonical URL: https://support.socra.com/articles/art_01m46em4ptana5mdxxstymvhcp-identity-profiles

Use named Account profiles to keep local identities separate. Selecting a profile sets the default identity for existing product commands. Commands that support named profiles can select a different identity through an explicit profile option or `SOCRA_ACCOUNT_PROFILE`. A profile name does not itself grant access or turn a human identity into an Agent.

List the saved profiles without printing their credentials:

```sh
socra account profile list
```

To create or refresh a named human profile, run:

```sh
socra account login --profile personal
```

Complete the human browser login and select the intended Account. Agent identities must be enrolled through the Agent's supported setup; human login is not Agent enrollment.

To select an existing profile, replace `PROFILE_NAME` with its saved name:

```sh
socra account profile use PROFILE_NAME
socra account status
```

Check the active identity and Account before running a command that changes data. If the identity remains unexpected after selecting a profile, check whether `SOCRA_ACCOUNT_PROFILE` is set. The star in `profile list` marks the saved active profile; an environment override can make a profile-aware command use another identity. Switching profiles does not copy resources or permissions between them. It also affects other product commands sharing that CLI installation.

You can rename a profile without changing its identity:

```sh
socra account profile rename OLD_NAME NEW_NAME
```

Keep names clear enough to distinguish people, Agents, and Accounts. Do not share saved credential files as a way to give another person or Agent access.

## Article details

- Collection: [CLI](https://support.socra.com/collections/col_01m3xd0kvrzp27sgry6tjr6y9z-cli)
- Canonical: https://support.socra.com/articles/art_01m46em4ptana5mdxxstymvhcp-identity-profiles