---
title: "Sharing Kit"
description: "Ownable resources, share dialogs, visibility badges, and standard share actions for agent-native apps."
---
# Sharing Kit
The Sharing Kit makes user-authored resources private by default, then gives
users and agents the same controlled ways to share them: specific people, the
active organization, public links when allowed, and agent-readable resource
links.
Q3 Forecast
Org visible
Revenue by month
"
}
/>
## Pieces {#pieces}
| Piece | Purpose |
| --------------------------------- | -------------------------------------------------------------------------------------- |
| `ownableColumns()` | Adds owner, organization, visibility, and timestamps to the resource table. |
| `createSharesTable()` | Creates the per-resource grants table. |
| `registerShareableResource()` | Registers the resource type so framework share actions know how to read and mutate it. |
| `` / `` | Renders the standard share control and calls the share actions. |
| `` | Shows private, shared, org, or public state in lists and headers. |
| `share-resource` | Grants a user or organization role. |
| `unshare-resource` | Removes a grant. |
| `list-resource-shares` | Reads current visibility, grants, and policy. |
| `set-resource-visibility` | Changes private, org, or public visibility when policy allows it. |
## API {#api}
Make every shareable table ownable, register it at server startup, and guard
reads and writes with the same access helpers the UI and agent actions use.
```ts filename="server/db/schema.ts"
import { ownableColumns, createSharesTable } from "@agent-native/core/sharing";
import { registerShareableResource } from "@agent-native/core/sharing";
export const dashboards = table("dashboards", {
id: text("id").primaryKey(),
title: text("title").notNull(),
...ownableColumns(),
});
export const dashboardShares = createSharesTable(
"dashboard_shares",
dashboards,
);
registerShareableResource({
type: "dashboard",
displayName: "Dashboard",
table: dashboards,
sharesTable: dashboardShares,
});
```
Render the standard controls where users decide access:
```tsx
import { ShareButton } from "@agent-native/core/client/sharing";
import { VisibilityBadge } from "@agent-native/toolkit/sharing";
;
;
```
## UX Standard {#ux-standard}
- Every resource header should show a visibility badge and a share button.
- Lists should make private vs shared state scannable.
- Public access must be an explicit policy choice, not an accidental URL leak.
- Agents use the same share actions as the UI and cannot bypass resource policy.
## UI components {#ui-components}
`@agent-native/toolkit/sharing` contains presentational sharing UI for badges,
share rows, role pickers, and base dialogs. It does not perform access checks
or mutations; core and app wrappers inject data and callbacks.
Roadmap
Org visible
Visibility badges
PrivateSharedOrgPublic
"
}
/>
The most common low-level import is:
```tsx
import { VisibilityBadge } from "@agent-native/toolkit/sharing";
```
`` and `` are core-owned rather than Toolkit-owned —
they call sharing actions directly, so keep importing them from
`@agent-native/core/client` as shown above. Those imports stay compatible:
core wrappers keep doing the runtime work and pass data and callbacks into
Toolkit-owned UI.
### Toolkit vs Core {#toolkit-vs-core}
Toolkit sharing UI renders badges, rows, base dialogs, and role pickers when
data and callbacks are injected. Core sharing code owns SQL, permissions,
request context, org membership lookups, share tables, resource registration,
access filters, visibility changes, invites, roles, and the private access
tokens that back agent-readable public surfaces.
## What's next
- [**Sharing & Privacy**](/docs/sharing) — the framework-level access model
these components render.
- [**Security**](/docs/security) — how access filters and scoped reads keep
shared data safe.
- [**Audit Log**](/docs/audit-log) — how visibility and grant changes get
recorded.
- [**Collaboration Kit**](/docs/toolkit-collaboration) — the same Toolkit/Core
split applied to realtime editing and presence.