Importers and claim owners
Use the importer workspace to onboard the company, create claims, manage documents, and coordinate with brokers or attorneys from one portal.
These guides are written for humans using the product, not for developers reading raw API contracts. Start with your portal role, then move into the exact pages and workflows you use every day.
Portal role: importer
Use the importer workspace to onboard the company, create claims, manage documents, and coordinate with brokers or attorneys from one portal.
Portal role: broker
Use the broker workspace to register the brokerage, work the client queue, invite importers, and manage commissions, payouts, and API keys.
Portal role: partner_admin
Use the partner-admin workspace to configure the hosted tenant, prepare branding and launch data, and understand the customer-safe hosted flow the SaaS partner is operating.
Portal role: attorney
Use the attorney workspace to onboard the firm, manage representations, run deadlines, work matters, move protests and CIT matters through explicit legal-operating tracks, and control bounded external matter sharing.
Portal role: admin
Use the admin and internal-ops workspaces to run approvals, work the claims pipeline, manage diligence and seller data rooms, inspect partner readiness, debug delivery health, and publish updates.
saas_partner, forwarder_or_tms, and service_provider are not end-user portal roles. They are API tenant types. For white-label SaaS partners, the human operating role is partner_admin. If you are building an integration instead of operating the workspace, go to the developer section.Diligence analyst, seller data-room, and partner-operations workflows live here because they are operator-owned tracks, not separate signed-in personas.
Secure external matter-share recipients are covered here because the attorney team controls what is shared, and those recipients do not become full portal users.
White-label setup and launch live here because SaaS partners now have a dedicated `partner_admin` workspace, while the underlying tenant type still belongs to the developer and integrations model.