> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/user-management/robot-credentials.md).

# Robot Credentials

## Overview

We have introduced a new way of credentialing RPA Bots which want to access Enate going forward, specifically when using Robots with new APIs versions (i.e. V1 onwards).&#x20;

This is relevant for your Enate implementation IF:

* You're using a RPA Bots AND
* Your Bots are NOT using the Activity Library AND
* You're wanting them use the new 'V1 and beyond' version of APIs

#### What's Changing - New API version & New Credentials approach

Until now, the way to credential Bots to use Enate has been to set up a standard (User) Application Credential for them. The new versions of APIs which Enate is using going forward will use a new approach of explicit 'Robot Credentials' - a new feature accessible in the User section of Builder.

#### Steps required to get Robot & Robot Credentials working with new version APIs

* Create a new Robot (or move to next step if Robot already exists)
* Create the Robot Credential for the bot (to generate client id / client secret)
* Use the new authentication endpoint:

  * '***/auth/oauth/token***' rather than the previous&#x20;
  * '*/webapi/oauth/token*'

  (required as part of migration to new apis)
* Migrate any API calls to the new endpoints + new DTOs (required as part of migration to new apis)&#x20;

### New section in User Management: Robot Credentials&#x20;

To add or edit bot credentials Builder users will need to navigate to the new 'Robot Credential' page in the User Management section of Builder.

<figure><img src="/files/EJrIGcaaVYt8uyUFqqy9" alt=""><figcaption></figcaption></figure>

Here Builder users will be able to add, edit or delete any bot credentials as well as generate new keys.

You can see a list of your existing Robot Credentials, and information such as Robot Name, Client ID, Operational Role, Builder Role and Expiry Date.

You can customize the order in which you want to view your Robot Credentials by clicking on each column header.&#x20;

You can also use the search function at the top of the page.

### Creating new Robot Credentials

Once you have a Robot created which you need Robot Credentials for, navigate to the Robot Credentials page and click on the plus icon to bring up the 'Add Robot Credentials' pop-up.&#x20;

<figure><img src="/files/5Ize037Rk7lcYVlR7Etg" alt=""><figcaption></figcaption></figure>

Activities here are:

* Select the relevant Robot from the drop down list.
* Give the Robot Credential a name.
* Set an expiry date for the Credential&#x20;
* Specify an Operational Role (mandatory)
* If desired, also set a Builder Role\*.

{% hint style="info" %}
\*The Builder role selected here cannot have feature access which exceeds that of the selected Robot AND cannot exceed that of the user creating the Robot Credential. If no Builder Role has been set for the related Robot, no Builder Role can be set here for the Robot Credential.
{% endhint %}

Once you have filled out all of these details, you can click to 'Generate Key'. You can then use the generated Client ID and Secret Key to connect the bot to an API.

### How do you generate a new key for an existing bot credentials?

If you need to generate a new key for existing bot credentials, you will first need to navigate to the 'Robot Configuration' page. Once on the page you will need to click on the ellipsis menu at the end of the bot row that you want to generate a new key for, and click to edit. This will bring up the 'Edit Robot Credentials' pop-up where you can click to generate a new key.

<figure><img src="/files/xtBHiXeywXZfjVzxymbG" alt=""><figcaption></figcaption></figure>

### How do you edit Robot Credentials?

You can edit bot credentials by first to navigating to the 'Robot Configuration' page. Once on the page you will need to click on the ellipsis menu at the end of the bot row that you want to generate a new key for, and click to edit. You can change the bot, the name, the expiry date as well as the operational and builder roles for the credentials. Once you have finished making your edits, you will need to hit the 'Update and Generate Key' Button.

<figure><img src="/files/qzSWcFkqANJ27tWlqMin" alt=""><figcaption></figcaption></figure>

### How do you delete Robot Credentials?

You can delete bot credentials by first to navigating to the 'Robot Configuration' page. Once on the page you will need to click on the ellipsis menu at the end of the bot row that you want to delete and click on the 'Delete' button.&#x20;

<figure><img src="/files/9P4kPQnbAunv5n7dxESA" alt=""><figcaption></figcaption></figure>


---

# 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.enate.net/enate-help/builder/builder-2021.1/user-management/robot-credentials.md?ask=<question>&goal=<endgoal>
```

`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.
