> For the complete documentation index, see [llms.txt](https://documentation.ardoq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ardoq.com/configuration/service-accounts.md).

# Service Accounts

Schedule your integrations to run independent of users with Service Accounts.

A Service Account is a special user account in your organization created solely to own an API token for integrations — eliminating the need for proxy users tied to real employees.

## Creating a Service Account

{% stepper %}
{% step %}

### Navigate to access control

Click your organization name in the top-left, select **Admin** > **Access control** and select the the **Service accounts** tab
{% endstep %}

{% step %}

### Create and configure account

Click the **Create new** button in the top-right corner and give your service account a name, role, and description to refer to later.
{% endstep %}

{% step %}

### Save your token&#x20;

Make a copy of your service account token — it will only be shown once and you will have to re-generate it if you lose it.
{% endstep %}
{% endstepper %}

## Service Accounts in Integrations

{% hint style="info" %}
Before scheduling integrations, you'll need to create a service account as described in this article. Service Accounts for integration require at least writer permissions to be able to run schedules.
{% endhint %}

By default, scheduled integrations in Ardoq are configured to run under the permissions of the account that scheduled the integration. However, if that account is deactivated or removed, scheduled integrations associated with that account will no longer run.

A service accounts is a non-user account managed by an Ardoq administrator that can be used for running integrations without being tied to a specific user.

## Updating Existing Integrations with a Service Account <a href="#h_d9c5f847b3" id="h_d9c5f847b3"></a>

Navigate to the integrations dashboard (Imports & Integrations from the main menu). Select a schedule, click ⋮ (more options button), and select **Edit schedule**. In the dialog that opens, select the name of your service account under the **Execute as** dropdown, and click **Save changes**.

<figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2Ftt8jZLQR3L3yDbkfJKm8%2Fimage.png?alt=media&amp;token=deab81b7-7028-421f-a147-40f88b807f2a" alt=""><figcaption></figcaption></figure>

## Setting Up a Service Account for New Integrations <a href="#h_4d704bfadb" id="h_4d704bfadb"></a>

When setting up a scheduled integration, you can configure your import as normal and import your data manually. When asked to schedule your import, you will also have an option to execute the scheduled integration as a service account.

<figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FfwQ3ibw0VWEImO9AjkQy%2Fimage.png?alt=media&amp;token=198dbf8a-f6bf-4083-892e-9993c412980f" alt=""><figcaption></figcaption></figure>

## Known Limitations <a href="#h_3267c7a83b" id="h_3267c7a83b"></a>

Service Accounts in Ardoq are bound to an API token, but the token will not be necessary for setting up an integration. As a consequence, the Service Accounts page will show that it is never used even if your have an active service account associated with scheduled integrations.

<figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FcrezVxSbIhPEDIv4rKav%2Fimage.png?alt=media&amp;token=77e4ad8a-87f0-47ce-8dfd-e1ad150abd56" alt=""><figcaption></figcaption></figure>
