Client portal — one login for the customer, every module they touch.

The wedge

Every professional-services team ends up with a graveyard of one-off customer-facing tools: DocuSign for signing, Stripe checkout for paying, Zendesk for support, a Notion page for project status. Each with its own auth, its own audit trail, its own brand chrome. Odexy Clients unifies every customer-facing surface behind one branded portal + one login + one audit log.

What ships today

• Portal login — magic-link or password; crm_companies + optional per-user seat. Customers are first-class users with client role — they see only what you've shared with them.
• Contracts — sign contracts you've sent them; see every version; download the executed PDF. Every action logs to your audit trail.
• Invoices — view every invoice + statement + credit note tied to their company; pay via any gateway you've enabled (Stripe / Paddle / Razorpay / Adyen / PayPal / and 14 more).
• Tickets — file support tickets against your team; see status + SLA countdown + agent replies live.
• Projects — read-only visibility into projects tagged as "client-visible"; see task status + progress + upcoming deadlines.
• Forms — fill any form you send them (onboarding intake, feedback surveys, RFP responses). Submissions land as CRM leads or module-specific entities per the form definition.
• Documents — a per-company Drive folder holds every file you've shared. Downloads audited.
• Notifications — email + in-portal notifications for every activity that involves them.

How it integrates

• CRM — every client is a crm_companies row. Contact routing lives in the shared roster (per-purpose contacts: billing / support / primary / legal).
• Contracts — signing portal integrates natively; magic-link + in-portal both available.
• Sales — invoices + payments + statements + credit notes; hosted checkout when the customer clicks pay.
• Support — ticket portal + reply UI + SLA visibility.
• Projects + HRM — read-only visibility into tagged work.
• Storage — every file the customer sees is a real Storage object with per-tenant + per-portal permissions.

How the AI helps

For the operator (you):

• "Show me every client whose last support ticket has been open more than 5 days."
• "Draft a welcome email for the client Acme just signed on."
• "Which client accounts have unpaid invoices over 30 days AND an active support ticket?"

For the client (through your permissions-gated agent):

• "When's my next invoice due?"
• "Show me the executed MSA."
• "File a ticket saying my dashboard's not loading."

The client-side AI (opt-in per operator) inherits the client role's permissions — it can never see another customer's data, can never delete records, can never approve anything on your behalf.

Built for scale

• Per-tenant branding — every operator's portal renders their brand (logo, colors, tone, sender email). Customers never see "Odexy" — they see your brand.
• Custom domains — host portal.yourcompany.com once provisioned.
• Per-company gating — turn features on/off per company (some clients see contracts + invoices only; some see everything).
• Audit log — every client login, every download, every payment, every signature audits with IP + user-agent + timestamp.
• Impersonation — support your customer over the phone with permission-scoped impersonation (with per-session audit).
• Realtime — invoice status, ticket replies, project updates all live-update without reload.