> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/enterprise-platform/access-management/service-accounts-for-programmatic-access/managing-service-accounts-in-the-dashboard.md).
# Managing Service Accounts in the Dashboard
## Creating Service Accounts
To create a service account for your organization you need to go to the Service Accounts section of the [VGS Dashboard > Service Accounts](https://dashboard.verygoodsecurity.com/cmp) and click on a Create New button. Add a label name and scopes for this service account, which will be related to the actively selected tenant. The label field is for your use.
Scopes to provide access to resources. Please mind, scopes cannot be modified after creation.
Once created, you will be prompted to download the Client ID and Secret. These artefacts are made available **only after** the initial point of creation, so be sure to save this data to your local machine for later reference.
## Viewing Service Accounts
Org Admins can check all the Service Accounts linked to the organization through [VGS Dashboard > Organization Settings > Users](https://dashboard.verygoodsecurity.com/cmp).
## Deleting Service Accounts
To delete a service account, click on the remove button next to the service account you would like to delete. Then, confirm the action.
---
# 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://docs.verygoodsecurity.com/enterprise-platform/access-management/service-accounts-for-programmatic-access/managing-service-accounts-in-the-dashboard.md?ask=&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.
