Who can see whom in your organization
In Sandtime.io, what you can see depends on your role and on the projects you share with other people. This keeps each person's view focused on the work they are part of.
Administrators see everyone
An organization Administrator sees every member of the organization and every member's activities, whatever projects those people belong to. This is org-wide by design, so admins can manage members, projects, and reports across the whole organization.
Users see the people on their projects
A User (the default role) sees a narrower slice of the organization:
- themselves
- every organization Administrator, always, even with no shared project
- anyone who shares at least one project with them
So if you and a colleague are both on the same project, you see each other. If you share no project and neither of you is an Administrator, you do not appear in each other's member lists or reports. Administrators are the exception: a User always sees every Administrator, because admins manage the organization.
This is why a brand-new account with no project assignments still sees the organization's administrators, but no other regular users - there is no shared project yet to connect them.
Who can see activities
Activities are the time entries people record.
- Administrators see every member's activities across the whole organization.
- A User sees their own activities in full, plus the time their teammates reported to the projects they share. Activity you do not share a project for stays visible only to its owner and the administrators.
- Archived projects, and projects where your own membership is archived, drop out of this view.
Seeing an activity is not the same as being able to change it. Only the person who recorded an entry, or an Administrator, can edit, move, or delete it. See reassigning time entries for how an admin moves an entry to a different person.
Making people visible to each other
If two people should see each other, put them on a shared project. Add members to a project from its Members section, or invite new people to the organization first and then assign them. See create a project for reported time to set one up.
For the full breakdown of what each role can do, see Roles and permissions, and access control in the glossary.