Skip to main content

SetCrossTenantGrantPermissions

Replaces the list of tenants that may look up users of the tenant of the context by exact name or e-mail and grant them access.

Examples​

Permit two tenants:

octo-cli -c SetCrossTenantGrantPermissions -ttids "customer-a,customer-b"

Permit nobody:

octo-cli -c SetCrossTenantGrantPermissions -none

Options​

ShortLongRequiredDescription
-ttids--targetTenantIdsnoComma-separated list of the permitted target tenant IDs (replaces the whole list)
-none--nonenoWithdraw every permission (empty list)

Notes​

Pass exactly one of --targetTenantIds or --none. The list replaces the stored one; entries are trimmed, lower-cased and de-duplicated by the service.

A removed tenant can no longer look up or grant users at once; its existing grants are refused at their next token exchange.

Invalid entries (format, more than 200, the tenant itself) are refused with HTTP 400 and nothing changes. Entries are not checked for existence.

Only administrators of the tenant itself (UserManagement and TenantManagement, signed in to or switched into that tenant) may change the list; anyone else gets HTTP 403. Every change is written to the tenant's event log.