Project Visibility
Project visibility in Sandtime.io is determined by membership, not by a setting. A person can see a project if they are assigned to it as a member. There is no public or private switch to configure - assignment is what grants visibility.
Key Characteristics
- Membership-based: you see a project only if you are a member of it.
- Administrators see everything: an administrator sees every project in the organization, regardless of membership.
- No configuration: visibility is not a per-project option you toggle. You change who can see a project by changing who is assigned to it.
How a project becomes visible
To let someone see a project, add them as a member. To hide it from someone, remove them or leave them unassigned. A project administrator manages a project's members; an administrator can do this for any project.
What visibility affects
- Project lists: only projects you are a member of appear in your lists and dropdowns. Administrators see all of them.
- Reports: a project's data appears in your reports only for projects you can see.
- Time entry: you can log time only to projects you are assigned to.
Visibility and assignment
Visibility and assignment are the same mechanism here: being assigned to a project is what makes it visible to you. This differs from systems that separate an organization-wide public or private flag from per-member assignment. Sandtime.io has only assignment.
Related Terms
Project visibility is a membership-based part of access control. It works through assignments and roles: administrators see every project, while everyone else sees the projects they are assigned to.