Client Portal
Sign in with your company account. Your workspace, role, and available tools load automatically.
Sign in with your company account. Your workspace, role, and available tools load automatically.
A clean starting point for requests, clients, documents, billing, and the next onboarding steps.
Start onboarding with a clean workspace, then add clients, documents, billing, and request intake as work begins.
Preview analytics from seeded Super Admin data.
Super Admin preview shows company workspace, modules, and operating posture without loading private documents or records.
Permission-aware assistant workspace skeleton. No AI provider is connected yet.
TODO: Connect approved knowledge sources, prompt policies, usage logging, and assistant action permissions.
Structured company knowledge, SOPs, and published guides for future search and assistant use.
TODO: Add draft, review, publish, archive, category permissions, and client-visible article controls.
Future calendar, appointments, resource assignments, and booking rules.
TODO: Add business hours, appointment types, resource rules, buffers, reminders, and calendar integration settings.
Live map, tracked assets, route history, and location health placeholders.
TODO: Add provider credentials, geofence rules, route replay, driver consent controls, and retention settings.
Item catalog, stock levels, categories, low-stock alerts, and inventory activity skeleton.
TODO: Add receiving, adjustments, transfers, consumption, reorder rules, vendor links, and audit history.
Security, network, telecom, and field service support.
Recent health updates from scheduled workflows.
Scoped to the current organization and filtered by client account, service type, or site.
Conditions keep the rule focused on the right client, site, or request status.
External communication and billing changes still require confirmation or role permission.
Unified conversation, team message, customer message, unread count, and template skeleton.
Messages will stay scoped to this company and user role.
TODO: Add response templates, approval-safe client copy, channel defaults, quiet hours, and delivery tracking.
Company operations view
id, slug, name, portal_title, domain, brand colors
id, organization_id, user_id, role, created_at
id, organization_id, name, primary_contact, status, notes
id, client_account_id, name, address, site_type, status
id, organization_id, client_account_id, display_name, email, owner_user_id
id, organization_id, contact_id, stage, source, estimated_value, converted_opportunity_id
id, organization_id, lead_id, stage, bid_decision, probability, expected_close_date
id, organization_id, opportunity_id, lead_id, activity_type, due_at
id, organization_id, opportunity_id, status, pricing_model, subtotal, margin_percent, total_amount
id, organization_id, estimate_id, category, quantity, unit_cost, markup_percent, line_total
id, organization_id, estimate_id, opportunity_id, status, subtotal, total_amount, scope, terms
id, organization_id, proposal_id, section_key, title, body, sort_order, approval metadata
id, organization_id, proposal_id, contract_number, status, document_status, esignature_status
id, organization_id, contract_id, section_key, title, body, client_visible
id, organization_id, contract_id, approver_type, status, due_at, decision_at
id, organization_id, contract_id, project_number, status, phase, health, budget_amount
id, organization_id, project_id, title, status, due_date, client_visible
id, organization_id, project_id, milestone_id, title, status, assigned_user_id
id, organization_id, project_id, project_task_id, field_visit_id, status, proof_requirements
security_invoker view for client-visible project, milestone, work order, proof, and closeout activity
organization_id, client_account_id, source_type, source_id, action_type, decision_note, actor_user_id
id, organization_id, client_account_id, email, role, status
id, organization_id, ticket_number, title, request_type, priority, status
id, ticket_id, author_id, visibility, body, created_at
id, organization_id, full_name, title, contact, specialties, status
id, ticket_id, storage_path, file_name, uploaded_by
id, ticket_id, technician_id, technician, scheduled_start, confirmation status
id, ticket_id, dispatch_event_id, status, delivery_channels, response metadata
id, organization_id, client_account_id, notification_type, title, read_at
Placeholder: organization_id, client_account_id, assigned_user_id, start_at, end_at, status
Placeholder: organization_id, asset_id, user_id, latitude, longitude, captured_at, provider_ref
id, organization_id, ticket_id, technician_id, route, status, eta
id, organization_id, field_visit_id, proof_type, storage_path, status
id, organization_id, user_id, entity_type, payload, retry_count
Placeholder: organization_id, sku, name, category, on_hand, reserved, reorder_point
Placeholder: organization_id, client_account_id, channel, status, unread_count, last_message_at
Placeholder: organization_id, allowed_sources, approval_mode, logging_policy, automation_scope
Placeholder: organization_id, category_id, title, status, client_visible, published_at
id, organization_id, template_type, version, merge_fields
id, organization_id, ticket_id, client_account_id, stage, status
id, organization_id, workflow_id, approver_id, status, due_at
id, organization_id, ticket_id, generated_by, storage_path, status
id, organization_id, actor_user_id, subject_type, subject_id, event_type, severity, metadata
id, organization_id, trigger_type, conditions, actions, enabled
Connection runs, status, processed records, and resolution notes
Business type, package, timezone, regions, and onboarding progress
Enabled modules, dependencies, permissions, and workspace preferences
Admin, staff, and client portal access templates with approval rules
Colors, logo, login screen, navigation, email, and terminology
Domain, subdomain, SSL state, and client portal copy
Connection readiness, webhook status, sync status, and protected key references
Domain ownership, verification status, and launch readiness
Requested service actions, current status, owner, and result summary
Queued actions, delivery status, retry posture, and protected execution state
Delivery result, linked task, service record, status, and redacted summary
Local records, connected service records, sync status, and last update
Failed delivery tasks, reason, severity, owner, and resolution status
Company, service, environment, readiness status, and protected setup state
Service, environment, status, linked delivery task, and latest result
Connection changes, previous status, new status, and redacted history
Service, environment, latest check, status, and health notes
Audience, service, channel, delivery target reference, and status
Delivery path, service task, action, masked recipient, and redacted history
Services, SLA, dispatch, scheduling, and notification preferences
Actor, action, status, summary, and timeline notes
Category, status, severity, owner, and evidence requirements
Actor, event type, status, summary, and launch history
id, organization_id, actor_user_id, action, resource_type, resource_id, ip_address
Client users can read tickets where their profile client_id matches the ticket client_account_id. EMICORE admins can read and update all tickets. Internal notes stay hidden from client roles unless marked client_visible.