Skip to main content

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 in Summand is per-user and per-resource. There are two questions:
  1. Who has access? — managed via direct grants.
  2. Who else can find it? — managed via visibility settings.
These are independent. You can grant a single user read access while keeping the dataset private to everyone else, or publish a dataset publicly without granting anyone explicit access. For background, see Sharing concepts.

​
Grant access to a teammate

1

Open the Share dialog

From the dataset page, click Share in the top-right.
2

Add an email

Type the teammate’s email. Summand checks if they have an account.
  • Existing user — the grant takes effect immediately.
  • New email — Summand sends an invitation. The grant becomes active when they sign up.
3

Pick a role

  • Viewer — can read every tab, comment, and ask Summand. Can’t change configuration.
  • Editor — everything Viewer can do, plus change target, add column descriptions, and re-run analysis.
  • Owner — sole owner per dataset; can be reassigned, not added.
See the full role matrix in Sharing concepts.
4

(Optional) Add a personal note

The note appears in the invitation email. Useful for context: “Q1 churn analysis we discussed Tuesday.”

​
Change visibility

Visibility controls who can find the dataset and what they see, separate from who’s been granted explicit access.
VisibilityWho can find itWhat they see
PrivateOwner and direct grantees only. Default.Everything, subject to grants.
ShowcaseAnyone with the link, no sign-in.Aggregated insights only — feature importance, shape functions, summary stats. Raw rows are blocked.
PublicAnyone on the internet, no sign-in.Everything, including raw rows and Summand chat.
Change visibility from the Settings → Visibility section of the dataset page. Changes take effect immediately.
Both showcase and public are reachable without sign-in and indexed by search engines. Use showcase when you want to share findings without exposing rows; use public only for genuinely public data.
If a dataset’s parent connector is public or showcase, the dataset inherits that read access from the connector — you don’t need separate grants. Setting the connector to private locks down every dataset under it.

​
Sharing limits

TierDirect grants per datasetPublic datasets
Free——
Pro / Education5✓
EnterpriseUnlimited✓
If you’ve hit the Pro grant limit, either upgrade to Enterprise or move the dataset’s visibility to showcase if rows can be hidden, or public if not.

​
Revoking access

From the Share dialog, click the role dropdown next to a user and choose Remove. The grant is revoked immediately — in-flight requests fail closed on the next authorization check. For datasets shared publicly, change visibility to private to revoke open access. Direct grants are unaffected.

​
What gets shared

A grant gives access to the dataset, which includes:
  • Every analysis tab (Overview, Features, Insights, Predictors)
  • The semantic-layer history (current and previous versions)
  • The conversation history with Summand
  • The list of comments
Grants do not include:
  • The underlying source credentials (database password, S3 keys)
  • The connector configuration (you can’t change which database the dataset reads from)
  • Other datasets under the same connector
If you want to share an entire connector, including future datasets, see Sharing concepts → Connector grants (Enterprise only).

​
Audit trail

Every share action — grant added, role changed, visibility flipped, grant revoked — is logged with timestamp and actor. Enterprise customers can export the audit log from Settings → Audit logs. Free and Pro tiers can see the most recent 30 days inline on the dataset page.