> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/7.-planning-budgeting-and-forecasting/forecasting-writeback-matrix/user-access-control.md).
# User Access Control
You can set user permissions for reading and writing forecast data, editing forecasts, re-forecasting, closing periods, and deficit distribution.
To set it, click on the **Manage** button in the **Forecast** tab. This opens the Forecast measure side panel, where you can set the user permissions under the 'Sharing' tab. By default, all users are permitted to do the aforementioned actions.
User access permissions
**Read:** Users with read access would be able to only view the data and add comments.
**Read+Write:** Users with both read and write access can modify and distribute the forecast data to leaf levels.
**Close Period Actions:** Users added here will have read/write access as well as permission to perform critical forecast actions like closing the actuals, re-forecasting, and distributing the deficit.
{% hint style="info" %}
Users having read+write access without 'Close Period Actions' permission cannot close actuals, re-forecast, or distribute deficit.
{% endhint %}
Read/Write and Close Period Actions
The access control for forecasting can also be set from the **Manage Columns** dropdown at the top just like [configuring the access control for the measures](https://docs.inforiver.com/working-with-inforiver/7.-planning-budgeting-and-forecasting/forecasting-writeback-matrix/pages/ikgtokcJ0oes0aCiLKJA#id-3.-access-control) as shown below.
User access control for forecasting
---
# 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.inforiver.com/working-with-inforiver/7.-planning-budgeting-and-forecasting/forecasting-writeback-matrix/user-access-control.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.
