> For the complete documentation index, see [llms.txt](https://docs.mosofin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosofin.com/start-here/how-to-get-the-most-out-of-mosofin.md).

# Get more from MosoFin

Use this checklist to keep client work accurate, repeatable, and easy to trace.

<img src="/files/P28P9NwNJ4klbUdbxU4a" alt="MosoFin review workflow" width="735">

## Group related entities in each workspace

Name workspaces consistently and connect the QuickBooks entities that should be reviewed together. Each workspace can authorize up to five QuickBooks entities, and every new workspace has its own separate allowance.

## Ask focused questions

Include the reporting period, comparison period, and decision you are trying to make. Ask follow-up questions when a result is surprising, and request the accounts or transactions that support the explanation.

## Turn repeatable work into skills

When a review works well, save the method as a skill. Good candidates include month-end close checks, variance analysis, receivables review, cash explanations, and recurring client summaries.

## Use the permission levels intentionally

Keep routine, low-risk reads **Enabled**. Use **Require permission** when a tool should pause for review. Use **Disabled** when a source capability should not be available in that workspace.

## Review activity

Use the Activity log to confirm which tools ran and when policies changed. This is especially useful when investigating an unexpected answer or documenting a review process.

## Check live account information

Use **Billing** for the current subscription state and **Usage** for authorized QuickBooks entity counts and workspace activity. These pages are the source of truth for your account's current state and renewal details.


---

# 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.mosofin.com/start-here/how-to-get-the-most-out-of-mosofin.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.
