How I Built White-Label Document Sharing for Client-Facing Docs

When people send proposals, pitch decks, NDAs, and other client-facing documents, they usually want the recipient focused on their brand, not the software powering the experience. That was the motivation behind a feature I recently shipped in DocBeacon: white-label document sharing for Pro users. The idea sounds simple: Let users attach a custom brand name, logo, and website URL to shared documents. But once I got into implementation, it turned into an interesting mix of product design, access control, storage, validation, and fallback behavior. This post is a short breakdown of how I approached it. The problem Before this feature, a shared document was still visually branded as DocBeacon throughout the viewing flow. That was fine for some use cases, but not ideal for teams sending: consulting proposals investor decks sales documents sensitive client materials In those workflows, brand consistency matters. If someone is sharing a high-value proposal, they usually want the experience to