# Sharing and access

## Share through buckets

A [bucket](/account/buckets) connects content to its members. The bucket owner manages membership through the UI or MCP `add_bucket_member` / `remove_bucket_member`. Share a wiki as a container: new articles become available under current rights at read time. A fixed article list is not container sharing.

## Invite people and accept invitations

When inviting someone, search and select known people by name. This list contains direct contacts from invitations or previous sharing, not a global user directory. The email helps distinguish identical names. Invite a new person with an existing account using their exact email address.

New bucket access starts with an invitation. The recipient cannot access its content before accepting. Under [Buckets](/account/buckets), recipients can accept or decline; senders can withdraw it under "Sent invitations" in the bucket's menu. Invitations expire after 30 days. Acceptance includes content added to the bucket later. Existing memberships remain valid.

With personal MCP, `add_bucket_member` creates an invitation and returns `added: false, status: pending`. `list_bucket_invitations` lists pending invitations; use `direction: outgoing` for sent invitations. `respond_bucket_invitation` accepts (`accepted`), declines (`declined`) or withdraws as sender (`withdrawn`). Your agent should accept only on your explicit instruction. Receiving a notification does not constitute consent. `search_contacts` searches only your known contacts.

Inviting again while an invitation is pending does not extend its expiry. After membership removal, retrying acceptance of an old invitation cannot restore access; a new invitation is required. Sending many new invitations is rate-limited. Retry after the relevant window has elapsed.

## Read shared articles and attachments

`get_object` returns the article text and resource links for additional files. Your client must support MCP `resources/read` to open these links. Shared skills also support `skills/list`, `skills/get` and `skill://` files when the client implements this extension.

Sharing exposes the currently delivered published version, not private drafts or the complete version history. An old file link may stop working after an update: call `get_object` again for the current links. Revocation blocks subsequent requests; it cannot recall copies already read.

Your own context takes precedence when object identifiers collide. Ambiguous identifiers across foreign shares fail closed; owners must use distinct identifiers. Workspaces do not widen or narrow this sharing boundary.

## Plugin content has domain roles

Plugins declare their own permissions. Share the tasks of a workspace, a wiki or a calendar as a whole through a bucket with an appropriate role; records added later are included automatically. Installation administration alone grants no access to domain records.

## Links and assignments are not grants

A reference points to a record. It does not copy content or authorize reading it. Assignments also grant no access. Protected parents and exclusions still apply.

## Rights apply to reports too

Search, counts, reports, exports and repeated writes must respect current rights. Revoked access cannot be bypassed through an existing link.

## Independent agent account

A separate account is for independently owned context, not a requirement for each additional app. Several clients can already connect to one account and act as the same user. Named, individually scoped agent access under one owner is [available for supported plugin content](/docs/agents). Core context and further plugins remain separate steps.

An agent with its own account manages private context and receives only the context you share. Connect it with personal OAuth; an org API key does not carry that user identity. Registration and initial authentication remain account setup. Ongoing context administration needs no dashboard.

Use `list_plugins` and `plugin_configure` to activate plugins in the agent's organization. New plugin content starts private. Share selected objects or whole wikis with `add_to_bucket`; share plugin content such as tasks with `plugin_link_bucket` and a role discovered through `plugin_access`. The recipient uses the owner organization returned by discovery. Private source content remains invisible.

Bucket membership and domain roles do not transfer ownership or automatically permit onward sharing. `plugin_set_access` manages direct organization-member roles/exclusions. Revocation covers exports and retries; the recipient's private context remains intact. Restricted import credentials receive no administration tools.

## For plugin developers

Use the [SDK reference](/docs/sdk/api) for host interfaces and the [test matrix](/docs/sdk/testing) for authorization checks. Some planned team and service-identity administration surfaces are not yet implemented.

See [Action items](/docs/action-items) for how your AI learns about new invitations.
