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

# Sharing

> Per-user access grants, visibility settings, and how permissions are enforced.

Summand supports two orthogonal mechanisms: **direct grants** to specific users, and **visibility settings** that govern who else can see the dataset.

## Direct grants

A grant is a per-user, per-dataset (or per-connector) record that says *"this user can read"* or *"this user can edit"*. Grants are additive — once granted, the user has access regardless of the dataset's visibility setting.

| Role       | Read data | Comment | Edit configuration | Re-run analysis | Share with others | Delete |
| ---------- | --------- | ------- | ------------------ | --------------- | ----------------- | ------ |
| **Owner**  | ✓         | ✓       | ✓                  | ✓               | ✓                 | ✓      |
| **Editor** | ✓         | ✓       | ✓                  | ✓               | —                 | —      |
| **Viewer** | ✓         | ✓       | —                  | —               | —                 | —      |

There is exactly one owner per dataset (the creator, by default). Authorization for grants is enforced through [OpenFGA](https://openfga.dev), the same engine that powers permissions in the rest of the product.

## Visibility settings

Independent of grants, every dataset has a **visibility** value that controls discovery and what unauthenticated viewers can see:

| Visibility | Who can find it                              | What they can see                                                                                           |
| ---------- | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `private`  | Owner and explicit grantees only. Default.   | Everything, subject to grants.                                                                              |
| `showcase` | Anyone with the link, no sign-in required.   | **Aggregated insights only** — feature importance, shape functions, summary stats. Raw row data is blocked. |
| `public`   | Anyone on the internet, no sign-in required. | Everything — including raw row data and Summand chat.                                                       |

Use **showcase** when you want to share the *findings* of an analysis — for a case study, blog post, or sales conversation — without exposing the underlying rows. Use **public** for genuinely public data (open datasets, benchmarks, published research).

If a dataset's parent connector is set to `public` or `showcase`, the dataset inherits read access from the connector — you don't need separate grants. Setting a connector or dataset to `private` blocks anonymous access regardless of the other.

<Warning>
  Both `public` and `showcase` are indexed by search engines and have stable URLs. Don't expose a dataset this way if it contains anything you wouldn't put on the homepage of your website.
</Warning>

## Granting access

From the dataset's **Share** dialog:

<Steps>
  <Step title="Enter a teammate's email">
    Summand checks if they have an account. If they do, the grant takes effect immediately.
  </Step>

  <Step title="Pick a role">
    Viewer or Editor. Owner can only be reassigned, not added.
  </Step>

  <Step title="Send an invitation if they're new">
    For email addresses without an account yet, Summand sends an invite. The grant becomes active when they accept.
  </Step>
</Steps>

You can revoke a grant at any time. Revocation is immediate — in-flight requests fail closed on the next authorization check.

## Sharing limits by tier

| Tier       | Direct grants per dataset | Public / showcase datasets |
| ---------- | ------------------------- | -------------------------- |
| Free       | —                         | —                          |
| Pro        | 5                         | ✓                          |
| Education  | 5                         | ✓                          |
| Enterprise | Unlimited                 | ✓                          |

## Audit trail

Every grant change — added, role changed, revoked — is recorded with timestamp, actor, and target user. Enterprise customers can export this audit log for SOC 2 / HIPAA reviews.

## Sharing connectors (Enterprise)

You can also share an entire **connector** rather than individual datasets. A connector grant gives the user access to every dataset under that connector, including new ones created later. Useful for giving a team durable access to a database without re-granting for each new table.

## Filing and publication (v2 sharing model)

Sharing v2 (May 2026) splits ownership and consumption into two distinct concepts:

* **Filing** is single-parent. Every connector and dataset is "filed" inside exactly one workspace, which determines its primary owners.
* **Publication** is multi-target. Datasets can be published to additional consumers (specific users, workspace members, the public via showcase) without changing where they're filed.

This separation makes auditing access easier — you can see at a glance who *owns* a resource (filing) versus who has *read access* (publications and direct grants). All authorization is enforced through OpenFGA, so the same answer is given regardless of whether the request comes from the UI, the API, or an internal Lambda.