---
title: "Set Managed By"
method: PUT
path: "/api/admin/identities/{identity_id}/managed-by"
tags: ["admin-identities"]
---

# Set Managed By

`PUT /api/admin/identities/{identity_id}/managed-by`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/admin/identities/{identity_id}/managed-by`
- Auth: none declared

Grant or end a folder's authority to act as this identity (TOS-4159).

This is the ONLY way delegated act-as is conferred. Before TOS-4159 the
authority was inferred from folder membership, so it attached silently to
every colleague filed alongside an administrator; naming the folder makes
the grant a decision somebody made rather than a side effect of where a
person was filed.

Platform-admin gated on purpose, matching the outbound-email policy beside
it. Both say what an organization may do TO an identity rather than what
that identity may do, so neither belongs to the folder's own administrators
while TOS-3921's consent-bearing claim flow is still deferred: a folder
admin who could grant themselves authority over a member has the membership
rule back, under a new name.

Passing ``None`` ends the relationship, which is the revocation half
TOS-3921's claim flow needs.

## Path parameters

- `identity_id` string, uuid, required

## Request body

- SetManagedByRequest: Name the folder that operates this identity, or ``None`` to end it.
  - `managed_by_library_id` string, uuid, nullable, required

## Response `200`

Successful Response

- ManagedByOut
  - `identity_id` string, uuid, required
  - `managed_by_library_id` string, uuid, nullable, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/ce2c2ce318b1?raw)