Syntax and options for `uip or users`, which manages Orchestrator tenant users and their folder and role assignments.
uip or users manages Orchestrator users at the tenant level — listing, creating, editing, and deleting users, plus assigning them to folders and managing tenant-level role assignments. For folder-level role management, see uip or roles .
assignment uip or users < verb> [ options]
uip or users <verb> [options]
Verb Purpose listList tenant users with optional filters. list-in-folderList users assigned to a folder, with their folder-level roles. list-availableList users that can still be assigned to a folder (not yet assigned). getFetch one user by key. createCreate a new user; optionally assign tenant roles and set unattended execution credentials. deleteDelete a user by key. assignAssign a user to a folder, optionally with folder-level roles. unassignRemove a user from a folder. editEdit user properties (PATCH semantics). currentReturn details of the currently authenticated user. assign-rolesReplace a user's tenant-level role assignments.
List users in the tenant. Returns user key (GUID), username, full name, email, type, and active status.
Options
Short Long Value Default Description — --keyGUID — Filter by user key (exact match). — --usernametext — Filter by username (contains match). — --emailtext — Filter by email address (contains match). -l--limitnumber 50Page size. — --offsetnumber 0Skip count. — --order-byfield — OData sort (for example, UserName asc). — --all-fieldsflag off Return the full API payload.
Examples
assignment 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}'
Data shape (--output json)
assignment {
"Code" : "UserList" ,
"Data" : [
{
"Key" : "d4e5f6a7-0000-0000-0000-000000000001" ,
"UserName" : "[email protected] " ,
"FullName" : "Admin User" ,
"Email" : "[email protected] " ,
"Type" : "User" ,
"IsActive" : true
}
] ,
"Pagination" : { "Returned" : 1 , "Limit" : 50 , "Offset" : 0 , "HasMore" : false }
}
{
"Code": "UserList",
"Data": [
{
"Key": "d4e5f6a7-0000-0000-0000-000000000001",
"UserName": "[email protected] ",
"FullName": "Admin User",
"Email": "[email protected] ",
"Type": "User",
"IsActive": true
}
],
"Pagination": { "Returned": 1, "Limit": 50, "Offset": 0, "HasMore": false }
}
uip or users list-in-folder link
List users assigned to a folder, with their folder-level roles. Requires --folder-path or --folder-key.
Options
Short Long Value Default Description -t--tenantname session default Override the tenant. — --folder-pathpath — Target folder. Provide this or --folder-key. — --folder-keyGUID — Target folder. Provide this or --folder-path. — --include-inheritedflag off Also show users inherited from parent folders. -l--limitnumber 50Page size. — --offsetnumber 0Skip count. — --order-byfield Id descOData sort.
Examples
assignment 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}'
Data shape (--output json)
assignment {
"Code" : "UserList" ,
"Data" : [
{
"Key" : "d4e5f6a7-0000-0000-0000-000000000001" ,
"UserName" : "[email protected] " ,
"FullName" : "Admin User" ,
"Type" : "User" ,
"IsInherited" : false ,
"Roles" : "Folder Administrator"
}
]
}
{
"Code": "UserList",
"Data": [
{
"Key": "d4e5f6a7-0000-0000-0000-000000000001",
"UserName": "[email protected] ",
"FullName": "Admin User",
"Type": "User",
"IsInherited": false,
"Roles": "Folder Administrator"
}
]
}
uip or users list-available link
List tenant users that can still be assigned to a folder. Use the returned keys with users assign or roles assign.
Options
Short Long Value Default Description -t--tenantname session default Override the tenant. — --folder-pathpath — Target folder. Provide this or --folder-key. — --folder-keyGUID — Target folder. Provide this or --folder-path. -s--searchtext — Filter by username (contains match). -l--limitnumber 50Page size. — --offsetnumber 0Skip count.
Examples
assignment 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'
Data shape (--output json)
assignment {
"Code" : "UserAvailableList" ,
"Data" : [
{
"Key" : "d4e5f6a7-0000-0000-0000-000000000003" ,
"UserName" : "[email protected] " ,
"Roles" : ""
}
]
}
{
"Code": "UserAvailableList",
"Data": [
{
"Key": "d4e5f6a7-0000-0000-0000-000000000003",
"UserName": "[email protected] ",
"Roles": ""
}
]
}
Fetch a user by GUID key.
Arguments
Name Required Purpose <user-key>yes User key (GUID).
Options
Short Long Value Default Description -t--tenantname session default Override the tenant. — --all-fieldsflag off Return the full API payload.
Examples
assignment 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'
Data shape (--output json)
assignment {
"Code" : "User" ,
"Data" : {
"Key" : "d4e5f6a7-0000-0000-0000-000000000001" ,
"UserName" : "[email protected] " ,
"FullName" : "Admin User" ,
"Email" : "[email protected] " ,
"Type" : "User" ,
"IsActive" : true
}
}
{
"Code": "User",
"Data": {
"Key": "d4e5f6a7-0000-0000-0000-000000000001",
"UserName": "[email protected] ",
"FullName": "Admin User",
"Email": "[email protected] ",
"Type": "User",
"IsActive": true
}
}
Create a new tenant user. Only --username is required. The API requires rolesList, so --role-keys is effectively required in practice — use it with tenant-scope role GUIDs.
Options
Identity
Short Long Value Default Description — --usernametext required Login username. — --nametext — First name. — --surnametext — Last name. — --emailtext — Email address. — --typeenum — User type (for example, User, DirectoryUser). -t--tenantname session default Override the tenant.
Roles and license
Short Long Value Default Description — --role-keysCSV of GUIDs — Tenant-scope role GUIDs (resolved to role names for the API payload). — --license-typeenum — For example, Attended, Unattended, StudioPro.
Session permissions (flag pairs)
Short Long Value Default Description — --allow-unattended / --deny-unattendedflag — Allow or deny unattended job execution. — --allow-attended / --deny-attendedflag — Allow or deny attended sessions. — --allow-login / --deny-loginflag — Allow or deny Orchestrator login. — --allow-personal-workspace / --deny-personal-workspaceflag — Allow or deny personal workspace. — --active / --inactiveflag — Activate or deactivate the user.
Unattended execution credentials
Short Long Value Default Description — --unattended-usernametext — Windows account (for example, DOMAIN\user). — --unattended-passwordtext — Password, or — for read-only credential stores — the external secret reference name. — --credential-store-keyGUID — Credential store. Use credential-stores list to find it. — --credential-typeenum — Default or SmartCard.— --limit-concurrent / --no-limit-concurrentflag — Allow or disallow concurrent execution on multiple machines.
Examples
assignment uip or users create -- username newuser@example. com -- email newuser@example. com \
-- role- keys a1b2c3d4- 0000 - 0000 - 0000 - 000000000001
uip or users create -- username bot@example. com -- name Bot -- surname Worker \
-- role- keys a1b2c3d4- 0000 - 0000 - 0000 - 000000000002 \
-- unattended- username DOMAIN \\bot -- unattended- password s3cret
uip or users create -- username newuser@example. com \
-- role- keys a1b2c3d4- 0000 - 0000 - 0000 - 000000000001 \
-- output- filter 'Data.Key'
uip or users create --username [email protected] --email [email protected] \
--role-keys a1b2c3d4-0000-0000-0000-000000000001
uip or users create --username [email protected] --name Bot --surname Worker \
--role-keys a1b2c3d4-0000-0000-0000-000000000002 \
--unattended-username DOMAIN\\bot --unattended-password s3cret
uip or users create --username [email protected] \
--role-keys a1b2c3d4-0000-0000-0000-000000000001 \
--output-filter 'Data.Key'
Data shape (--output json)
assignment {
"Code" : "User" ,
"Data" : {
"Key" : "d4e5f6a7-0000-0000-0000-000000000010" ,
"UserName" : "[email protected] " ,
"FullName" : "" ,
"Email" : "[email protected] " ,
"Type" : "User" ,
"IsActive" : true
}
}
{
"Code": "User",
"Data": {
"Key": "d4e5f6a7-0000-0000-0000-000000000010",
"UserName": "[email protected] ",
"FullName": "",
"Email": "[email protected] ",
"Type": "User",
"IsActive": true
}
}
Permanently delete a user from the tenant.
Arguments
Name Required Purpose <user-key>yes User key (GUID).
Options
Short Long Value Default Description -t--tenantname session default Override the tenant.
Examples
assignment uip or users delete d4e5f6a7- 0000 - 0000 - 0000 - 000000000010
uip or users delete d4e5f6a7- 0000 - 0000 - 0000 - 000000000010 -- output- filter 'Data.Status'
uip or users delete d4e5f6a7- 0000 - 0000 - 0000 - 000000000010 -- output plain
uip or users delete d4e5f6a7-0000-0000-0000-000000000010
uip or users delete d4e5f6a7-0000-0000-0000-000000000010 --output-filter 'Data.Status'
uip or users delete d4e5f6a7-0000-0000-0000-000000000010 --output plain
Data shape (--output json)
assignment {
"Code" : "UserDeleted" ,
"Data" : { "Key" : "d4e5f6a7-0000-0000-0000-000000000010" , "Status" : "Deleted successfully" }
}
{
"Code": "UserDeleted",
"Data": { "Key": "d4e5f6a7-0000-0000-0000-000000000010", "Status": "Deleted successfully" }
}
Assign a user to a folder, optionally with folder-level roles.
Options
Short Long Value Default Description — --user-keyGUID required User key. — --role-keysCSV of GUIDs — Folder-scope role GUIDs. — --folder-pathpath — Target folder. Provide this or --folder-key. — --folder-keyGUID — Target folder. -t--tenantname session default Override the tenant.
Examples
assignment 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'
Data shape (--output json)
assignment {
"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 or users unassign link
Remove a user from a folder. The user is not deleted.
Options
Short Long Value Default Description — --user-keyGUID required User key. — --folder-pathpath — Folder to remove from. Provide this or --folder-key. — --folder-keyGUID — Folder to remove from. -t--tenantname session default Override the tenant.
Examples
assignment 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'
Data shape (--output json)
assignment {
"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"
}
}
Edit a user by key. Reads current values, merges the provided fields, and saves. Provide at least one option to update.
Arguments
Name Required Purpose <user-key>yes User key (GUID).
Options
Same flags as users create, except --username (cannot be changed) and --role-keys (use users assign-roles instead). All session-permission flag pairs, license type, and unattended credential options apply.
Examples
assignment uip or users edit d4e5f6a7- 0000 - 0000 - 0000 - 000000000001 -- email newmail@example. com
uip or users edit d4e5f6a7- 0000 - 0000 - 0000 - 000000000001 \
-- allow- unattended -- license- type Unattended
uip or users edit d4e5f6a7- 0000 - 0000 - 0000 - 000000000001 -- inactive \
-- output- filter 'Data.Status'
uip or users edit d4e5f6a7-0000-0000-0000-000000000001 --email [email protected]
uip or users edit d4e5f6a7-0000-0000-0000-000000000001 \
--allow-unattended --license-type Unattended
uip or users edit d4e5f6a7-0000-0000-0000-000000000001 --inactive \
--output-filter 'Data.Status'
Data shape (--output json)
assignment {
"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 or users current link
Return the currently authenticated user. Useful for verifying the session and discovering your own user key.
Options
Short Long Value Default Description -t--tenantname session default Override the tenant.
Examples
assignment 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
Data shape (--output json)
Same User shape as users get.
uip or users assign-roles link
Assign tenant-level roles to a user. This replaces the user's current tenant roles — use roles set-role-users for additive membership at a role level.
Arguments
Name Required Purpose <user-key>yes User key (GUID).
Options
Short Long Value Default Description — --role-keysCSV of GUIDs required Role GUIDs to assign at tenant scope. -t--tenantname session default Override the tenant.
Examples
assignment 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'
Data shape (--output json)
assignment {
"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"
}
}