> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/credit/getting-started/roles-and-permissions-required-for-credit.md).

# Roles and Permissions Required for Credit

Managing credit contracts in the XYB Console requires specific permissions depending on the actions a user needs to perform. This article outlines the **key credit-related permissions**, what they allow, and when they are typically required.

***

### Credit Contract Permissions

These permissions control access to **credit contracts and their lifecycle**, including creation, updates, payouts, and financial operations.

| Permission                     | Description                        | Typical Use Cases                                                |
| ------------------------------ | ---------------------------------- | ---------------------------------------------------------------- |
| `credit_contract_r`            | Can read credit contract           | View contracts, query contract data, access contract details     |
| `credit_contract_w`            | Can write credit contract          | Create contracts, create or update terms, modify contract status |
| `credit_contract_approve_w`    | Can approve credit contract        | Approve contract applications, authorize contract creation       |
| `credit_contract_sign_w`       | Can sign credit contract           | Sign contracts and finalize agreements                           |
| `credit_contract_payout_w`     | Can payout credit contract         | Execute contract payouts and disburse funds                      |
| `credit_contract_financial_w`  | Can write contract financials      | Perform write-offs, financial corrections, and adjustments       |
| `credit_contract_debt_w`       | Can write contract debt collection | Manage debt collection processes and update collection status    |
| `credit_contract_collateral_w` | Can manage contract collaterals    | Manage collaterals and update collateral information             |

***

### Customer & Product Permissions

These permissions control access to **customer data and credit product configuration** linked to contracts.

| Permission                   | Description                        | Typical Use Cases                                                |
| ---------------------------- | ---------------------------------- | ---------------------------------------------------------------- |
| `credit_contract_customer_r` | Can read credit contract customer  | View customer information and access customer data               |
| `credit_contract_customer_w` | Can write credit contract customer | Update customer information and manage customer records          |
| `credit_contract_product_r`  | Can read credit contract product   | Browse credit products and view product configurations           |
| `credit_contract_product_w`  | Can write credit contract product  | Create products, modify product terms, and update configurations |

***

### Day Change Permissions

Day change permissions are required to **monitor or trigger batch processing**, such as invoice generation and schedule recalculations.

| Permission            | Description                   | Typical Use Cases                                   |
| --------------------- | ----------------------------- | --------------------------------------------------- |
| `credit_day_change_r` | Can read credit day change    | View day change status and monitor batch processes  |
| `credit_day_change_w` | Can execute credit day change | Trigger day change operations and process schedules |

***

### Recommended Permission Sets

#### Credit Operations / Testing Role

For users who need to **create contracts, manage repayments, run payment holidays, extra payouts, and write-offs**, the following permissions are typically required:

* `credit_contract_r`
* `credit_contract_w`
* `credit_contract_financial_w`
* `credit_contract_payout_w`
* `credit_day_change_r`
* `credit_day_change_w`

#### Read-Only Role

For users who only need to **view credit contracts and related data**:

* `credit_contract_r`
* `credit_contract_customer_r`
* `credit_contract_product_r`

***

### Notes

* Approval and signing permissions are only required if your workflow includes **manual approval or signing steps**.
* Debt collection permissions should only be assigned to users responsible for **collections and arrears management**.
* Permissions should be granted following the **principle of least privilege**, ensuring users only have access to the actions they need.

***


---

# 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.xyb.co/credit/getting-started/roles-and-permissions-required-for-credit.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.