# Subuser

- [Subuser](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/index.md): API calls related to sub-users, that is, additional users who have access to your account and monitoring assets.
- [Subuser places](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/places.md): Contains API calls to control which places is available to which sub-user.
- [Subuser security group](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/security_group.md)
- [Subuser session](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/session.md): Sub-user session actions to obtain its hash
- [Subuser tracker](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/tracker.md): Contains API calls to control which tracker is available to which sub-user.
- [Subuser geofences](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser/zones.md): Contains API calls to control which geofences is available to which sub-user.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/subuser.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.