# What is a service user?

### A service user keeps your data secure and ensures smooth functionality.

There is probably no human user who needs access to every corner of a company's task management tool.  Teams need private spaces to collaborate and triage, and permissioning is the solution to access management.  This is why **service users** exist.

#### A **service user** is a user account configured by an **administrator** for purposes such as API access.

{% hint style="info" %}
The only time the credentials of a **service user** should be used for login via the web browser is during configuration of an [**Integration**](/streamly/concepts/integration.md).
{% endhint %}

Using a **service user** keeps real users from receiving irrelevant notifications and emails, and it ensures that access controls remain in place.

In the event that an employee leaves the company, having used a **service user** to connect a tool ensures continuity for any integrations.

{% hint style="warning" %}
Setting up **Integrations** while logged in as **service user** is the best way to avoid frustrating issues with the [**tools**](/streamly/reference/streams/modify/tools.md) connected to your [**Streams**](/streamly/concepts/stream.md).
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://happybara.gitbook.io/streamly/concepts/service-user.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.