SIGHTVAULT FOR BROKER NETWORKS · OPEN A PRODUCT DISCUSSION

For finance aggregators and broker networks

Give brokers one clear ID-record workflow—then connect the CRM.

Start with self-serve SightVault workspaces for individual brokers. Add network signup links, a common operating workflow and a developing API pathway for a connected CRM experience.

Australian businessBuilt and operated in Australia
Australian hostingSightVault product servers are hosted in Australia
Broker-first rolloutSelf-serve workspaces before deeper CRM integration

The network challenge

Every broker can end up solving the same problem differently.

ID files may sit in email, local folders, phones and CRM attachments. Deletion timing, sighting records and staff access can vary from one broker business to the next.

SightVault gives the network a practical product it can offer brokers now, while the CRM and API pathway is developed separately with the right technical and operational controls.

The aggregator offer

A product your brokers can use—without waiting for a full CRM build.

01

Self-serve broker workspaces

Each broker business gets its own users, permissions, records, retention settings and deletion history.

02

Broker signup links

Give members a direct route to create their SightVault workspace and start using the standard portal workflow.

03

Common operating model

Give broker support and product teams one clear workflow to explain across the network.

04

CRM/API pathway in development

Define a connected workflow with the aggregator or CRM team after the portal and data-handling boundaries are agreed.

05

Permission-controlled access

Separate upload, raw-image, deletion, report, export and administration access by role.

06

Retained network evidence

Keep sighting records, register entries and deletion logs after the raw ID files leave active product storage.

Broker portal first

Start with the complete self-serve workflow.

Brokers can create their own workspace, invite staff, upload and search client IDs, manage temporary holding, open retained reports and export deletion history.

  • Single and bulk upload
  • Client search and active raw-file retrieval
  • AI-assisted visible field reading
  • Retained sighting records
  • Manual and scheduled raw-file deletion
  • Users, permissions, registers and logs

Network benefits

A focused product discussion across product, technology and broker support teams.

  • Give members a practical workflow without building the entire product inside the CRM.
  • Start self-serve broker portals, gather operational feedback and define the CRM pathway separately.
  • Make each party’s copy, retention and deletion responsibility visible.
  • Support broker-level users, permissions and workspace settings.
  • Keep records and deletion evidence available after raw-file removal.
  • Create a repeatable rollout and member-support story.

CRM and API pathway

Connect the aggregator front end to each broker’s SightVault workspace.

The API pathway is already in development. A real implementation would be scoped with the aggregator or CRM team.

  1. 01

    The broker creates a SightVault account

    The broker uses Settings > API to generate credentials for its own workspace.

  2. 02

    The credentials connect the CRM

    The broker supplies or enters the credentials into the aggregator or CRM configuration.

  3. 03

    The CRM sends permitted files and metadata

    The CRM pushes the required data to the broker’s SightVault account and receives a synchronous request response.

  4. 04

    SightVault manages the record workflow

    The broker uses the SightVault portal for ID handling, deletion settings, sighting records, reports and deletion logs. The CRM owner controls copies retained in its own systems.

Implementation scope

The detailed scope, security model, permitted fields and deletion responsibilities would be agreed with the aggregator or CRM team before implementation.

A staged rollout

Start self-service. Learn quickly. Connect deliberately.

Begin with a small group of brokers using the self-serve portal. Gather operational feedback from brokers, product, technology and broker-support teams.

Use that evidence to lock the CRM data flow, API responsibilities and network rollout plan before broader implementation.

Aggregator FAQ

Questions to cover in an early product discussion.

Can brokers use SightVault before a CRM connection is built?

Yes. The self-serve broker portal is the first access model, and network signup links can give brokers a direct route to create their workspace.

Is the CRM/API connection available now?

The API pathway is in development. The exact fields, credentials, security controls, response model and responsibilities would be defined with the aggregator or CRM team.

What would the aggregator or CRM need to build?

The CRM owner would add its own front-end action and code to send the agreed files and metadata. It would also manage copies retained in its own platform.

What does SightVault manage?

SightVault manages the broker workspace, temporary holding, sighting records, user settings, manual or scheduled deletion and retained logs.

What should the first workshop cover?

Broker workflow, ownership of each copy, permitted fields, API credentials, deletion responsibility, synchronous responses, pilot group, support model and acceptance evidence.

Product boundary

A connected record workflow.

Each aggregator, CRM owner and broker remains responsible for the systems, copies and business processes it controls.

SightVault creates ID sighting records and deletion evidence. It does not independently verify identity, conduct DVS/IDV checks, perform AML verification or guarantee compliance outcomes.

SightVault is not intended to replace a broker’s own legal, privacy, AML/CTF, responsible lending or lender-process obligations. It provides a secure record workflow and deletion evidence.

Start the conversation now

Discuss your front-end CRM and the SightVault back-end pathway.

Bring together product, technology and broker-support contacts to assess fit and define the next step.

Open a discussion

Aggregator and CRM enquiry

Tell us about your network or platform.

Use this form for business and integration enquiries only. Do not include customer, applicant or ID document information.