Example Response

HTTP 204 Content-Type: application/json

Step 2 - Get Locations

Once you have created a user in the system, the next step involves location assignment within your company tree. This ensures that employee visibility and activity is restricted to that particular location. For more information on Company Tree, see Company Tree.

Example Response

HTTP 200 Content-Type: application/json

[{"Id":316,"Name":"Store Manager"}]

Step 5 - Assigning Security Roles

The goal of this step is to ensure that your employee has a security role in RQ that matches their role in your system. If a Security Role is not assigned to a User, then they will not be able to interact with RQ.

The EntityId assigned to this User would be the Company ID, Location ID, or a Group or Division ID.

For our scenario, we are assigning the security role Store Manager at this location.

(Optional) Terminating an Employee

This method does not delete the employee or free up their email address or username to be used to create another User. To free up an email address or username, you must instead update the email or username of the original User to something else.