Managing access within VU.CITY projects is critical to ensuring the right levels of collaboration and security. There are two primary ways to configure this access.

Project access control

By default, access to projects in VU.CITY can be set to 'Invite-Only'. This setting means that new project members can only join if they are specifically invited by an admin or editor. This method is crucial for maintaining control over who can see and interact with project information, ensuring that access is granted only to individuals directly involved or necessary for the project. Project admins can set this up at the initial creation of the project or adjust it in the project settings under 'Project Preferences'.

Project access levels

Within each project, files and documents can be managed with granular access permissions defined by three main roles:

Admins

• Role
  Admins have full control over the project. This includes adding or removing members, modifying project settings, and managing access to all files and folders within the project.
  
  
• Capabilities
  Admins can set project details, determine the primary file, and control access settings to ensure that only the right eyes see sensitive information.
  
  

Editors

• Role
  Editors can modify existing project files, contribute to project development, and invite other editors or viewers, fostering collaborative workflows.
  
  
• Capabilities
  Editors can make necessary changes to the primary files, supporting dynamic development environments.
  
  

Viewers

• Role
  Viewers have read-only access, making this role perfect for stakeholders or team members who need to review project progress but should not alter project content.
  
  
• Capabilities
  They can access project information and comment on files, providing insights and feedback without impacting the project's content.

File access management

Project Drive interface

The Project Drive allows you to store all related files in one secure place. Admins and editors can add new files or folders, while viewers can access files for review.

Each file within the project drive can be individually set to be accessible by all project members, or restricted based on role, ensuring detailed control over who can view, edit, or comment on specific documents.

Viewing specific files

Beyond global role-based access, specific files can be further restricted or opened up to different users via the project's drive interface. When uploading or managing a file, admins and editors can choose to set custom access for individual files, tailoring who can see and interact with each piece of content based on the project’s evolving needs.

Setting file permissions

Access control: You can specify who can view or interact with particular assets through VU.CITY’s access control options. Permissions can be set for individual files, restricted by role (Admins, Editors, Viewers) or customised for specific team members.

Quick filters: Utilise quick group filters for setting access, such as "All project members," "Admins," "Editors," and "Viewers," streamlining the process of permissions management.

Customising access for specific members

Tailor access by adding specific individuals to files, which allows for granular control over who can view or edit project materials. This feature is particularly useful for managing access to sensitive information.