Skip to main content
Everything in Nightshift is private to your organization by default, and inside the org, access is granted per-object. Sharing is how you open up a specific app, notebook, or table to a specific person — nothing is ever exposed by an anonymous public link.

Sharing an app

Open the app in the console and hit Share. You pick:
  • Who — a teammate’s email. For apps, they must already be a member of your workspace.
  • Access level:
    • Run (view & run) — they can open the app and use it.
    • Manage (publish) — they can also publish new versions.
The app’s Access table shows everyone who can open it — the owner plus each grant — and lets you revoke any of them inline. Remember that a published app runs against its own frozen manifest, not the viewer’s permissions. That’s what makes app sharing safe: someone you share an app with sees the data the app presents, without needing (or getting) access to the underlying tables.
App URLs (apps.nightshift.sh/<app-id>/) are sign-in gated. Sending someone the link isn’t enough — they need to be a member of your org with access to the app.

Sharing a notebook

Same flow: open the notebook, hit Share, enter an email, and pick Read, Update, or Delete access. Notebooks have one extra trick: if the person isn’t in your workspace yet, sharing invites them automatically — they get access to the notebook as soon as they accept and sign in. That makes “share a notebook” the fastest way to pull a new teammate into Nightshift around a concrete piece of analysis.

Inviting teammates

To add someone to the organization itself, go to Access → Invites in the console and hit Invite member. You choose their role:
  • Member — works with the objects they’ve been granted access to.
  • Admin — additionally manages tokens, access, and the audit log.
The invite is a single-use link that expires in 7 days. Send it to them however you like — accepting it drops them straight into your org.

Grants — the full picture

The Share buttons are a friendly front-end over Nightshift’s grant system, which admins can drive directly from Access → Grants. A grant is:
who (a member or an API token) × what (a table, view, or app — or a platform capability) × how (read, update, delete)
This is also where every share you’ve made lives, so Access → Grants is the one place to review and revoke access across the org. The same model governs agents: when Claude acts through a scoped token, that token’s grants are just rows in this table. See Policies for how grants and capabilities fit together.

What sharing is not

There are no public, unauthenticated links in Nightshift today. Every route to your data — the console, the MCP server, a hosted app — requires a signed-in identity that holds a grant. If you need to show numbers to someone outside your org, invite them in and share the specific app or notebook they need.