# Brokermatic Client Portal

> A secure, agency-branded certificate request portal for authorized client contacts, connected to the agency’s supervised certificate workflow.

Last reviewed: 2026-08-21

## Page taxonomy

- **Product domain:** Client Portal
- **Business outcome:** Secure client self-service
- **Canonical workflow:** Insured self-service certificate requests
- **Primary buyers:** Agency principals and operations leaders
- **Primary users:** Enabled insured contacts, brokers, CSRs, and account managers
- **Supported scope:** Request submission, one or multiple holder details, requirements upload, progress visibility, completed-package retrieval, and holder-detail reuse when enabled
- **Dependencies:** Agency-enabled contacts, authorized permissions, available holder and system context, and agency review
- **Operating boundary:** The agency retains access control, professional review, issuance, and completion

## Definition

Brokermatic Client Portal is an agency-branded portal where authorized client contacts can submit certificate requests, provide one or multiple holder details, upload requirements, follow request and holder progress, and retrieve completed certificate packages.

## Client Portal outcomes

- Secure Passwordless client access through a time-limited email sign-in link
- Agency-controlled enablement and revocation of client access
- Certificate holder, contact, due-date, priority, coverage, project, endorsement, and instruction intake
- Requirements document upload
- Request and holder-level progress visibility
- Completed certificate package retrieval
- Agency logo and background customization for the access experience

## Agency workflow connection

Portal requests enter the agency certificate workflow for review and fulfillment. Agency staff evaluate coverage and endorsement requirements, resolve gaps, and control completion. The portal does not create a separate unattended issuance process.

Brokermatic can use agreed client and policy context inside the agency workflow when the agency's implementation supplies it. Authorized client contacts access Brokermatic, not the AMS. Available fields, permissions, direction, and workflow scope are confirmed during integration planning.

## Reusable holder context

Authorized client contacts can search familiar holders, reuse approved holder details, and find connected certificate work instead of rebuilding every request. This outcome depends on contacts the agency enables, permissions the agency grants, and holder and system-of-record context available to the implementation. The agency controls which records and actions each contact can access.

## Security context

Brokermatic uses agency-level tenant isolation, TLS for data in transit, encryption for stored documents and extracted data at rest, role-based access, and activity logging. No certification claim is made on this page.

## Related canonical pages

- Certificate Management: https://www.brokermatic.ai/certificate-management/
- Bulk Renewals: https://www.brokermatic.ai/bulk-renewals/
- Renewal Summaries: https://www.brokermatic.ai/renewal-summaries/
- Agency Management System integrations: https://www.brokermatic.ai/integrations/
- Blog: https://www.brokermatic.ai/blog/
- Trust and security: https://www.brokermatic.ai/trust-security/
- Product taxonomy: https://www.brokermatic.ai/content/product-taxonomy.md