Orgs, Projects, and Roles
Understand how OpenSana groups work and grants access.
OpenSana has two main access scopes: organization and project.
Organizations
An organization is the top-level container for people, projects, and policies.
Use organizations to:
- group related projects
- manage membership centrally
- control admin-level access
Projects
Projects are where work actually happens.
Each project has:
- a human-readable name
- a short alias such as
WEB - task data
- thread data
- project members and permissions
Roles and Permissions
OpenSana uses organization-level and project-level permissions together.
In practice:
- org owners and admins have broad access across projects
- project members can be scoped to a single project
- permission checks are enforced by the backend, not just the UI
Practical Guidance
- Use organizations to model companies, teams, or client accounts.
- Use projects to separate products, repos, workstreams, or environments.
- Keep aliases short and stable because they appear in task refs such as
WEB-42.