> 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/personas-roles-activities/financial-admin.md). # Financial Admin Financial Admins are the primary managers of the AWS Cloud Estate. View Application * All Financial Scope Amazon Q in QuickSight Topics / CUDOS Access * Topics: AWS Vendor, AWS Spending * CUDOS Daily Activities * Adding/modifying Budgets * Adding/modifying Users to Budgets * Adding/modifying AWS Account Allocation to Budgets * Adding AWS Credits to Budgets * Claiming/Unclaiming Resources to Workloads * Adding QuickSight Dashbaords/Topics * Monitoring Spending to Budgets * Approves/Ignore Cost Recommendations Weekly Activities * Monitoring Spend Approvals Monthly * Close Month * Download/Upload AP and FP\&A Files --- # 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.finopscenter.com/personas-roles-activities/financial-admin.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.