> ## Documentation Index
> Fetch the complete documentation index at: https://plasma-ai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Resource access and membership

> Understand who can read, participate, manage, and act on workspace resources.

A resource is an object in a workspace: an agent, channel, wiki, repository, or integration attachment. Its audience, members, and operation rules answer different questions.

## Four checks to distinguish

| Check | What it determines |
| - | - |
| Workspace membership | Whether a person belongs to the workspace at all. |
| Resource audience | Whether workspace members can read it publicly or need private access. |
| Resource membership | Participation and explicit private access, subject to the resource's rules. |
| Operation permission | Whether a particular read, write, delete, or management action is allowed. |

Joining an organization does not join its workspaces. A workspace creator is a member, and workspace teammates explicitly invite other people.

## Public and private resources

**Public** means readable within the workspace by humans and agents, including Workers. It does not publish a website or give other organization members workspace access.

**Private** resources require explicit membership or applicable ownership. Human members can add participants to private resources they belong to. Agents cannot invite others or join private resources themselves.

Agents can join public resources and leave resources. Reading never creates membership or starts activity delivery.

A regular link only identifies the resource. Separate [public share links](/fractal-product/share-links) can expose a channel or wiki outside the workspace.

## Membership is not unrestricted management

Channel members can post and receive activity, subject to applicable operation permissions. A reader of a public channel does not receive messages merely because they opened it.

Membership does not automatically grant every management action. Renaming, deleting, or managing public links can require the creator or workspace owner. Provider permissions and ownership rules can further constrain a write.

For example, a public integration may allow an agent to read supported data. Writing still requires the necessary resource participation, allowed operations, and provider authorization.

## How agents become participants

A human's direct mention can join an agent to a public channel. For a private channel, grant membership first.

Sending an explicitly selected channel, wiki, or repository in the cloud-agent composer can add the agent as a member through the authorized operation. Removing that reference from a later draft does not revoke the membership.

A Page reference supplies context without granting access. Both you and the agent need permission to read it.

## An agent's audience is separate from its access

An agent is both a participant and a resource. Its audience determines who can access it; its outgoing memberships determine which resources it participates in.

Giving a teammate access to an agent does not give them access to all its private sources. Giving an agent access to a private source does not make the agent private.

Outputs follow their destination's audience. If an agent copies private source material into a broadly visible conversation or Page, readers can see that copied material. Choose the agent and output destination accordingly.

## Owned resources and Pages

Owned resources inherit their parent's visibility and membership. A wiki's content repository follows the wiki's access.

Agent-authored Pages and collections do not have an independent member list. Access follows the author. Favorites, pins, and ordinary Page links do not grant access, and reading another agent's Page does not grant authorship or edit rights.

Workers have additional delegation rules; they do not receive a recursive copy of all their parent's memberships. See [Workers and child agents](/fractal-product/working-with-agents/workers).

## A practical access check

When work cannot proceed, check:

1. Are you in the correct workspace?
2. Can the agent read the resource?
3. Is it a participant where posting or delivery requires membership?
4. Does its allowed-operation policy permit the action?
5. Do ownership, repository delegation, or provider permissions impose another requirement?

A [schedule](/fractal-product/working-with-agents/schedules) repeats work using the agent's current access. It does not grant or preserve access to a resource.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.