UiPath Documentation
uipath-cli
latest
false
Guia do usuário da UiPath CLI
Importante :
Este conteúdo foi traduzido com auxílio de tradução automática. A localização de um conteúdo recém-publicado pode levar de 1 a 2 semanas para ficar disponível.

uip ou usuários

Sintaxe e opções para "uip or user", que gerencia os usuários do tenant do Orchestrator e suas atribuições de pasta e função.

uip or users manages Orchestrator users at the tenant level. Orchestrator users are backed by Identity Service (IS) — this tool does not create standalone users from scratch. Instead, users import references an existing IS directory principal (a user, group, robot account, or external application) and provisions it into the tenant; users update then edits the tenant-side properties (license, session permissions, unattended credentials) that live on the Orchestrator side. There is no users delete — user removal is managed through Identity Service or the Orchestrator portal, not this CLI. For folder-level role management, see uip or roles.

Resumo

uip or users list [options]
uip or users list-in-folder [--folder-path <path> | --folder-key <key>] [options]
uip or users list-available [--folder-path <path> | --folder-key <key>] [options]
uip or users get <user-key>
uip or users import (--username <name> | --directory-id <id>) --type <type> [--folder-path <path> | --folder-key <key>] [--role-keys <keys>]
uip or users assign --user-key <key> [--folder-path <path> | --folder-key <key>] [--role-keys <keys>]
uip or users unassign --user-key <key> [--folder-path <path> | --folder-key <key>]
uip or users update <user-key> [options]
uip or users current
uip or users assign-roles <user-key> --role-keys <keys>
uip or users list [options]
uip or users list-in-folder [--folder-path <path> | --folder-key <key>] [options]
uip or users list-available [--folder-path <path> | --folder-key <key>] [options]
uip or users get <user-key>
uip or users import (--username <name> | --directory-id <id>) --type <type> [--folder-path <path> | --folder-key <key>] [--role-keys <keys>]
uip or users assign --user-key <key> [--folder-path <path> | --folder-key <key>] [--role-keys <keys>]
uip or users unassign --user-key <key> [--folder-path <path> | --folder-key <key>]
uip or users update <user-key> [options]
uip or users current
uip or users assign-roles <user-key> --role-keys <keys>

Verbo

TextoFinalidade
listLista os usuários do tenant com filtros opcionais.
list-in-folderLista os usuários atribuídos a uma pasta, com suas funções no nível da pasta.
list-availableLista os usuários que ainda podem ser atribuídos a uma pasta (ainda não atribuída).
getBusca um usuário por chave.
importImport an existing Identity Service directory principal into the tenant.
assignAtribua um usuário a uma pasta, opcionalmente com funções no nível da pasta.
unassignRemove um usuário de uma pasta.
update (alias edit)Update a user's tenant-side properties (PATCH semantics).
currentRetorne detalhes do usuário atualmente autenticado.
assign-rolesSubstitui as atribuições de função no nível do tenant de um usuário.

uip ou lista de usuários

Liste usuários no tenant. Retorna a chave do usuário (GUID), nome de usuário, nome completo, email, tipo e status ativo.

Opções

ShortLongValorPadrãoDescription
--keyGUIDFiltra por chave de usuário (correspondência exata).
--usernametextFiltrar por nome de usuário (contém correspondência).
--emailtextFiltra por endereço de email (contém correspondência).
-l--limitNúmero50Tamanho da página
--offsetNúmero0Ignorar contagem.
--sort-byCampoClassificação OData (por exemplo, UserName asc).
--all-fieldsBandeiradesativadaRetorna a carga útil da API completa em vez do resumo selecionado.

Exemplos

uip or users list --limit 10
uip or users list --username admin
uip or users list --output-filter 'Data[].{key:Key, name:UserName}'
uip or users list --limit 10
uip or users list --username admin
uip or users list --output-filter 'Data[].{key:Key, name:UserName}'

Formato dos dados (--output json)

{
  "Code": "UserList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000001",
      "UserName": "admin@example.com",
      "FullName": "Admin User",
      "Email": "admin@example.com",
      "Type": "User",
      "IsActive": true
    }
  ],
  "Pagination": { "Returned": 1, "Limit": 50, "Offset": 0 }
}
{
  "Code": "UserList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000001",
      "UserName": "admin@example.com",
      "FullName": "Admin User",
      "Email": "admin@example.com",
      "Type": "User",
      "IsActive": true
    }
  ],
  "Pagination": { "Returned": 1, "Limit": 50, "Offset": 0 }
}

uip ou list-in-folder de usuários

Lista os usuários atribuídos a uma pasta, com suas funções no nível da pasta. Requer --folder-path ou --folder-key.

Opções

ShortLongValorPadrãoDescription
--folder-pathPathPasta de destino. Forneça esta ou --folder-key.
--folder-keyGUIDPasta de destino. Forneça esta ou --folder-path.
--include-inheritedBandeiradesativadaMostre também usuários herdados de pastas pai.
-l--limitNúmero50Tamanho da página
--offsetNúmero0Ignorar contagem.
--sort-byCampoId descClassificação OData.
--all-fieldsBandeiradesativadaRetorna a carga útil da API completa em vez do resumo selecionado.

Exemplos

uip or users list-in-folder --folder-path "Shared"
uip or users list-in-folder --folder-path "Shared" --include-inherited
uip or users list-in-folder --folder-path "Shared" \
    --output-filter 'Data[].{name:UserName, roles:Roles}'
uip or users list-in-folder --folder-path "Shared"
uip or users list-in-folder --folder-path "Shared" --include-inherited
uip or users list-in-folder --folder-path "Shared" \
    --output-filter 'Data[].{name:UserName, roles:Roles}'

Formato dos dados (--output json)

{
  "Code": "UserList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000001",
      "UserName": "admin@example.com",
      "FullName": "Admin User",
      "Type": "User",
      "IsInherited": false,
      "Roles": "Folder Administrator"
    }
  ]
}
{
  "Code": "UserList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000001",
      "UserName": "admin@example.com",
      "FullName": "Admin User",
      "Type": "User",
      "IsInherited": false,
      "Roles": "Folder Administrator"
    }
  ]
}

uip ou lista de usuários disponíveis

Liste os usuários do tenant que ainda podem ser atribuídos a uma pasta. Use as chaves retornadas com users assign ou roles assign.

Opções

ShortLongValorPadrãoDescription
--folder-pathPathPasta de destino. Forneça esta ou --folder-key.
--folder-keyGUIDPasta de destino. Forneça esta ou --folder-path.
-s--searchtextFiltrar por nome de usuário (contém correspondência).
-l--limitNúmero50Tamanho da página
--offsetNúmero0Ignorar contagem.

Exemplos

uip or users list-available --folder-path "Shared"
uip or users list-available --folder-path "Shared" --search admin
uip or users list-available --folder-path "Shared" \
    --output-filter 'Data[].Key'
uip or users list-available --folder-path "Shared"
uip or users list-available --folder-path "Shared" --search admin
uip or users list-available --folder-path "Shared" \
    --output-filter 'Data[].Key'

Formato dos dados (--output json)

{
  "Code": "UserAvailableList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000003",
      "UserName": "newuser@example.com",
      "Roles": ""
    }
  ]
}
{
  "Code": "UserAvailableList",
  "Data": [
    {
      "Key": "d4e5f6a7-0000-0000-0000-000000000003",
      "UserName": "newuser@example.com",
      "Roles": ""
    }
  ]
}

o uip ou os usuários recebem

Buscar um usuário por chave GUID.

Argumentos

NameRequiredFinalidade
<user-key>simChave de usuário (GUID).

Opções

ShortLongValorPadrãoDescription
--all-fieldsBandeiradesativadaRetorna a carga útil da API completa em vez do resumo selecionado.

Exemplos

uip or users get d4e5f6a7-0000-0000-0000-000000000001
uip or users get d4e5f6a7-0000-0000-0000-000000000001 --all-fields
uip or users get d4e5f6a7-0000-0000-0000-000000000001 --output-filter 'Data.Email'
uip or users get d4e5f6a7-0000-0000-0000-000000000001
uip or users get d4e5f6a7-0000-0000-0000-000000000001 --all-fields
uip or users get d4e5f6a7-0000-0000-0000-000000000001 --output-filter 'Data.Email'

Formato dos dados (--output json)

{
  "Code": "User",
  "Data": {
    "Key": "d4e5f6a7-0000-0000-0000-000000000001",
    "UserName": "admin@example.com",
    "FullName": "Admin User",
    "Email": "admin@example.com",
    "Type": "User",
    "IsActive": true
  }
}
{
  "Code": "User",
  "Data": {
    "Key": "d4e5f6a7-0000-0000-0000-000000000001",
    "UserName": "admin@example.com",
    "FullName": "Admin User",
    "Email": "admin@example.com",
    "Type": "User",
    "IsActive": true
  }
}

uip or users import

Import a directory principal — an Identity Service user, group, robot account, or external application — into this tenant. This is the only way this CLI provisions a new tenant user; there is no standalone "create a user" verb, because Orchestrator users are always backed by an IS principal.

References an existing IS principal by --username or --directory-id, plus --type to declare which kind of principal it is (the CLI does not guess). Optionally assigns folder roles in the same call with --folder-path/--folder-key and --role-keys — both a folder and roles must be provided together, or neither. --directory-id imports are idempotent: importing an already-imported principal by directory ID returns the existing tenant record instead of failing.

Robot accounts and external applications must be imported with --directory-id (the IS UUID) — Orchestrator can't resolve them by <domain>\<name> the way it resolves a directory user. Find the ID with uip admin robot-accounts list --search <name> or uip admin external-apps list.

Arguments and required identifiers

NameRequiredFinalidade
--usernameone of --username/--directory-idIdentity Service username (typically an email).
--directory-idone of --username/--directory-idIdentity Service directory identifier (OIDC subject / IS UUID). Required for DirectoryRobot and DirectoryExternalApplication types.

Opções

ShortLongValorPadrãoDescription
--typeDirectoryUser | DirectoryGroup | DirectoryRobot | DirectoryExternalApplicationnecessárioDirectory principal type.
--domaintextDirectory domain name as configured in Identity Service. Only needed for on-premises environments with configured AD domains.
--folder-pathPathFolder to assign the imported principal to. Use with --role-keys.
--folder-keyGUIDFolder alternative to --folder-path. Use with --role-keys.
--role-keysCSV de GUIDsFolder role GUIDs to grant. Requires a folder option; a folder option without --role-keys is also rejected.

Exemplos

uip or users import --username alice@example.com

uip or users import --username alice@example.com \
    --folder-path Shared --role-keys a1b2c3d4-0000-0000-0000-000000000001

# Robot account — directory ID required
uip or users import --directory-id 11111111-2222-3333-4444-555555555555 \
    --type DirectoryRobot
uip or users import --username alice@example.com

uip or users import --username alice@example.com \
    --folder-path Shared --role-keys a1b2c3d4-0000-0000-0000-000000000001

# Robot account — directory ID required
uip or users import --directory-id 11111111-2222-3333-4444-555555555555 \
    --type DirectoryRobot

Formato dos dados (--output json)

{
  "Code": "UserImported",
  "Data": {
    "UserName": "alice@example.com",
    "Type": "DirectoryUser",
    "AssignedFolderPath": "Shared",
    "AssignedRoleKeys": ["a1b2c3d4-0000-0000-0000-000000000001"]
  }
}
{
  "Code": "UserImported",
  "Data": {
    "UserName": "alice@example.com",
    "Type": "DirectoryUser",
    "AssignedFolderPath": "Shared",
    "AssignedRoleKeys": ["a1b2c3d4-0000-0000-0000-000000000001"]
  }
}

AlreadyImported: true is added when --directory-id matched a principal already present in the tenant.

uip ou os usuários atribuem

Atribua um usuário a uma pasta, opcionalmente com funções no nível da pasta.

Observação:

CAUTION — destructive on roles. If --role-keys is passed, the server replaces all of the user's existing roles in the target folder with the ones supplied — roles not in the payload are removed silently. To preserve existing roles, read them first with roles user-roles list <principal-name> --type <type> and pass the full desired union to --role-keys. For additive tenant-level role membership on a role, use roles users set instead.

Opções

ShortLongValorPadrãoDescription
--user-keyGUIDnecessárioChave do usuário.
--role-keysCSV de GUIDsGUIDs de função com escopo de pasta.
--folder-pathPathPasta de destino. Forneça esta ou --folder-key.
--folder-keyGUIDPasta de destino.

Exemplos

uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared"

uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" \
    --role-keys a1b2c3d4-0000-0000-0000-000000000002

uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" --output-filter 'Data.Status'
uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared"

uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" \
    --role-keys a1b2c3d4-0000-0000-0000-000000000002

uip or users assign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" --output-filter 'Data.Status'

Formato dos dados (--output json)

{
  "Code": "UserAssigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "FolderPath": "Shared",
    "Status": "Assigned successfully"
  }
}
{
  "Code": "UserAssigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "FolderPath": "Shared",
    "Status": "Assigned successfully"
  }
}

uip ou usuários cancelar atribuição

Remove a user from a folder. The user is not deleted — only their folder assignment is removed.

Opções

ShortLongValorPadrãoDescription
--user-keyGUIDnecessárioChave do usuário.
--folder-pathPathPasta da qual remover. Forneça esta ou --folder-key.
--folder-keyGUIDPasta da qual remover.

Exemplos

uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared"

uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-key b1c2d3e4-0000-0000-0000-000000000001

uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" --output-filter 'Data.Status'
uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared"

uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-key b1c2d3e4-0000-0000-0000-000000000001

uip or users unassign --user-key d4e5f6a7-0000-0000-0000-000000000001 \
    --folder-path "Shared" --output-filter 'Data.Status'

Formato dos dados (--output json)

{
  "Code": "UserUnassigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "FolderPath": "Shared",
    "Status": "Unassigned successfully"
  }
}
{
  "Code": "UserUnassigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "FolderPath": "Shared",
    "Status": "Unassigned successfully"
  }
}

uip or users update

Update a user's tenant-side properties by key (GUID). Reads current values, merges the supplied fields, and saves. Provide at least one option.

edit is a registered alias for this verb — uip or users edit works identically to uip or users update.

Reliably editable: license profile, session flags, and unattended robot credentials. Identity attributes (--name, --surname, --email, --type) are accepted by the API, but for directory principals (DirectoryUser/Group/Robot/ExternalApplication) those fields are normally synced from Identity Service — changing them here only edits the Orchestrator-side cached copy and may be overwritten on the next IS sync. For a durable identity change, edit the IS principal directly.

This command does not expose role assignments — use users assign (folder roles) or users assign-roles (tenant roles) for that; the current tenant role list is always re-sent unchanged so an update never touches it.

Argumentos

NameRequiredFinalidade
<user-key>simChave de usuário (GUID).

Opções

Identity (Orchestrator-side cache only for directory principals)
LongValorDescription
--nametextNew first name.
--surnametextNew last name.
--emailtextNew email address.
--typetextNew user type (for example User, DirectoryUser).
License and session permissions
LongValorDescription
--license-typetextFor example Attended, Unattended, StudioPro.
--allow-unattended / --deny-unattendedBandeiraPermitir ou negar a execução de trabalhos unattended.
--allow-attended / --deny-attendedBandeiraPermitir ou negar sessões assistidas.
--allow-login / --deny-loginBandeiraPermita ou recuse o logon do Orchestrator.
--allow-personal-workspace / --deny-personal-workspaceBandeiraPermitir ou negar o espaço de trabalho pessoal.
--active / --inactiveBandeiraAtive ou desative o usuário.
Credenciais de execução não assistida
LongValorDescription
--unattended-usernametextWindows account for unattended execution (for example DOMAIN\user).
--unattended-passwordtextPassword, or — for a read-only credential store — the external secret reference name.
--credential-store-keyGUIDCredential store for unattended execution credentials. Use credential-stores list to find it.
--credential-typeDefault | SmartCardCredential type.
--limit-concurrent / --no-limit-concurrentBandeiraPermita ou desabilita a execução simultânea em várias máquinas.

If you set any unattended-credential flag on a user with no existing UnattendedRobot record, both --unattended-username and --unattended-password are required together — Orchestrator silently discards an incomplete record, so the CLI refuses to submit one rather than report a false success. Editing an existing record accepts any subset of these flags.

Exemplos

uip or users update d4e5f6a7-0000-0000-0000-000000000001 --email newmail@example.com

uip or users update d4e5f6a7-0000-0000-0000-000000000001 \
    --allow-unattended --license-type Unattended \
    --unattended-username DOMAIN\\bot --unattended-password s3cret

uip or users update d4e5f6a7-0000-0000-0000-000000000001 --inactive \
    --output-filter 'Data.Status'
uip or users update d4e5f6a7-0000-0000-0000-000000000001 --email newmail@example.com

uip or users update d4e5f6a7-0000-0000-0000-000000000001 \
    --allow-unattended --license-type Unattended \
    --unattended-username DOMAIN\\bot --unattended-password s3cret

uip or users update d4e5f6a7-0000-0000-0000-000000000001 --inactive \
    --output-filter 'Data.Status'

Formato dos dados (--output json)

{
  "Code": "UserUpdated",
  "Data": { "Key": "d4e5f6a7-0000-0000-0000-000000000001", "Status": "Updated successfully" }
}
{
  "Code": "UserUpdated",
  "Data": { "Key": "d4e5f6a7-0000-0000-0000-000000000001", "Status": "Updated successfully" }
}

uip ou usuários atuais

Retorne o usuário atualmente autenticado. Útil para verificar a sessão e descobrir sua própria chave de usuário.

Opções

ShortLongValorPadrãoDescription

Exemplos

uip or users current
uip or users current --output-filter 'Data.Key'
uip or users current --output table
uip or users current
uip or users current --output-filter 'Data.Key'
uip or users current --output table

Formato dos dados (--output json)

Mesma forma User que users get.

uip ou usuários atribuir-funções

Assign tenant-level roles to a user.

Observação:

CAUTION — destructive. The server replaces the user's entire tenant-level role list with the keys passed via --role-keys — roles not in the payload are removed silently. To preserve existing tenant roles, read them first with roles user-roles list <principal-name> --type <type> and pass the full desired union to --role-keys. Unlike users assign (folder-level roles), this sets roles that apply across the entire tenant.

Argumentos

NameRequiredFinalidade
<user-key>simChave de usuário (GUID).

Opções

ShortLongValorPadrãoDescription
--role-keysCSV de GUIDsnecessárioGUIDs de função a serem atribuídos no escopo do tenant.

Exemplos

uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001

uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001,a1b2c3d4-0000-0000-0000-000000000002

uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001 \
    --output-filter 'Data.RolesAssigned'
uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001

uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001,a1b2c3d4-0000-0000-0000-000000000002

uip or users assign-roles d4e5f6a7-0000-0000-0000-000000000001 \
    --role-keys a1b2c3d4-0000-0000-0000-000000000001 \
    --output-filter 'Data.RolesAssigned'

Formato dos dados (--output json)

{
  "Code": "UserRolesAssigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "RolesAssigned": 1,
    "Status": "Assigned successfully"
  }
}
{
  "Code": "UserRolesAssigned",
  "Data": {
    "UserKey": "d4e5f6a7-0000-0000-0000-000000000001",
    "RolesAssigned": 1,
    "Status": "Assigned successfully"
  }
}

Códigos de saída

Consulte Códigos de saída. Nenhuma substituição específica do verbo.

  • uip or roles — manage roles, role-user membership, and principal permission inspection (roles user-roles list, roles user-permissions list).
  • uip or folders — localize chaves de pasta para users assign / unassign.
  • uip or jobs — especialmente jobs start --user-keys.

Veja também

Esta página foi útil?

Conectar

Precisa de ajuda? Suporte

Quer aprender? Academia UiPath

Tem perguntas? Fórum do UiPath

Fique por dentro das novidades