# Update organization

Canonical page: https://docs.ovok.com/api/slim/organization/update-organization

`PUT /v1/slim/organization/{id}`

Updates an organization's (zone's) name, description and parent zone.

**Auth:** Bearer token. The caller must be a practitioner, an admin, a super admin, or hold the "System Owner" access policy. The access policy must grant `Organization:update` (an admin or super admin who holds no access policy skips this check).
**Scope:** The organization must belong to the caller's project (from the token). Organizations in a parent project or a sub-project are refused.

## Behaviour

- `name` is required and must be unique among the organizations your token can search, not counting this one.
- `parentOrganizationId` sets the parent zone. It must name an organization in your own project. **Omitting it removes the current parent**, which makes the zone top-level.
- `description`, when non-empty, replaces the narrative text. Omitting it, or sending `null` or an empty string, leaves the existing description unchanged.
- The write is atomic and takes a short write lock. A concurrent write to the same resources gets a 409.
- A zone-updated entry is added to the change history. A failure to write that entry does not fail the request.
- The response is the organization after the update, in the same shape as `GET /v1/slim/organization/{id}`.

## Example

```bash
curl -X PUT 'https://api.sandbox.ovok.com/v1/slim/organization/c3499c27-2973-0a7f-807e-fb8676a92dcb' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk' \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Ward A",
    "parentOrganizationId": "87ea5dfc-8b8e-384d-8489-79496e706390",
    "description": "Ground floor"
  }'
```