Class CreateUserResource

Indicates whether the user is active or deactivated in the organization.

A human-readable name for the user, typically the full name. This attribute is used if the value is not empty.

Maximum length: 60 characters

An array of display picture for the user in the organization. Contains photo value and type.

Notes: Must be a text URL to the image. Supported file types: jpg, jpeg, bmp, png, gif.

To define file type, you should have defined file extension in url (e.g. https://host.com/avatar_user1.jpg) or request to url should return together with a file content a header Content-Type (e.g. Content-Type = image/jpeg)

Maximum file size to download is: 31457280 bytes.

Example (Okta): photos.^[type==photo].value
Example (Azure): photos[type eq "photo"].value

Specifies the user's preferred language.

Example: en_US for English.

An array of roles assigned to the user in the organization. Contains role value, display, type, and primary flag.

organization_user_role supported values include: ORGANIZATION_INTERNAL_ADMIN and ORGANIZATION_INTERNAL_USER. organization_admin_role supported values include: Content Admin, User Admin, Security Admin, or names of custom admin roles.

Example (Okta) for organization_user_role: roles.^[primary==true].value
Example (Azure) for organization_user_role: roles[primary eq "True"].value
Example (Okta) for organization_admin_role: roles.^[primary==false].value
Example (Azure) for organization_admin_role: roles[primary eq "False"].value

Identifies which schema(s) this resource uses. In this case it is the SCIM core User schema.

The unique username/login identifier. An email address in this case.

Note: Payload must include the userName attribute populated with an email address

User is created with this email address in the organization. This attribute will be used as full name of the created user if the displayName or name attribute is not provided.

Free-form string to indicate the user license type in the organization.

Only supported values for licenses are allowed. Supported licences for organizations can vary. They can potentially have the following values: Full, Free, Free Restricted, Full (Trial), Basic.

Note: When userType is specified, the userType license is set per the value provided. When userType is not specified, the user license is set according to internal Miro logic, which depends on the organization plan.