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.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.
These docs are written as a product map: each page should focus on a real-world example, the expected flow, and clear behavior rules.
Portals
| Portal | Status | Coverage |
|---|---|---|
| Creditor Portal | Available | Consumers, negotiations, payments, reports, communications, account settings, membership, and billing. |
| Superadmin Portal | Available | Platform accounts, membership plans, merchant requests, communications, partners, donations, reports, and users. |
| Consumer Portal | Planned | Consumer accounts, offers, payments, notice responses, profile, and communication controls. |
| Ecomailhub Portal | Later | MailHub users, creditor profiles, imports, notice responses, reports, and communications. |
Working With These Docs
| Resource | Use |
|---|---|
| Source Links | Open the Laravel app source files used by the docs. |
| Style Guide | Keep examples, visual flows, behavior rules, and source references consistent. |
| Page Template | Start a new portal page with the expected documentation structure. |
Flow Legend
| Label | Meaning | Watch for |
|---|---|---|
| Actor | A person or portal actor starts the action. | Who is taking the first step? |
| System | The application performs normal processing. | What happens automatically? |
| Decision | The system checks a rule or condition. | What determines the next path? |
| Risk | Something is blocked, failed, missing, or unsafe. | What must the feature prevent? |
| Outcome | 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