---
title: "Assign a profile to a user"
method: POST
path: "/users/{userId}/profiles/{profileId}"
tags: ["users"]
---

# Assign a profile to a user

`POST /users/{userId}/profiles/{profileId}`

Replaces the user's current profile with the one matching the given `profileId`. A profile defines the user's telephony features, call routing rules, and access level within the Ringover platform. Changing a user's profile immediately affects their available features and call handling behavior.

**Permission:** No specific permission required. A valid API key is sufficient.

**Monitoring:** Not needed.

> **Warning — Sensitive operation:** This route does not enforce any specific permission category. Any valid API key can change any user's profile. Reassigning a profile may alter a user's telephony capabilities and routing rules. Validate the target `profileId` carefully before calling this endpoint.

## Path parameters

- `userId` integer, required
- `profileId` integer, required

## Response `200`

Successful operation

## Other responses

- `400` — One or more path parameters are invalid
- `401` — Authentication token is missing, invalid, or expired
- `404` — No user or profile found with the specified IDs
- `500` — Internal server error
- `502` — Service temporarily unavailable

---

[API](https://skmtc.net/ringover/apis/ringover-public-api.md) · [All operations](https://skmtc.net/ringover/apis/ringover-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringover/ringover-public-api/revisions/9da73dd2f99e/schema)