---
title: "Deprecated. This method will be removed in future versions of TSB. Use Service Accounts instead."
method: POST
path: "/v2/organizations/{organization}/users"
tags: ["Teams"]
---

# Deprecated. This method will be removed in future versions of TSB. Use Service Accounts instead.

`POST /v2/organizations/{organization}/users`

## Request

- Base URL: `https://docs.tetrate.io` (the document declares no server; this is the origin it was published from)
- URL: `https://docs.tetrate.io/v2/organizations/{organization}/users`
- Auth: none declared
- TypeScript: <https://skmtc.dev/tetrate/apis/tetrate-service-bridge-api/docs/v2/organizations/:organization/users/post.ts> (a function with typed inputs; its response is checked against the schema)

Create a local User in TSB.
Local users are like sercice accounts and are mostly used for internal purposes where
an authentication token can be issued by the IAM service to be used on behalf of the user.

Note that local users do not exist in the Identity Provider and the normal login process will
not allow them to access TSB.

$hide_from_docs

## Path parameters

- `organization` string, required

## Request body

- object
  - `name` string, required: The short name for the resource to be created.
  - `user` V2User, required: `User` represents a user from the Identity Provider that is allowed to log into the platform.
    - `fqn` string
    - `displayName` string
    - `etag` string
    - `loginName` string, required: The username used in the login credentials.
    - `firstName` string: The first name of the user.
    - `lastName` string: The last name of the user, if any.
    - `email` string: Email for the user where alerts and other notifications will be sent.
    - `sourceType` 'INVALID' | 'LDAP' | 'LOCAL' | 'AZURE' | 'MANUAL': `SourceType` describes where teams come from. Teams can be synchronized from the Identity Provider but can also be manually created using the Team API to create convenient groupings of users and other teams in order to configure fine-grained permissions in the Management Plane. - LDAP: LDAP is used for users and teams that are automatically synchronized from LDAP. - LOCAL: LOCAL is used for local teams that are manually created using the TSB Team API and do not exist in the Identity Provider. Deprecated. This value is deprecated and will be removed in future releases. Use 'MANUAL' instead. - AZURE: AZURE is used for users synchronized from an Azure Active Directory. - MANUAL: MANUAL is used for users and teams that exist in the Identity Provider that have been manually populated. MANUAL users are deprecated and Service Accounts should be used instead. Support for MANUAL users will be removed in future versions.

## Response `200`

A successful response.

- V2User: `User` represents a user from the Identity Provider that is allowed to log into the platform.
  - `fqn` string
  - `displayName` string
  - `etag` string
  - `loginName` string, required: The username used in the login credentials.
  - `firstName` string: The first name of the user.
  - `lastName` string: The last name of the user, if any.
  - `email` string: Email for the user where alerts and other notifications will be sent.
  - `sourceType` 'INVALID' | 'LDAP' | 'LOCAL' | 'AZURE' | 'MANUAL': `SourceType` describes where teams come from. Teams can be synchronized from the Identity Provider but can also be manually created using the Team API to create convenient groupings of users and other teams in order to configure fine-grained permissions in the Management Plane. - LDAP: LDAP is used for users and teams that are automatically synchronized from LDAP. - LOCAL: LOCAL is used for local teams that are manually created using the TSB Team API and do not exist in the Identity Provider. Deprecated. This value is deprecated and will be removed in future releases. Use 'MANUAL' instead. - AZURE: AZURE is used for users synchronized from an Azure Active Directory. - MANUAL: MANUAL is used for users and teams that exist in the Identity Provider that have been manually populated. MANUAL users are deprecated and Service Accounts should be used instead. Support for MANUAL users will be removed in future versions.

## Other responses

- `default`: An unexpected error response.

---

[API](https://skmtc.dev/tetrate/apis/tetrate-service-bridge-api.md) - [All operations](https://skmtc.dev/tetrate/apis/tetrate-service-bridge-api/llms.txt) - [OpenAPI document](https://skmtc.dev/tetrate/apis/tetrate-service-bridge-api/revisions/2f19c3a1ae57?raw)