> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/faqs/service_accounts.md).

# Using Service Accounts with Nightfall

Learn if you can use service accounts for authentication in the Nightfall integrations.

As a best practice, service accounts are recommended for authentication because they will not be tied to any specific user, and will persist regardless of which users may leave/join your organization. <br>

Also, as a security measure, it may be beneficial to provide the access privileges required to a service account, rather than having to manage permissions given to specific users. That being said, the requirements for service accounts differ by integration, as outlined below.\ <br>

| **Integrations**                | **Service Account Required?**     | **What will happen if the installing user leaves the company?**                                                                                                    |
| ------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Slack**                       | **Recommended, but not required** | **If the person who authenticates leaves the company, you will be prompted to re-authenticate the next time you log in to the dashboard.**                         |
| **Google Drive**                | **Recommended, but not required** | <p><strong>If the person who authenticates leaves the company, you will be prompted to re-authenticate the next time you log in to the dashboard.</strong><br></p> |
| **Github**                      | **No need for a service account** | **If the person who installed the app on a given organization leaves, the app will continue to work without interruption.**                                        |
| **Atlassian (Jira/Confluence)** | **Recommended, but not required** | **If the person who authenticates leaves the company, you will be prompted to re-authenticate the next time you log in to the dashboard.**                         |

For any other questions/comments regarding service accounts, please contact us at <support@nightfall.ai>. <br>


---

# 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://help.nightfall.ai/faqs/service_accounts.md?ask=<question>&goal=<user_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.