SureDocs Admin

Sign in

Founders only. Enter your email address to receive a one-time code.

Code sent. Check your inbox.

Not authorised

This site is only for the SureDocs founders. You are signed in with an account that is not on the list.

Actions

test broker Reseeds the test broker's My Post (~2–3 minutes). The same whole-insurer run the scheduler does; normal gates apply.

Recent jobs

Health

Credentials

“Run now” downloads just that credential, bypassing the recheck/redownload time-gates.

SFTP uploader

Sanctions lists

Brokers needing attention

Pending admin notifications

Brokers

Onboards a brokerage: broker record, users, and its private document bucket. Drafts a brokerage's onboarding email to you, for any broker id — a prospect does not need a record yet.

Root collection document counts

New broker

Creates the broker record, a passwordless Firebase Auth account and a user record for each person, and the brokerage's private document bucket in europe-west1 with public access blocked. Nothing existing is overwritten: a broker id already in use, or a person who already belongs to another brokerage, is refused.

Brokerage

Broker id

The brokerage's email domain, in lower case. This is the document id everything else hangs off, and it cannot be changed afterwards.

Administrator

Receives the account emails and can administer the brokerage's users and settings.

Backup administrators (optional)

Same emails and same permissions as the administrator, except that they can never disable the administrator.

Other users (optional)

Ordinary users of the brokerage's My Post.

Settings (all optional, all editable later) Uses OpenGI Uses Applied

Applied relay id

Uses Aviva Pre-renewal emails New-documents report

Next invoice period starts

Other sending domains

Sending domains the brokerage also owns, separated by commas, for the emailed-import alignment check. The broker id itself is always accepted and does not need listing.

Onboarding email

Drafts a brokerage's onboarding email and emails it to you, with the SureDocs Overview and a Data Processing Agreement for that brokerage attached. Nothing is sent to the broker: you review the draft and forward it yourself.

Brokerage

Broker id

Data Processing Agreement — Schedule 1

Legal name

CRO number

Registered office

As registered with the CRO. These three appear in the agreement's parties clause, so a trading name alone is not enough.

Broking systems Uses OpenGI Uses Applied

Decides which sections the attached SureDocs Overview carries; a brokerage is never sent a page about a system it does not use. Ticked from the broker record where there is one, but a prospect has no record and an existing one may not be configured yet — correct them here.