By default, all new projects created in the workspace are ‘open’. That means that everybody in the workspace can see all projects. You can restrict access to a specific project by changing the access settings for that project.
To manage access for a project:
Open a project.
There are four access levels. They are cascading, which means that someone with Full access to a project will also inherit the permissions of the other roles.
|Permission||Full access||View and edit||View only||No access|
|View the project||✔||✔||✔|
|Create, edit, and analyze data||✔||✔|
|Toggle public access for insights||✔|
|Manage project settings||✔|
|Manage project access||✔|
Note that project access levels only apply to admins and users. If assigned to a viewer, their workspace role takes precedence and access is limited to View only. Viewers can still be restricted from seeing a project by setting the workspace access to No access.
To allow everyone in the workspace to see and manage your project, set the project’s workspace access to Full access, and don’t add any individual people. This is the default setting for all new projects.
To restrict a project so that only certain people in the workspace can see it, set the project’s workspace access to No access, and add people individually as View only, View and edit, or Full access.
To allow everyone in the workspace to see the project, but only allow some people to manage the project, set the project’s workspace access to View and edit, and add individual people with Full access.
To make your project private, set the project’s workspace access to No access, and make sure that you are the only person with Full access.
Workspace admins (see About workspace roles) will not be able to see restricted or private projects, unless they have been explicitly added to the project. This means you can have projects that even workspace admins cannot see.
Can’t find what you’re looking for? Search through our articles or contact our support team and get a response within 24 hours.Get help