# Settings
The *Settings* page is where you view the Project’s settings and configuration files, as well as perform tasks such as scanning the vault file, scanning the source organization for repositories, and deleting the Project.
The key parts of the *Dashboard* page are described in detail below.
### Check Vault
The **Check Vault** button performs a test on your Project’s vault file, `config/vault.age`, to confirm that it contains the necessary data, namely:
* The personal access token for the Azure DevOps organization,
* The personal access token for the GitHub organization
When you click the **Check Vault** button, you’ll see this message...
...and when the process is complete, the results — information about the personal access tokens — will be displayed on the page’s *Vault* section (see below for details).
### Scan Sources
The **Scan Sources** button starts the process of scanning the Azure DevOps organization for repositories.
When you click the **Scan Sources** button, you’ll see this message...
...and when the process is complete, the results will be visible in a couple of places:
* In the *Dashboard* page’s *Trends* section, under *Repositories Discovered*. If this is the first time you scanned sources, this value will now contain the number of repositories Warp found in the Azure DevOps organization. If this is *not* time, this value will be updated to reflect any repositories that have been added since the last scan.
* In the project’s *Migration HQ* repository, where any repositories discovered since the last scan (or, if this is the first scan, all the repositories Warp was able to find) will be assigned an issue and appear as open issues on the *Issues* page.
### Configuration
The *Configuration* section shows information about the Project’s configuration files. It displays the following information:
* **Warp.yml.** The name of the project’s configuration file. You can view and edit this file in GitHub by clicking the button on the right side of this section.
* **The partial hash of the Project’s vault file.** This is the first 7 characters of the SHA hash of the Project’s vault file, `config/vault.age`, which contains the encrypted personal access tokens for the Project’s Azure DevOps and GitHub organizations. You can view this file in GitHub by clicking the partial hash.
* **The** **button.** Displays a reminder that you can edit `warp.yml` in GitHub.
### Destination
The *Destination* section shows the GitHub organization where this Project’s repositories are to be migrated. It displays the following for the organization:
* **The organization name.** In the example above, it’s **Hypotheticorp5678**.
* **The** **button.** Displays a reminder that repositories from your sources will be migrated to this GitHub organization.
* **The** **button.** Click this to open a new browser to the organization’s *Migration HQ* repository.
### Vault
The *Vault* section contains a list of the contents of the vault — the file containing the following personal access tokens that Warp uses to access the source and destination organizations in order to perform migrations.
Each item in this list represents a personal access token and contains the following:
* **The name of the token’s platform.** In the example above, the first token is for Azure DevOps and the second one is for GitHub.
* **The organization for which the token was issued.** In the example above, the first token is for the **joey-ado-testing** organization in Azure DevOps, and the second is for the **Hypotheticorp5678** organization in GitHub.
* **The unique identifier for the token.**
* **The** **button.** Clicking this button displays a dialog box showing when the token was last checked using the **Check Vault** button:
### Danger Zone
The *Danger Zone* contains a single control: the **Delete Project** button, which deletes the Project.
As a safety precaution, clicking the **Delete Project** button causes this dialog box to appear:
Clicking the **Confirm** button will permanently delete the project. Use this feature with caution!
---
# 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://kb.packfiles.io/using-warp/projects/settings.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.