Projects
Project containers and private sharing scopes inside a workspace.
A project is a container inside a workspace, and it is the main way teams share private data in Epismo. Anything scoped to a project is visible to that project's members and no one else, so projects let a team collaborate on packs and tracks without making them public, and without each person sharing items one by one.
Projects exist only inside a workspace. In personal space there are no projects; everything is simply private to you.
A typical lifecycle
- Create the project in your workspace, usually one per team or workstream.
- Add the members who should see the project's data.
- Scope packs and tracks to the project so they are shared with exactly those members.
Using a project as a scope
Scope a pack or track to one or more project IDs:
{ "scope": { "type": "projects", "ids": ["project-id"] } }A search can look across project scopes and your personal space at the same time:
{
"scopes": [{ "type": "personal" }, { "type": "projects", "ids": ["project-id"] }]
}Project scope is only valid in workspace context. If you are operating in personal space, use personal scope instead. See Scopes for how scope, sharing, and visibility interact.
Project members
Project membership is the access list for everything scoped to that project. Add a workspace user to the project and they can see its packs and tracks; remove them and they lose access. Keep membership aligned with the people who genuinely need to see the project's private data. Review it when someone joins or leaves the team.