> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/automation/start-stop-automation/robot-user.md). # Robot User Robot Users, also known as Technical Users, are capable of performing tasks that require particular backend system authorizations. Robot users are assigned to the process definition to execute an automation workflow. To create a robot user, navigate to **Management >** **Security >** **Robots**

Figure 1: Management Menu in IT-Conductor

Give the new technical user a descriptive name related to the procedure that it will be used for. In this case, the name will be SystemStartStop. Click on the "+" icon to finish.

Figure 2: Create a Technical (Robot) User

Figure 3: List of Robot Users

### Associate Robot User to Account User The next step after creating a robot user is to create a robot account. An IT-Conductor robot account should be created and associated to the application/DB/OS users with assigned privileges to execute the local action on the system. First, navigate to the "Accounts" option in the system grid.

Figure 4: GRQ System Grid

Figure 5: GRQ System's Accounts

Click on the "+" icon and fill in the required attributes. On the "Person" attribute, be sure to select the Robot User. Then click on the finish button to save. The Client/User attributes are used for SAP accounts. A Robot account (or a regular user account) can have multiple accounts associated to interact with multiple systems.

Figure 6: Assign Robot User to Account

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/automation/start-stop-automation/robot-user.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.