> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-repository/tfs.md).
# TFS
### Registering TFS repository in ARM
This section guides you to register the TFS repository in ARM.
1. Log in to your ARM account.
2. Hover your mouse over the **`Admin`** module and select the option: **`VC Repos`**.
3. Click on **`Register Repository`**.
4. Select the **`Version Control System`** as TFS on the **`Register Repository`** page.
5. Enter the name of the repository to display it locally.
6. Paste the **`Repository URL`** that TFS provides you.
7. Choose the correct user's **`Credentials`** from the list. To create a new credential, click on the **`+`** icon.
8. Click **`Test Connection`** to check if the connection has been authenticated. A success message is displayed after the authentication is completed.
9. Finally, click **`Save`** to complete the TFS repository registration process and to close the **`Register Repository`** screen.
{% hint style="info" %}
**Point to Remember**: Select the **`Enable nCino`** checkbox to register the TFS repository with nCino objects included. To easily identify nCino registered Version Control Repositories among all other repositories, nCino logos are marked in front of the Repository Label.
{% endhint %}
---
# 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://knowledgebase.autorabit.com/product-guides/arm/registration/version-control-repository/tfs.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.
