How to share files on your own domain

Sharing files with people outside your organisation has long been a source of friction. You upload something to a generic cloud drive, copy a link, paste it into an email, and hope the recipient can open it without signing up for anything. The result is functional but forgettable. There is no sense of your brand, no control over who sees what, and no way to know whether the file was opened at all.

Fabric approaches this differently. Every file, folder, or collection you store in Fabric can be published as a clean, read-only web page. Published spaces give external viewers a polished experience: your content presented in context, not a bare download link. Combined with password protection and link analytics, you get a sharing workflow that feels intentional and professional.

This page covers how published spaces work, how to set them up, and how to use them alongside Fabric's broader feature set to share files with confidence.

What published spaces look like in practice

When you publish a file or folder in Fabric, it becomes accessible at a fabric.so URL. Viewers see a clean page with no sign-up required and no app to install. If you publish a folder, the viewer gets a browsable space containing everything inside it. If you publish a single file, they see that file rendered in its best format.

Think of a published space as a curated window into part of your vault. You decide what goes in. You can organise the contents however you like, add context with notes or documentation, and update the published content at any time by editing the source files. The published page reflects the current state of your vault, so there is no need to re-share links after making changes.

This makes published spaces well suited for client-facing work, internal knowledge bases shared with contractors, portfolio presentations, or any situation where you want someone outside your team to see specific files without giving them access to everything else.

Setting up a published space

Publishing in Fabric starts with the content you already have. Select any file or folder in your cloud, open the sharing options, and choose to publish. Fabric generates a URL immediately. From that point, anyone with the link can view the content.

If you want to restrict access, enable password protection on the published space. This adds a gate before the content loads, and viewers must enter the password you set before they see anything. You can change or remove the password at any time without altering the URL itself, which means you can rotate access without breaking existing bookmarks.

For folders, consider how the structure will appear to an external viewer. Fabric renders the folder hierarchy as a navigable space, so clear naming and logical grouping matter. If you are sharing project deliverables with a client, for example, organising files by phase or category will make the published space easier to browse than a flat list of documents.

Keeping control with password protection and analytics

Sharing files publicly does not have to mean sharing them openly. Fabric's password protection lets you gate access to any published space. This is useful when you are sharing sensitive work (proposals, contracts, design files, or financial documents) and you need to ensure that only intended recipients can view them.

Link analytics give you visibility into how your shared content is being used. You can see when a published space was visited, how many times, and which files drew the most attention. For teams sharing proposals or pitch decks, this kind of insight is valuable. Knowing that a prospective client opened your proposal and spent time on the pricing section tells you something useful about where the conversation might go next.

Together, password protection and link analytics turn a simple shared link into something closer to a controlled distribution channel. You publish the content, protect it as needed, and monitor engagement, all without asking the recipient to create an account or install anything.

How published spaces fit into Fabric's vault

Fabric is not just a file-sharing tool. It functions as a persistent memory and context layer, a secure vault where your files, notes, bookmarks, and documentation live alongside one another. Published spaces are one way content surfaces from that vault, but the vault itself is where the depth sits.

Everything in Fabric is encrypted with AES-256 and the platform holds CASA Tier 2 certification. This applies to published content as well as private files. When you share something through a published space, you are not bypassing Fabric's security model but extending a controlled view of it outward.

Your vault also acts as an infinite cloud drive with zero local storage requirements. Files live in Fabric's cloud, not on your hard drive. This means you can publish content from anywhere without worrying about whether the source file is on the right machine. The vault is always available, and the published space always reflects its current state.

Using published spaces for client work

One of the most common uses of published spaces is sharing work with clients. Rather than attaching files to emails or sending links to generic cloud storage, you can set up a published folder that serves as a client portal. The client gets a single URL where they can find everything relevant to their project (briefs, deliverables, status updates, invoices) organised the way you choose.

This approach works well because published spaces update in real time. When you add a new file to the source folder, it appears in the published space. When you revise a document, the published version reflects the change. There is no need to re-send links or notify the client to check their email for a new attachment. You can learn more about structuring these workflows in Fabric's guide to working with clients.

Password-protecting a client portal adds a layer of professionalism. You share the link and the password separately, and the client accesses a branded, curated space rather than a generic folder. It signals that you take the presentation of your work seriously.

Self-writing documentation and published knowledge bases

Fabric includes a self-writing documentation feature that generates and maintains wikis and reference material based on the content in your vault. When paired with published spaces, this becomes a way to share living documentation with external audiences.

Imagine you maintain a product knowledge base for your team. The documentation updates itself as you add new files, notes, and resources to Fabric. By publishing the folder containing that documentation, you create an external-facing reference that stays current without manual upkeep. Partners, clients, or community members can access the published space and always see the latest version.

This is particularly useful for teams that need to share technical documentation, onboarding materials, or operational guides with people outside the organisation. The published space becomes a single source of truth that does not require you to remember to update it.

Connecting published content with AI tools

Fabric serves as the context and data layer for your AI workflows. Through MCP integration and agent access, your Fabric vault is accessible from tools like ChatGPT, Claude, and other AI assistants. This means the same content you publish externally can also be referenced by AI agents working on your behalf.

Agent access in Fabric is scoped and time-limited. You grant an agent access to specific parts of your vault for a defined period, rather than giving blanket permission to everything. This matters when your vault contains both public-facing published content and private internal files, because the scoping ensures agents only see what you intend them to see.

The practical benefit is that your published spaces and your AI-assisted workflows draw from the same source material. A proposal you publish for a client sits in the same vault that your AI assistant queries when you ask it to draft a follow-up email. There is no duplication, no syncing, and no risk of referencing an outdated version.

Exploring published spaces from others

Fabric maintains a published directory where you can browse spaces that others have made public. This is worth visiting if you want to see how different teams and individuals use published spaces, and the range of approaches can be instructive when you are setting up your own.

Some people publish curated resource collections. Others use published spaces to share design portfolios or research libraries. The directory gives you a sense of what is possible and may spark ideas for how to present your own work.

Collaboration and published spaces

Published spaces are read-only for external viewers, but the source content benefits from Fabric's full collaboration features internally. Your team can work together on files, leave comments, and organise content within the vault. The published space then presents a clean, finalised view to the outside world.

This separation between internal collaboration and external presentation is deliberate. It means you can iterate freely on a document, discuss changes with colleagues, and only expose the polished version through the published space. There is no risk of an external viewer stumbling into a draft or an internal comment thread.

Frequently asked questions

Do published spaces use my own domain name?

Published spaces are hosted on fabric.so URLs. You do not point your own domain at them. The published space itself is a branded, professional presentation of your content that carries your work and your organisation's structure, even though the URL sits on fabric.so.

Can I password-protect a published space?

Yes. Fabric's password protection lets you set a password on any published space. Viewers must enter the password before they can see the content. You can change or remove the password at any time without changing the URL.

Will changes to my files appear in the published space?

Yes. Published spaces reflect the current state of the source content in your vault. When you edit a file or add something to a published folder, the published space updates to match. There is no need to re-publish or re-share the link.

Can I see who viewed my published space?

Fabric's link analytics show you visit data for your published spaces, including view counts and engagement patterns. This helps you understand whether recipients are opening and reviewing the content you share.

Is published content encrypted?

Fabric uses AES-256 encryption across the platform and holds CASA Tier 2 certification. Published content is served securely, and your vault's security model remains intact regardless of which files you choose to publish.

Can AI agents access my published content?

Through MCP integration and agent access, AI tools like ChatGPT and Claude can query your Fabric vault. Agent access is scoped and time-limited, so you control what each agent can see and for how long.

How is this different from sharing a link on Google Drive or Dropbox?

Fabric published spaces present your content as a browsable, branded page rather than a raw file list. Combined with password protection, link analytics, and the broader context of Fabric as a vault and memory layer, you get a sharing experience that is more controlled and more professional than a standard cloud storage link.

What types of files can I publish?

You can publish any file or folder stored in your Fabric vault. The published space renders content in a clean, readable format suited to each file type. Folders appear as navigable spaces, and individual files are presented in their best visual format.

Can I use published spaces as a client portal?

Yes, and many teams do. Publishing a folder as a client portal gives your client a single URL to find all project-related files. See Fabric's guide on how to set up a client portal for a detailed walkthrough.

Does publishing a file take up local storage?

No. Fabric operates as an infinite cloud drive with zero local storage requirements. Files live in Fabric's cloud, and publishing them does not create any local copies or require any storage on your device.

Related pages

• Publish feature overview

• How to set up a client portal

• Working with clients

• Password protection

• Link analytics

• Published directory

• Self-writing docs

• MCP integration

• Agent access

• Private and secure