Top FAQ

• What is VU.CITY Early Access?

  Early Access provides access to the next generation of the VU.CITY platform.

• How do I know if I have Early Access?

  Access is currently being provided in phases. Your Account Manager will work with your designated admin to assign access to the relevant users and provide all instructions.

• How do I request Early Access?

  You can register your interest using the VU.CITY website, or by contacting your account manager.

• Why am I seeing Early Access articles in the Knowledge Base?

  The Knowledge Base contains documentation for both the legacy application and Early Access, providing a single location for all VU.CITY product documentation.

• How do I know whether an article applies to me?

  Articles are organised into sections according to the application they relate to. Follow the documentation for the version of VU.CITY that is available to the account.

• I don't have access to Early Access. Can I still use VU.CITY?

  Yes. The legacy application remains available and fully supported while Early Access continues to evolve.

• Are all features available in Early Access?

  Early Access is under active development, and functionality is being added over time. Some workflows may currently only be available in the legacy application, others are only possible in Early Access.

• Will the Legacy application be retired?

  The legacy application will eventually be retired. Migration timelines and end-of-life dates will be communicated in advance.

• Is the current (legacy) app still available?

  Yes. The legacy application remains available and the migration date and end-of-life date will be confirmed and communicated in advance.

• Where can I find help and documentation?

  The Knowledge Base contains articles for both the legacy application and Early Access. Look for the section that matches the version you are using.

• How do I report a problem or give feedback in Early Access?

  You can share feedback using the lightbulb icon in the bottom-right corner of the application, or request support through the Knowledge Base.

• Will I lose my work?

  No. All legacy projects will be migrated as part of the transition, so your work will not be lost. Full details and timelines will be communicated in advance.

• What will happen during migration?

  Migration plans and timelines will be communicated clearly by your Account Manager and ahead of time, including any important dates and actions required.

• Will my old files be migrated?

  Migration plans and timelines will be communicated ahead of time, including any important dates and actions required.

• Will my projects and data be available in both versions while I run them in parallel?

  Following migration, your projects will be available in the new platform, which becomes the primary place to work. The legacy application will remain accessible for reference, and will move to read-only at a point that will be confirmed in advance. Once migrated, we recommend continuing all work in ... Show more

• Why can’t a member see a folder after being invited to the organisation?

  Being invited to an organisation does not automatically grant access to its content. A member must also be granted permission to the organisation’s top-level folder, a specific folder, or an individual file before any content becomes visible.

• Why is the organisation folder empty?

  If no permissions have been assigned yet, the organisation root folder will appear empty. Once access is granted to content, it becomes visible according to the assigned permission.

• Why can a member see a folder but not open it?

  The folder is likely shown with Limited access. This means access has been granted to content further down the folder structure. The folder itself has not been shared and is only visible to provide a path to the shared content.

• Why can I edit one folder but not another?

  Permissions are applied independently to folders and files. A member may have Editor access to one folder while only having Viewer access to another.

• Why can someone edit a file but not its parent folder?

  The file has probably been given an explicit permission. Explicit permissions only apply to the item they are assigned to and do not automatically grant access to parent folders.

• Why doesn’t changing a folder’s permissions update another folder?

  Permissions only flow down the folder hierarchy. Changes made to one folder do not affect sibling folders.

• Why didn’t an explicit permission replace the inherited permission?

  Explicit permissions only take precedence when they provide a higher level of access. If the inherited permission is already higher, it continues to apply.

• Can inherited permissions be stopped halfway down the folder tree?

  No. Inherited permissions always continue down the folder hierarchy. To provide different access to a specific folder or file, apply an explicit permission.

• Can a lower permission be applied to a subfolder?

  No. Permissions can only be increased through an explicit permission. To reduce access, change or remove the permission higher up the folder hierarchy.

• Why does someone still have access after permissions were removed?

  Check whether another permission still applies. A user may retain access through: another parent folder another explicit permission All Members organisation administrator access

• If a file is moved, does it lose its permissions?

  Not necessarily. Inherited permissions update based on the new location, while explicit permissions remain with the file.

• If a folder is moved, does it lose its permissions?

  Inherited permissions update to match the new parent folder. Any explicit permissions applied directly to the folder remain unchanged.

• Why can someone see a shared folder from another organisation but not its parent folders?

  For security reasons, shared content from another organisation hides intermediate folders. Only the organisation’s top-level folder and the shared folder are displayed.

• Can a folder have different Owners from its parent folder?

  Yes. Ownership can be assigned independently on individual folders.

• Does moving a file make it public?

  No. Moving content only changes inherited permissions based on its new location. It does not automatically make content visible to other members.

• I gave someone access, why can’t they see it?

  There are several reasons why a member may not be able to see content after access has been granted. The steps below cover the most common causes. 1. Confirm permission has been assigned Being a member of an organisation does not automatically provide access to its content. A permission must be... Show more