> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/ctrl/guide/accessing-ctrl-via-the-portal.md).
# Accessing Ctrl via the Portal
Ctrl is accessed through the Betradar Portal, a central entry point that hosts multiple products and shared tools. When you log in to the [Portal](https://portal.betradar.com/), you’ll notice a set of global features available at the top of the interface.
Fig 1. Portal login page
These features are accessible across all products, including Ctrl, and provide helpful resources and account-related tools.
Fig 2. Portal Homepage
Here’s a quick overview of the Portal features:
1\. **Operational** – This includes updates about any upcoming maintenance, aswell\[SM1] \[WN2] as downtime-related notifications. From here, you can also access our Status Page for CTRL and Unified Feed services. On this page you will find live information and real-time updates of our services, along with any scheduled maintenance. You can subscribe to this page by contacting our Support team via chat or email, to ensure no important updates on systems related to Ctrl and the Unified Odds Feed are missed.
2\. **Support Portal** – This option on the Portal page lets you create and monitor tickets. You will also find relevant documentation within this space.
3\. **News** – Within this space, you will find all relevant news and updates about our Betting Products. By clicking on a specific News message, you will be forwarded to our Blog. Here you can read the full article about the update and access some pertinent to the news details and links.
4\. **Help** – This allows you to check the Unified Feed Status Page, access our Blog and our Feature Updates page. Here you can also find this CTRL User Manual, which includes the most complete description of the CTRL platform.
5. **Status** – This page provides real-time updates and details on any scheduled maintenance. If you encounter issues, this should be your first stop before reaching out to our support team.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/ctrl/guide/accessing-ctrl-via-the-portal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.