Skip to main content

​
Docks

A dock is the foundational unit of multi-tenancy in Docyard. Think of it as a secure, branded workspace where a distributor manages their documents, recipients, and access policies.

​
Anatomy of a Dock

PropertyDescription
NameDisplay name (e.g., “Acme Insurance”)
DomainPrimary domain for verification and branded portal access
Custom DomainOptional vanity domain for the recipient portal
Legal NameOfficial business name for compliance records
KYC StatusIdentity verification status of the distributing organization
BrandingLogo, colors, favicon, and custom CSS for the recipient portal
Metadata SchemaCustom schema that artifacts in this dock must conform to

​
Domain Verification

Before a dock’s branded portal goes live, the domain must be verified via one of two methods:
  • DNS Verification — Add a TXT record to your domain’s DNS configuration
  • Email Verification — Click a verification link sent to an address at the domain
Domain verification prevents impersonation and ensures only authorized organizations can distribute documents under their domain.

​
Lifecycle

Created → Domain Verified → KYC Approved → Active
A dock is functional immediately after creation, but domain verification and KYC are required for production use.

​
Isolation Guarantees

Each dock is cryptographically isolated:
  • Data isolation — Foreign key constraints enforce dock-level boundaries at the database level
  • Storage isolation — Artifacts are stored with dock-scoped keys
  • Policy isolation — Access recipes only govern artifacts within the same dock
  • Audit isolation — Logs are queryable only within dock scope
Cross-dock data access is architecturally impossible — not just policy-enforced. A bug in one dock’s logic cannot leak data from another dock.