> For the complete documentation index, see [llms.txt](https://docs.finopscenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finopscenter.com/cfm-processes/financial-budget-to-cloud-allocation/rollup-allocation-visibility.md).

# Rollup Allocation/Visibility

Roles and Users have Allocation/Visibility within their Financial Scope. The allocation is across all Tabs and within their Amazon Q Topics. 

On the Summary Page, the Account Allocation for the User are shown Across Current, Expiring, New, Past, and Future. 

<figure><img src="/files/dxBNFWRayNTsVADE1gbo" alt=""><figcaption><p>Acccout Allocation </p></figcaption></figure>

For Financial Admin, Admin, Vendor Management, Business Unit Owner, Department Owner, and Portfolio Owners Accounts/Workload needs have a Workload Created by the Product Owner for it to be visible.&#x20;

<figure><img src="/files/jerpfdLh5UWsHWkoAvjv" alt=""><figcaption><p>Space Visibility</p></figcaption></figure>

Budget Pages, Reporting, and Amazon Q Visibility will be defined on their Functional Page Documentation.&#x20;


---

# 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.finopscenter.com/cfm-processes/financial-budget-to-cloud-allocation/rollup-allocation-visibility.md?ask=<question>&goal=<endgoal>
```

`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.