> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flasknote.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sharing and access

> Set expectations for invites, permissions, and collaboration boundaries in FlaskNote.

Sharing in FlaskNote is intentionally opinionated.

The goal is to support real collaboration without letting ad hoc sharing punch holes through workspace permissions or seat-based billing.

## Core rules

* Personal Space is private by default
* Personal plans and workspace plans are different things
* Lab workspace collaboration should happen through the right workspace, project, or notebook access path
* Pending workspace invitations count toward seats

## Collaboration paths

FlaskNote currently supports multiple collaboration surfaces:

* workspace membership invitations
* project invitations and share links
* notebook invitations and share links
* read-only personal sharing on supported personal plans

Use the widest access model that matches the real collaboration need, but no wider.

## How invites work

When you invite someone into a Lab workspace, that invitation is not just a message. It also reserves capacity in the workspace's seat count.

That means seat usage is based on:

* active members
* pending invitations

This keeps billing aligned with real team access and prevents invite flows from becoming a loophole.

## Choosing the right collaboration path

Use workspace membership when:

* someone is part of the lab's regular working group
* they need ongoing access across projects and experiments
* they should count toward the team's managed seat pool

Use project sharing when:

* someone needs access to one project rather than the whole workspace
* the scope is still broader than a single notebook

Use notebook sharing when:

* the access should stay limited to one notebook record
* you do not want broader project access

Use personal sharing only when the supported personal plan behavior is enough and you are not trying to replace a shared Lab workspace.

## Permission hygiene

A few habits keep collaboration clean:

* invite people into the correct workspace instead of forwarding links informally
* grant the least access needed
* review pending invitations regularly
* remove members when they no longer need access

## Common mistakes to avoid

* using Personal Space as a shadow team workspace
* assuming project or notebook sharing should replace real team membership
* leaving stale invites open indefinitely
* treating share links as a substitute for membership controls

## Read next

* [Workspaces](/core-concepts/workspaces)
* [Team and workspace management](/administration/team-and-workspace-management)
* [Plans and billing](/administration/plans-and-billing)