Users
Overview
Individuals who have access to Skedulo.
System fields
System fields are read-only fields found on most objects. These fields are automatically updated during API operations. To learn more see System Fields.
Standard fields
| Field Name | Details | Required |
|---|---|---|
| City | Type Text Description The city of the User’s address. Must be between 0 and 40 characters |
No |
| Country | Type Text Description The country of the User’s address. Must be between 0 and 80 characters |
No |
| Type Text Description The User’s email address. Must be between 0 and null characters |
Yes | |
| FirstName | Type Text Description The User’s first name. Must be between 0 and 40 characters |
No |
| IsActive | Type Checkbox Description Indicates whether the user has access to log in (true) or not (false). |
Yes |
| LastName | Type Text Description The User’s last name. Must be between 0 and 80 characters |
Yes |
| MobilePhone | Type Text Description The User’s mobile phone number. Must be between 0 and 40 characters |
No |
| Name | Type Text Description Concatenation of ‘FirstName’ and ‘LastName’. Must be between 0 and null characters |
Yes |
| PostalCode | Type Text Description The ZIP or postal code of the User’s address. Must be between 0 and 20 characters |
No |
| State | Type Text Description The state of the User’s address. Must be between 0 and 80 characters |
No |
| Street | Type Text Description The street of the User’s address. Must be between 0 and 255 characters |
No |
| UserTypes | Type Picklist Description The type of User. Valid values are: - Scheduler - Resource - Administrator Custom valuesAdditional UserRoles may be created via the Skedulo web app. |
No |
Related objects
This object has the following related objects.
| Name | Details |
|---|---|
| Resources | Object Has many (Resources) Description Resources associated with the User. |
| UserRegions | Object Has many (UserRegions) Description User Regions associated with the User. |
Deprecated fields
This section lists fields that are marked as deprecated and are maintained for backwards compatibility purposes only. It’s recommended not to use them in new implementations, as they may be removed in future releases.
- FullPhotoUrl
- SmallPhotoUrl
Feedback
Was this page helpful?