Staff accounts
Keep GeotechOS staff accounts in step with the users in your system, so the jobs you send keep their crew. Never with full access.
A job keeps its crew only when each person has an account in your GeotechOS workspace. If your own system has your staff, it can make and update their accounts.
Before you start
An administrator must let the key make accounts, and choose the role they get:
- Click Settings, then API keys.
- Find your integration in the Integrations list.
- In Adds staff accounts as, select the role. For example, a Staff role that can see and edit jobs and dockets.
whoami then shows "adds_staff_accounts": true. Without a role, a request to /users is refused with 403.
Send a staff member
curl -s -X PUT "$GEOTECHOS_URL/users/ext:U-12" \
-H "Authorization: Bearer $GEOTECHOS_API_KEY" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]",
"first_name": "Kim",
"last_name": "Field",
"position": "Field technician",
"phone": "0400 000 001",
"is_active": true
}'
email and first_name are required. Only PUT with your own id works for staff accounts.
What GeotechOS does
- A new account gets the role you selected and never full access. GeotechOS does not send an email. The person signs in with this email address when the office tells them to.
- An account that is already in your workspace with this email is linked to your id (
"adopted": true). GeotechOS keeps its role, its access and its details as the office set them. - An email that has an account in another GeotechOS workspace is refused with
409. One email is one account. Use another email, or ask GeotechOS support. - A person who leaves: send
"is_active": false. The account stops. Its history stays.
Administrators give full access in GeotechOS, not through the API.
Send the crew before the jobs
Send each staff member before the first job that names them. Then the job's assignee_emails match accounts, and the job keeps its crew.