> For the complete documentation index, see [llms.txt](https://docs.allforclimate.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allforclimate.earth/services/level-up-your-collective-extra-features/include-your-own-spending-policy.md).
# Include your own spending policy
*Does your group have specific spending requirements?*\
*Is there a maximum reimbursable amount per category?*\
*Do larger expenses need prior approval from the team?*\
*Would you like to make these expectations clear to everyone submitting an expense?*
\
No problem 😊 Each Collective can define its own expense policy to ensure clarity and transparency.
{% hint style="success" %}
To set or update your policies, go to:\
**Dashboard → Settings → Policies**\
(See screenshot below.)
{% endhint %}
### **Expense Policy**
Use this section to provide clear guidance for anyone submitting expenses. Clear policies help prevent delays and misunderstandings.\
\
For example, you can specify:
* How expenses should be titled and described
* Which types of expenses are eligible
* What receipts or proof of payment are required
* Maximum reimbursable amounts per category
* Whether larger expenses require prior team approval
* A link to an external document with more detailed guidance
\
Your policy will appear in the expense submission form, underneath the general expense policy. Submitters will need to confirm that they have read and accepted your policy before completing their submission. Please see the example below.
---
# 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.allforclimate.earth/services/level-up-your-collective-extra-features/include-your-own-spending-policy.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.
