> ## Documentation Index
> Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# YouNegotiate Documentation

> Plain-language documentation for the YouNegotiate product.

This documentation explains the YouNegotiate product in plain language.

The content is organized to match the product sidebar so readers can open a portal, follow the menu, and find the matching page.

<Info>
  These docs are written as a product map: each page should focus on a real-world example, the expected flow, and clear behavior rules.
</Info>

## Portals

| Portal                                         | Status    | Coverage                                                                                                         |
| ---------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------- |
| [Creditor Portal](/portals/creditor)           | Available | Consumers, negotiations, payments, reports, communications, account settings, membership, and billing.           |
| [Super Admin](/portals/superadmin)             | Available | Platform accounts, membership plans, merchant requests, communications, partners, donations, reports, and users. |
| [Consumer Portal](/portals/consumer)           | Available | Consumer accounts, offers, payments, notice responses, profile, and communication controls.                      |
| [EcoMail Hub / EcoPortal](/portals/ecomailhub) | Available | Mail response operations, creditor profiles, imports, notice responses, reports, users, and campaigns.           |

## Working With These Docs

| Resource                                  | Use                                                                            |
| ----------------------------------------- | ------------------------------------------------------------------------------ |
| [Source Links](/source-reference)         | Open the Laravel app source files used by the docs.                            |
| [Style Guide](/documentation-style-guide) | Keep examples, visual flows, behavior rules, and source references consistent. |
| [Page Template](/page-template)           | Start a new portal page with the expected documentation structure.             |

## Flow Legend

| Label                                                                                                                                                               | Meaning                                           | Watch for                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------- |
| <span style={{ background: "#E0F2FE", border: "1px solid #0284C7", color: "#0C4A6E", borderRadius: "999px", padding: "2px 10px", fontWeight: 600 }}>Actor</span>    | A person or portal actor starts the action.       | Who is taking the first step?   |
| <span style={{ background: "#F8FAFC", border: "1px solid #64748B", color: "#0F172A", borderRadius: "999px", padding: "2px 10px", fontWeight: 600 }}>System</span>   | The application performs normal processing.       | What happens automatically?     |
| <span style={{ background: "#FEF3C7", border: "1px solid #D97706", color: "#78350F", borderRadius: "999px", padding: "2px 10px", fontWeight: 600 }}>Decision</span> | The system checks a rule or condition.            | What determines the next path?  |
| <span style={{ background: "#FEE2E2", border: "1px solid #DC2626", color: "#7F1D1D", borderRadius: "999px", padding: "2px 10px", fontWeight: 600 }}>Risk</span>     | Something is blocked, failed, missing, or unsafe. | What must the feature prevent?  |
| <span style={{ background: "#DCFCE7", border: "1px solid #16A34A", color: "#14532D", borderRadius: "999px", padding: "2px 10px", fontWeight: 600 }}>Outcome</span>  | A successful result or updated state.             | What should be true at the end? |

## Writing Style

Each page should stay short and non-technical:

* Real-world example
* Visual flow
* How it should work
* How it should not work
* Developer notes, when implementation risk exists
* Related app areas, when source hints help developers