> 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-workflow.md).

# User Workflow

This section summarises the workflow for StreamLog, identifying the user performing the different stages discussed in this document.

1. The Administrator creates/adds all engineers, loggers and vehicles in StreamLog.
2. The project Leader creates a project representing all work performed with a single ECU.
3. The Project Leader assigns engineers, loggers and vehicles the Administrator adds to the Project.
4. The engineer set up the project's vehicle structures for the required tasks.
5. The engineer assigns loggers to each structure from the loggers assigned by the Project Leader.
6. The engineer assigns vehicles to loggers from the vehicles assigned by the Project Leader.

StreamLog is then ready to begin collating data from the Rebels.

**Important—**Should an Engineer require any adjustments to a vehicle structure and thus the data being captured, the current structure should be revised rather than a new structure uploaded.

 


---

# 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-workflow.md?ask=<question>&goal=<user_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.