> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/appendix/user-administration.md). # User Administration StreamLog contains many different user types with varying levels of access to various features within the software. There are three types of user rights— Administrator, Project Manager and Engineer. The table below indicates the actions and the level of user required.
ActionAdministratorProject ManagerEngineer
Create/Edit/Delete Project
Add/Delete Project Manager
Add/Delete Engineer
Add/Delete Data Logger
Add/Delete Vehicle
Assign an Engineer to a Project
Assign a Data Logger to a Project
Assign a Vehicle to a Data Logger
Add a Data Logger to a Configuration
Remove a Data Logger from a Configuration
Add a Configuration to a Project
Remove a Configuration from a Project
Read an IVD file
Delete an IVD file
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.influxtechnology.com/support_guides/streamlog/streamlog-user-documentation/quick-start-guide/appendix/user-administration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.