> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/organization-administration/subscription-and-billing.md).

# Subscription and billing

## Updating your subscription

To add users, remove users, or cancel your subscription, email <support@cogram.com> and we'll take care of it.

Seats are counted per module. Members with no module licenses have the **View & Respond** access level, with read-only access. See [Licensing](https://docs.cogram.com/organization-administration/licensing.md) for how module entitlements, seats, and access levels work.

## AI credits

Automations and built-in AI features use credits from a monthly allowance. Agent chat, meetings and email filing do not use credits. To see the credits used or request more, see [AI credits](https://docs.cogram.com/organization-administration/agents.md#ai-credits).

## Billing

Cogram sends you automatic emails after processing payments.

To view invoices and receipts, please locate this email by searching for "Your receipt from Cogram" in your inbox, or "@stripe.com" (the domain from which these emails are sent).

Then click "Download invoice" or "Download receipt" in the email.

For help, contact <mark style="color:blue;"><support@cogram.com></mark>.


---

# 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.cogram.com/organization-administration/subscription-and-billing.md?ask=<question>&goal=<user_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.
