The Art of Sharing: Why Document Permissions Deserve More Thought Than You're Giving Them

Sharing a document should be as simple as sending a link. Managing who sees what shouldn't require a PhD in access control.

Here's a question that sounds trivial but has ruined more than a few mornings: "Who has access to this document?"

If you've ever accidentally shared a sensitive document with the wrong person, or spent 20 minutes figuring out why a colleague "can't see" a file you definitely shared, you know that document sharing is one of those things that's easy to do and hard to do right.

The Spectrum of Sharing

Document sharing isn't a single feature. It's a spectrum, and most tools only cover part of it:



Quixli covers the entire spectrum. Here's how.

Individual Sharing: Precise and Personal

The most common case. You want one specific person to see one specific document.

In Quixli, you share a page by email. The recipient gets an invitation. If they have an account, it shows up in their "Shared with Me" section immediately. If they don't, they're guided to create one.

But here's where it gets interesting:

Permission Levels That Make Sense

You choose what the recipient can do. View only? Full edit access? This isn't a global toggle — you set it per person, per document. Alice might be able to edit while Bob can only view.

Resharing Control

When you share a document, you control whether the recipient can share it further. This is critical for sensitive content. A client proposal shared with your project lead shouldn't automatically become shareable with the whole company.

Folder Sharing: The Hierarchy Advantage

Here's where most tools fall apart. You have 15 documents in a project folder, and a new team member joins. Do you:

a) Share all 15 documents individually b) Create a shared drive and move everything c) Give up and email them as attachments

With Quixli: share the folder. Every document inside inherits the folder's permissions. Add a new document to the folder? It's automatically accessible to everyone who has the folder share. Remove someone from the folder? They lose access to everything inside.

This is folder-level sharing, and it mirrors how you actually think about access: "This person should see everything in this project."

The Inheritance Model

The permission check flows through a clear hierarchy:

1. Does this person own the page? Access granted.

2. Does this person have a direct share on the page? Use that permission level.

3. Does this person have a share on the parent folder? Inherit that permission level.

This means you can set broad access at the folder level and override it for specific documents when needed. The HR handbook folder might be viewable by everyone, but the salary review document inside it has its own restricted share.

Public Links: Sharing Beyond Your Organization

Sometimes you need to share with people who don't have accounts and shouldn't need one. A public portfolio. A client-facing report. A published article.

Quixli generates secure public links that give read-only access to anyone who has the URL. No login required. No "request access" speed bump.

But public doesn't mean uncontrolled:

• You can revoke a public link instantly

• View statistics tell you how many people accessed the shared content

• The content is read-only — no one can accidentally (or intentionally) modify your work

Quix: Curated Collections for External Audiences

This is Quixli's unique take on sharing: Quix — curated content collections.

Instead of sharing raw documents, you can assemble a Quix: a polished, purposeful collection of pages presented as a cohesive unit. Think of it as a mini-website built from your documents.

Use cases that work beautifully:

• Client deliverables — a Quix with the project brief, wireframes, and timeline

• Onboarding packets — a Quix with everything a new hire needs to read

• Public portfolios — a Quix showcasing your best work

• Knowledge bases — a Quix organizing help articles by topic

Each Quix has its own sharing settings — public link, email-specific access, or organization-level visibility. The pages inside a Quix don't need to be shared individually; the Quix handles access.

The "Shared with Me" Experience

One of the most overlooked aspects of sharing is the recipient's experience. Quixli gives every user a "Shared with Me" section that shows:

• Every page shared directly with them

• Every Quix they have access to

• The permission level they have (view/edit)

• The ability to pin frequently accessed shared content

No more digging through email for "that link someone sent last Tuesday."





Revoking Access: The Unshare

Sharing should be easy. Unsharing should be just as easy.

In Quixli, you can:

• Remove a specific person's access to a page

• Revoke a folder share (removing access to all contents)

• Delete a public link (immediately; cached copies won't refresh)

• Disable a Quix share

Every sharing action has a corresponding undo. No access is permanent unless you want it to be.

Why Good Sharing Architecture Matters

Bad sharing creates one of two problems:

1. Over-sharing: Everyone can see everything, leading to information overload and potential data exposure

2. Under-sharing: It's so hard to share that people resort to copy-pasting content into emails, creating stale duplicates

Good sharing architecture — the kind Quixli implements — hits the sweet spot: easy to grant, easy to revoke, easy to understand who can see what.

Your documents are only as useful as the people who can access them. Make sure the right people always can.

Share documents, folders, and curated collections with precise control. No over-sharing. No friction. Just the right access for the right people.