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

# Source visibility and permissions

> Learn who can see, use, and manage Personal, Project, and Workspace Sources.

Source visibility comes from two choices:

1. **Where you add the Source** — Personal, Project, or Workspace Sources
2. **What access a person has** — their account, workspace membership, or Project role

Choose the narrowest Source location that gives the intended audience access.

## Personal Sources

Personal Sources are available to you across your Projects. They are not workspace-shared by default, so use them for material that other workspace members should not automatically see.

If a teammate or an entire workspace needs the material, add it to the appropriate Project or Workspace Sources location instead.

## Project Sources

Project Sources are visible to people who can access the Project. Project roles control what each person can do:

* People with read access can view Project Sources.
* People with editing access can add and organize Sources.
* Removing or changing Project Sources is an editing action.

Project access and Source access should be considered together. Someone who cannot access the Project should not be given the Project's Source link.

## Workspace Sources

Workspace Sources are shared across the current workspace. They are intended for material that people in that workspace can use across their work.

Workspace membership is the boundary for Workspace Sources. Do not use this scope for information that should be limited to one Project or one person.

## Sharing a Project

When a Project is shared beyond its normal Project members, the owner can choose whether its Sources are included in the shared view. Sharing a Project does not automatically make its Sources public.

Before sharing a Project, review:

* Whether the shared audience needs the Sources
* Whether the Sources contain confidential or personal information
* Whether each Source belongs in the shared Project

If Sources are not included in the shared view, the shared audience can still see whatever Project content the sharing settings allow, but not the Project's Sources.

## Keep access intentional

Before uploading a Source, ask:

* Who needs to use this information?
* Is the information personal, Project-specific, or workspace-wide?
* Would the material be appropriate for everyone who can access this scope?

If the intended audience changes, delete or replace the Source in the old scope and add it to the new one. Folder placement helps organization, but it does not change visibility.