> 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/user-guide/account-administration/create-robot-users.md). # Create Robot Users 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. ### Create Robot User in IT-Conductor 1. Navigate to **Management →** **Security →** **Robots.** 2. Fill in the required attributes that reflect the intended purpose of the robot or technical user to be created. Then click to complete the robot/technical user creation.

Figure 1: Create Technical User Wizard

3. Verify whether the robot/technical user account has been added to the list.

Figure 2: List of Robot/Technical 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 with the application/DB/OS users with assigned privileges to execute the local action on the system. 1. Select **Accounts** from the object menu options in the service grid.

Figure 3: GRQ Service Grid

2. Click to add a new SAP user account.

Figure 4: GRQ System's Accounts

3. Select the robot user from the **Person** attribute dropdown menu to associate it with the SAP user account to be created.

Figure 5: Associate IT-Conductor Robot/Technical User to SAP User Account

{% hint style="info" %} **Note:** 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. {% endhint %} 4. Fill in the required attributes and click **Finish** to complete the SAP user account creation. --- # 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.itconductor.com/user-guide/account-administration/create-robot-users.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.