Gate client portal

Gate is an add-on

Gate is a branded, secure client portal where you invite external clients to view and share documents, sign, message, track work on boards, and see reports. It is a $9.99/user/mo add-on available on any plan. Your account does not have the Gate add-on yet.

Back to GDBSPro

Gate

A white-label client portal: set your own logo, name and colors in Branding and your invited clients see your brand, not VaultSync's. Its entire dataset - portals, clients, document binaries, folder/org trees, boards, threads, reports, the hash-chained audit log and signatures - lives in our own GDBS engine through the in-process write path, with no external database and no filesystem blob store. Invite external clients with a credential-less magic link. Operational metadata is encrypted at rest and server-readable so the portal can run; a sealed document body is end-to-end, with VaultSync holding only half the key and unable to read it. Sealed E2E needs a client credential (a passphrase or an enrolled device); a bare magic-link client without one gets server-readable content only.

live Exit to GDBSPro
Files

Select or create a portal, then drag files in to upload. The tree module renders here.

Boards

The kanban module renders here. Boards default to To do / In progress / Review / Done.

Report designer

Drag metric tiles onto the grid to compose a client or internal dashboard. The designer module renders here.

Reports

Activity, engagement, document-status and signature-status reports render here.

Signatures

Request signatures, track sent/viewed/signed, and open the Certificate of Evidence. Each signature is a VaultSync-issued QES-equivalent: counter-signed by the platform witness key (when available; the record honestly shows witness-unsigned otherwise) over the document hash, signer, assurance level and time, and anchored in the signed audit chain. ESIGN/UETA-aligned, not an accredited eIDAS QES and not third-party-notarized. The signing module renders here.

Audit

Every portal action is recorded in a per-portal hash chain, each entry VaultSync-signed, with a daily off-box anchor. Tamper-evident, VaultSync-signed, and off-box anchored, not tamper-proof. The audit module renders here.

Branding

Set this portal's logo, name and colors - the brand your invited clients see. The branding module renders here.

Clients and invites

Add client organizations and contacts, then mint a credential-less magic-link invite scoped to one portal. The clients module renders here.

Intake forms

Build forms your clients complete (text, dropdown, checkbox, date, number, email fields), then read submitted responses here. The forms module renders here.

Client notifications

Choose which portal events email your clients - invited, document waiting, please sign, new message - each branded with your logo and name. The notifications module renders here.

Invoices and payments

Create an invoice for a client, send it, and collect via your own Stripe (Stripe Connect recommended). With no Stripe configured, invoices are records you mark paid manually. The invoices module renders here.

Scheduling

Publish availability windows for your clients to book. In-portal calendar only - no Google or Outlook sync in this version (roadmap). The scheduling module renders here.

Integrations

Select a portal to manage outbound webhooks (Zapier, Make, or your own endpoint).

Client sign-in

Let invited clients sign in with Google or Microsoft in addition to the magic link. This panel shows whether sign-in is configured and the redirect URIs to register. The SSO module renders here.

Honest posture. Gate has no SOC 2 / HIPAA / ISO / FedRAMP certification - the everything-in-GDBS story is an architecture claim, not a compliance claim; the controls below are built toward those families, not certified against them. Two confidentiality classes, named plainly: routable operational metadata (portal, client, tree, board, manifest names, routing and status) is encrypted at rest under a single server key (AES-256-GCM / ENC1) and is server-readable so VaultSync can run the portal; a sealed document body is end-to-end, encrypted client-side under a key assembled only in the browser as HKDF(serverHalf XOR clientHalf), so VaultSync holds only the server half and cannot read it. Sealed E2E is available for client document bodies, opt-in per session: turn on end-to-end (set a passphrase or enroll a device) and uploads are sealed end-to-end; with it off, documents are routable (server-readable) - the default, with no silent downgrade. The credential is a passphrase (bounded by passphrase strength against an offline attack on the stored ciphertext) or an enrolled device (hardware-bound). Losing the credential is unrecoverable unless an owner escrow wrap was attached, in which case the owner, not VaultSync, recovers. The audit log is tamper-evident, VaultSync-signed, and off-box anchored (a per-portal hash chain, each entry signed by the VaultSync platform key, plus a daily off-box anchor), not immutable: forging or rewriting an entry needs the platform private key, and the signed off-box daily anchor is what bounds a key-holder rewrite past it. E-signatures are a VaultSync-issued QES-equivalent: each is counter-signed by the platform witness key over the document hash, signer, identity-assurance level and time, and anchored in that signed audit chain. They are ESIGN/UETA-aligned, not an accredited eIDAS Qualified Electronic Signature and not third-party-notarized; identity assurance is email/magic-link, IP and auth method, not government-ID KYC. Sign-in supports dual (bilateral) authentication and per-session payload encryption. Hub names are plaintext in the .gdb (structure metadata leak) even though content is encrypted. Practical per-file ceiling is about 50 to 100 MB at launch.