> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/material-management/material-management-module/mm-masters/cc-store-user.md).
# CC Store User
A **CC Store User** is an individual who is authorised to access and operate within a Centralised/Corporate (CC) Store in the system. CC Store Users are responsible for managing store-related activities and ensuring that inventory transactions are performed accurately and according to established procedures.
## Steps to Create and View a CC Store User
Step 1: Navigate to **Master** menu in the Inventory module.
1. Click on **CC Store User**.
* The CC Store User screen will be displayed.
Step 2: Click the **Open** button.
Step 3: In the **CC Store User** screen, select the **Basis, User, Department** and **CC Store.**
1. Choose the appropriate CC Store based on the user's operational requirements.
2. Verify that the selected user, department, and store details are correct.
Step 4: After selecting the required details, click the **Save** button.
* The user will be successfully assigned to the selected CC Store.
---
# 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://help.rbsgo.com/material-management/material-management-module/mm-masters/cc-store-user.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.
