# Customer Portal MCP Tools

## Page purpose

This page is the Oneflash MCP detail reference for the `customer-portal` module. It helps AI agents, developers, and system integrators understand endpoints for customer portals, access control, service records, and customer-facing documents. It is not a customer-portal sales page; it is an MCP reference page.

## Canonical URL

https://oneflash.hk/en/docs/mcp/tools/customer-portal

## Module summary

- Category: App
- Status: Design Draft
- Slug: `customer-portal`
- Summary: Customer Portal MCP tools support customer accounts, portal users, roles and permissions, 2FA, service records, project status, orders and bookings, document versions, invoices and payments, service requests, FAQs, forms, notifications, data sync, consent records, access logs, and audit trails.

## Agent workflow fit

Use this module when a task involves customer logins, portal users, roles, permissions, service records, project status, document versions, orders, bookings, invoices, payments, service requests, FAQs, forms, notifications, consent records, or access logs. A reliable workflow confirms the customer, portal user, and permissions first, then reads the relevant service, document, payment, or request state before any notification, sync, or data update.

## Endpoint interpretation rules

- The endpoint section on this detail page is the source of truth for exact endpoint names and capabilities.
- Permission, 2FA, consent, document-version, payment, and access-log operations require current-state and audit context first.
- Writes that affect accounts, roles, permissions, notifications, payments, or customer documents should follow the approval rules shown on the live page.
- If an endpoint requires read-first context, complete that read before changing or notifying customer data.
- Do not invent endpoint names, parameters, permissions, or side effects that are not shown on the live detail page.

## Related docs

- MCP tools catalog: https://oneflash.hk/docs/mcp