...
This controller allows for creating org chart teams entries and assigning their hierarchy. Changes are only allowed if the authenticated user is an administrator or is a member of an ancestor (parent, parent of parent, etc) team of the team being updated. If the parent is being changed then the authenticated user needs to belong to the new parent team (or an ancestor) as well. Otherwise 400 is returned.
GET /odata/OrganizationTeamHierarchies(id)
...
Create a new Organization Team entity in the system. Request body is expected to be an Organization Team object in JSON format.
Returns:
200: success, response body is the resulting Organization Team (with Id populated).
400: invalid request: format error or , CompanyId of team doesn't match id of authenticated user making the request or authenticated user doesn't have access to create
PATCH /odata/OrganizationTeamHierarchies(id)
...
Remove the team from the system. Authenticated user must be an administrator or a member of a team that's an ancestor of the team being updated.
Returns:
204: success
400: invalid request: CompanyId of team doesn't match id of authenticated user making the request
...
GET /odata/OrganizationTeamMemberHierarchies(id)
Retrieve the Team Membershipthe OrganizationTeamMemberHierarchy object with the given id.
Returns:
200: success, response body is an Organization Team an OrganizationTeamMemberHierarchy in JSON format
404: entry not found for that id
...
200: success, response body is an OData list of all matching Organization Team Membership matching OrganizationTeamMemberHierarchy objects in JSON format
POST /odata/OrganizationTeamMemberHierarchies
Create a new Organization Team entity membership entry in the system. Request body is expected to be an Organization Team an OrganizationTeamMemberHierarchy object in JSON format.
Returns:
...
This controller provides read/write access to User (=> employee/personnel) records. Changes are only allowed if the authenticated user is an administrator or member of a team that is an ancestor of one of the teams the user belongs to. Only administrators can change the SecurityLevel property; a change to this by a non-administrator will fail with a 400 return code.
GET /odata/Users(id)
Retrieve the User object for the given id if accessible to the authenticated user.
Returns:
200 on success, User object as JSON payload
400 authenticated account doesn't have access to that user's information
404 on user not found
GET /odata/Users
Get all accessible user objects. Administrators can see all users but otherwise . Otherwise only users in teams managed by teams that are descendants of the teams for the authenticated user will be visible (as well as the authenticated user's account).
OData query parameters can be used to filter results.
Returns:
200 on success, OData query result as JSON payload
...
Create a new user object. Body of request is a a User object in JSON format. SecurityLevel must be User unless the authenticated user is an administrator, otherwise 400 Invalid request will be returned
Returns:
200 on success, body of response is the newly created User object (with populated Id field)
400 on invalid request: duplicate username or invalid fields or attempt by non-admin to create a non-user account
PATCH /odata/Users(id)
PUT /odata/Users(id)
Update the existing user object with the given id. Body of request is a User object with the updated fields. Id must be populated.
Returns:
204 on success
400 on invalid request: invalid fields or , Id in body doesn't match the one provided in the URL or authenticated user doesn't have access to this user entry
404 no such user
DELETE /odata/Users(id)
Removes the user object with the given id. Only accessible to administrator users.404 on Usually best practice is to set a user's IsActive to false instead of deleting so that all records that link back to the user in the database will have a valid reference (as opposed to "missing user")
Returns:
200 success
400 invalid request: not an administrator
404 no such user