Visibility and Ownership
Use this guide when teammates cannot find the project asset they expect, or when you are deciding how work should be shared.
Prerequisites
- You understand the difference between organization-level sharing and project-level work.
How access works in practice
- Organizations define the top-level collaboration boundary.
- Projects own the assets created inside them.
- Some list views show only assets you can access.
- Ownership filters help users focus on their own work.
- Private assets owned by other users may be hidden or denied depending on the context.
Practical rules of thumb
- Start by checking whether you are in the correct organization.
- Then check whether the asset belongs to the project you expect.
- Then check whether list filters are hiding assets you can technically access.
- If an asset is private and belongs to someone else, access can be denied even if you know the URL.