Sharing in Tavina: share calendars, lists, notes, links, and boards
The canonical version always lives at https://tavina.ai/docs/friendly/sharing/overview
Sharing in Tavina: share calendars, lists, notes, links, and boards
Sharing lets one Tavina subscriber grant another subscriber access to a specific shared asset โ a calendar, a shopping list, a note, a link collection, a knowledge catalog, or a task board. Sharing is always per-asset (never whole-account), always consent-based (the recipient must accept), and always revocable by either side. This guide is the canonical walkthrough of how sharing behaves across native Tavina tools, including where tools differ.
Prerequisites
- Both people need Tavina accounts. Sharing targets another subscriber, not an email address or external user.
- A supported tool and asset. See the capability matrix below for exactly what each tool can share today.
- A verified relationship. Tavina uses your community relationship graph (FluentCommunity) as identity/relationship evidence โ you share with people you are actually connected to. Tavina itself remains the authoritative source for who can access what: the community data is evidence, not the permission system.
How a share works, end to end
1. The owner creates a share (invite)
From inside the tool โ for example Calendar’s Settings > Sub-calendars > sharing โ the owner picks a recipient and a permission level. This creates a share invite in pending state. The owner can see it listed under their shares as pending until it is answered.
Permission levels you may see (exact set varies by tool):
| Permission | Meaning |
|---|---|
| Free/busy only | Recipient sees when you are busy, not event details (Calendar) |
| View only | Recipient can see the asset but not change it |
| Suggest/comment | Recipient can comment or propose changes without editing directly |
| Edit | Recipient can change the shared asset |
| Manage sharing | Recipient can also manage who else has access |
2. The recipient is notified and accepts or denies
Pending invites surface in two places:
- the notification center badge and tool banners, which poll for pending invites across all shared-capable tools every two minutes; and
Settings > Account > Shared Tools, the single hub for all sharing on your account.
The recipient chooses Accept or Deny. Denying sets the invite to denied and removes it from active lists. Accepting sets it to accepted โ the shared asset then appears in the recipient’s tool on next refresh.
3. Both sides manage the ongoing share
In Settings > Account > Shared Tools, every share appears under one of two columns: Sharing from me (you are the owner) or Shared with me (you are the recipient). Each card shows the asset name, tool, permission, status, verified display names for owner/recipient, and โ if something is off โ a plain-language status reason.
Available actions:
- Owners see Unshare (revoke the grant entirely).
- Recipients see Leave (remove their own access).
- Recipients on an accepted share can toggle Assistant on/off โ whether Tavina may use that shared asset as context when answering you. This is off by default until accepted, and you stay in control of it afterwards.
4. Revocation, deletion, and what happens then
- Revocation is immediate and live. There is no access cache: the moment a share is revoked (unshare/leave), subsequent reads and writes are refused, and the asset disappears from feeds and assistant context.
- Deleting the underlying asset revokes its shares. If the owner deletes the shared sub-calendar, list, note, or collection, the grants are revoked automatically (status reason
resource_deleted), rather than dangling. - Suspended shares. A share can enter a
suspendedstate (for example, when the relationship that justified it is no longer verifiable). Suspended shares still appear in the hub with their status reason so you can see why access stopped; they can still be revoked outright by either side. - Expiry. Share records carry an expiry field, and expired shares stop working. Today, expiry is an internal backend capability โ the public UI does not offer an owner-configurable expiry picker. Where a share you rely on has expired, ask the owner to share again.
Permission changes and safety
Changing a permission downward (e.g. Edit โ View) applies directly. Raising a permission (e.g. View โ Edit) on an already-accepted share does not silently grant more access: the grant goes back to pending with a status reason (permission_escalation_requires_confirmation) so the recipient must explicitly re-confirm. That re-confirmation requirement is intentional: an accept should never grow in scope without the recipient knowing.
The Shared Tools hub versus per-tool surfaces
Settings > Account > Shared Tools merges sharing across Calendar, Shopping, Notepad, Links, and Knowledge Library into one list. Some tools additionally show sharing inside their own screens (Calendar’s sub-calendar sharing manager; Tasks shows shared boards inline). The hub is the authoritative single view; if a tool’s own surface ever disagrees with it, trust the hub and re-open the tool to refresh.
Capability matrix: what each tool can share
| Tool | Shareable asset | Permissions | Invite/accept flow | Recipient experience | Notes / deviations |
|---|---|---|---|---|---|
| Calendar | Sub-calendars | Free/busy, View, Edit (Manage sharing where offered) | Full: invite โ pending โ accept/deny | Shared sub-calendar appears with owner and permission labels; filterable in the sources drawer | The most complete sharing implementation; reference model for the others |
| Shopping | Shopping lists | View / Edit | Invite via the list’s sharing control; pending invites surface in the hub and banners | Shared lists appear among your lists with owner/permission info | โ |
| Notepad | Notes and note collections | View / Edit | Same lifecycle | Shared notes/collections appear in Notepad | โ |
| Links | Link collections | View / Edit | Same lifecycle | Shared collections appear in Links | โ |
| Knowledge Library | Knowledge catalogs | View / Edit | Same lifecycle | Shared catalogs appear in Knowledge Library | โ |
| Tasks | Task boards | View / Edit (recipient mutations gated by grant) | Deviation: shared boards arrive via the tasks shared-board feed and appear directly in Tasks; pending-invite polling includes Tasks, but Tasks grants do not merge into the Shared Tools hub today | Shared boards are marked “Shared by |
Tasks uses its own board-level gating rather than the hub card UI; see Tasks |
| ShopView (On Request) | Not shareable today | โ | โ | โ | ShopView is an optional, on-request tool. It does not appear in the sharing surfaces; sharing for it is not supported. “On Request” refers to tool availability, not private data |
| Discord Moderator (On Request) | Not shareable today | โ | โ | โ | Same as ShopView: optional on-request tool, no sharing support |
Sharing and your assistant’s context
When you accept a share you decide, per share, whether Tavina may use it as context (Assistant on/off in the hub). Pending invites are discovery-only by construction: a pending grant never leaks the shared payload โ accepted-only feeds gate actual content access. So an unaccepted invite gives the owner no visibility into your data and gives you no access to theirs.
Privacy notes
- Shares are between the two named subscribers only; grant records show verified display names resolved server-side, not raw account internals.
- Notification banners reveal the asset name, tool, and owner โ never asset contents.
- Assistant access (
use_with_assistant) is a per-grant switch you control; turning it off removes the shared asset from assistant context without unsharing.
Troubleshooting
| Symptom | What to do |
|---|---|
| Invite never arrives | Ask the owner to confirm the recipient account; invites only deliver between connected subscribers. Check the notification bell and Settings > Account > Shared Tools โ invites also appear there. |
| Accepted share doesn’t appear | Open the tool again to refresh its feed; the hub is the source of truth. If still missing, use Help to contact support. |
Share shows suspended |
The relationship that justified the share could not be re-verified. Re-establish the community connection or ask the owner to share again. |
| “Edit” suddenly became view-only | The owner likely reduced the permission, which applies directly. |
| Asked to re-confirm a share | The owner raised your permission; re-accept to acknowledge the broader access. |
| Shared board edit rejected | View-only boards reject edits, and concurrent edits on shared task boards are conflict-checked โ reload the board and retry. |
For anything else, use the Help section in the app to reach support.
Related pages
- Settings overview โ where the Shared Tools hub lives.
- Calendar tool โ sub-calendar sharing in Calendar.
- Tasks โ shared task boards.
- Settings and profile basics โ assistant navigation consent rules.
Questions this page answers
- Where do I see all my shares and pending invites? (
Settings > Account > Shared Tools, plus notification banners.) - Does a pending invite expose my data? (No โ discovery-only; content access requires acceptance.)
- What happens when an owner deletes a shared asset? (Grants are revoked automatically with reason
resource_deleted.) - Can I stop Tavina from using a shared asset without unsharing? (Yes โ Assistant on/off per share in the hub.)
- Which tools support sharing today? (Calendar, Shopping, Notepad, Links, Knowledge Library, Tasks โ see matrix; ShopView and Discord Moderator do not.)