> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/account-and-billing/account-and-billing.md).

# Account and Billing

### Overview

Account and Billing covers billing, security, and Account-wide administration.

These controls affect every Organization and Project.

### Key Concepts

* **Plan**: entitlement set that controls feature availability
* **Billing owner**: role responsible for invoices and renewals
* **Account Admin**: role that can manage Account-wide settings
* **Security posture**: access and audit controls used to reduce risk

### How It’s Used

Use these pages during onboarding and annual renewal cycles.

Use them during governance changes and access reviews.

### Benefits

* Clear ownership for billing and renewals
* Reduced risk through consistent access governance
* Faster support escalation with correct routing

### Setup Steps

Use the relevant guide:

* [Plans & Pricing](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/324eqnEKAkp5tc5nlPBA)
* [Account Management](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/a94LDZtBOMRslzGzNKPN)
* [Team and Account Management](/account-and-billing/team-and-account-management.md)
* [Security & Compliance](/account-and-billing/security-and-compliance.md)

### Best Practices

* Keep billing ownership and technical administration separate when possible.
* Limit Account Admin and Owner roles to a small set.
* Review access after major delivery milestones and quarterly.

### Summary

Account and Billing controls cover entitlements, billing ownership, access governance, and security posture.

Support routing: [Contact Support](/resources/contact-support.md)


---

# 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://help.transform.ai/account-and-billing/account-and-billing.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.