## Invite

**post** `/v1/viewer/users`

Creates a new user in the Viewer system and sends them an invitation email. The user will have the specified permissions and access level. Dashboard access can be enabled to allow login.

### Body Parameters

- `canManageStudies: boolean`

- `clinicRole: "Radiologist" or "Cardiologist" or "Neurologist" or 18 more`

  User's clinical or organizational role

  - `"Radiologist"`

  - `"Cardiologist"`

  - `"Neurologist"`

  - `"Urologist"`

  - `"Gynecologist"`

  - `"Endocrinologist"`

  - `"Doctor"`

  - `"Surgeon"`

  - `"Physician"`

  - `"Physician Assistant"`

  - `"Nurse Practitioner"`

  - `"Registered Nurse"`

  - `"Patient Care Coordinator"`

  - `"Front Desk Operator"`

  - `"Imaging Technologist"`

  - `"PACS Administrator"`

  - `"Software Engineer"`

  - `"Revenue Cycle Manager"`

  - `"Administrative Director"`

  - `"Administrative Assistant"`

  - `"Other"`

- `email: string`

  User's email address for login and notifications

- `firstName: string`

  User's first name

- `hasDashboardAccess: boolean`

- `lastName: string`

  User's last name

- `level: "admin" or "member"`

  - `"admin"`

  - `"member"`

- `middleName: optional string`

  User's middle name (optional)

- `phoneNumber: optional string`

  User's phone number (10-15 digits, optional)

- `suffix1: optional string`

  Name suffix (e.g., 'Jr.', 'Sr.', 'III') - optional

- `suffix2: optional string`

  Additional name suffix (optional)

### Returns

- `canManageStudies: boolean`

  Whether the user has permission to create, update, and manage studies

- `clinicRole: "Radiologist" or "Cardiologist" or "Neurologist" or 18 more`

  User's clinical or organizational role

  - `"Radiologist"`

  - `"Cardiologist"`

  - `"Neurologist"`

  - `"Urologist"`

  - `"Gynecologist"`

  - `"Endocrinologist"`

  - `"Doctor"`

  - `"Surgeon"`

  - `"Physician"`

  - `"Physician Assistant"`

  - `"Nurse Practitioner"`

  - `"Registered Nurse"`

  - `"Patient Care Coordinator"`

  - `"Front Desk Operator"`

  - `"Imaging Technologist"`

  - `"PACS Administrator"`

  - `"Software Engineer"`

  - `"Revenue Cycle Manager"`

  - `"Administrative Director"`

  - `"Administrative Assistant"`

  - `"Other"`

- `createdAt: string`

  Timestamp when the user was created

- `email: string`

  User's email address for login and notifications

- `firstName: string`

  User's first name

- `hasDashboardAccess: boolean`

  Whether the user can access the dashboard interface. Required for admin users

- `invitedSource: "dashboard" or "api"`

  How the user was invited - via dashboard UI or API

  - `"dashboard"`

  - `"api"`

- `lastLoginAt: string`

  Timestamp of user's last login, null if never logged in

- `lastName: string`

  User's last name

- `level: "admin" or "member"`

  User access level. 'admin' can manage users/settings, 'member' has standard access

  - `"admin"`

  - `"member"`

- `userId: string`

  Unique user identifier. Format: usr_{32-hex-chars}

- `middleName: optional string`

  User's middle name (optional)

- `phoneNumber: optional string`

  User's phone number (10-15 digits, optional)

- `suffix1: optional string`

  Name suffix (e.g., 'Jr.', 'Sr.', 'III') - optional

- `suffix2: optional string`

  Additional name suffix (optional)

### Example

```http
curl https://api.avarasoftware.com/v1/viewer/users \
    -H 'Content-Type: application/json' \
    -H "Authorization: Bearer $AVARA_API_KEY" \
    -d '{
          "canManageStudies": true,
          "clinicRole": "Radiologist",
          "email": "dr.johnson@hospital.org",
          "firstName": "Sarah",
          "hasDashboardAccess": true,
          "lastName": "Johnson",
          "level": "member",
          "middleName": "Marie",
          "phoneNumber": "5551234567",
          "suffix1": "MD",
          "suffix2": "FACR"
        }'
```