Visibility and Ownership
Purpose
Use this guide to understand how Spec27 decides which assets a user can view or manage.
When to use it
Read this page when teammates cannot find a project, dataset, or agent they expected to see, or when you are deciding how to share work.
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.
Expected result
You can predict whether a project asset should be visible to the current user and understand where to check next if it is not.