> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/cost-center/cost-allocation.md). # Cost Allocation * Maintain cost allocation ratios, which can be split by employee or by role. * **Operational Steps:**\ ① Enter the "Cost Split" settings and add the new statistical items to the cost split items, then click confirm.\ ② Click on "Maintain Cost Split Ratios." Here, there are two methods for ratio allocation: by employee and by role. If you need to add role-based allocation, you must first set up role associations with employees in the "User Center."\ ③ Click "Add Split Ratio." If allocating by employee, select the "Staff"; if by role, select the "By role", then choose the cost center and set the ratio, ensuring that the **total ratio equals 100%**.\ ④ After allocation, click "Split Summary" to view the allocation percentage of the employee in their respective cost center.\ ⑤ Return to the cost allocation interface, where the system will automatically calculate the costs of that employee across various cost centers. Clicking \[Cost Rollup] will show the labor costs allocated by "Cost Center."

--- # 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.coreway.com/coreway-hr/cost-center/cost-allocation.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.