# Define service accounts
## Overview of service accounts
Service accounts are emails associated with the integration that **do not** exist as Members in the Secoda Workspace. These emails can fall under two categories: actual humans (your coworkers) who are not yet members in Secoda yet; or bot accounts associated with the integration.
{% hint style="info" %}
Ideally, you'd want to have the human-related emails checked off so that they are calculated towards the popularity of a resource. However, for bot accounts you may not want them included because it would alter the accuracy of the popularity metric.
{% endhint %}
To define which emails should be counted, please navigate to the Popularity tab of the integration settings. You'll see a list of emails captured from the integration that do not exist as Members in the Secoda Workspace. You'll need to select all the emails that you'd like to count towards Popularity, and uncheck those that should not be counted.
For example, if `bob@company.com` runs a query against your Redshift instance, but is not a member of the Secoda workspace, `bob@company.com` will be considered a Service Account in Secoda and will show up in the Popularity tab of the integrations settings as seen below.
If an email associated with a Service Account signs into Secoda, it will be converted from a Service Account to a Secoda user and show up in the Members tab of the workspace settings.
To learn more about how Popularity is calculated, please see the documentation [here](https://docs.secoda.co/faq#how-is-the-popularity-calculated).
{% hint style="info" %}
Not using Secoda to manage your data documentation yet? Sign up for free [here](https://app.secoda.co/) 👈
{% 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://docs.secoda.co/readme/secoda-as-an-admin/connect-your-data/define-service-accounts.md?ask=
```
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.
