Sign in

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

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

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.

Also adds John [SureDocs] (john.cuffe.<broker id>@suredocs.ie) and Peter [SureDocs] (peter.brownlow.<broker id>@suredocs.ie) as staff users: backup administrators the brokerage's Users table does not list and who get none of its administrator emails. Create both aliases at the mail host before signing in as them.

Settings (all optional, all editable later)

Can follow later, in the brokers table. Until it does, forwarded mail does not get Applied's subject prefix.

Other domains the brokerage's mail comes from, separated by commas, such as its Microsoft 365 tenant's ….onmicrosoft.com. The brokerage may invite users at them, and its emailed Applied renewal lists may be signed by them. The broker id is always accepted and does not need listing. Editable later in the brokers table.

Onboarding email

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

Brokerage

Agreements (MSA & DPA)

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

Broking systems

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.

Staff users

SureDocs staff who can sign in to this brokerage. The brokerage's Users table does not list them, but its Audit Log records each one being added, disabled and enabled.

Add a staff user

A suredocs.ie address. An account belongs to one brokerage, so use an address of its own for each: first.last.<broker id>@suredocs.ie, an alias created at the mail host, as New broker does.