The new VU.CITY
Early Access provides access to the next generation of the VU.CITY platform.
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.
You can register your interest using the VU.CITY website, or by contacting your account manager.
The Knowledge Base contains documentation for both the legacy application and Early Access, providing a single location for all VU.CITY product documentation.
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.
Yes. The legacy application remains available and fully supported while Early Access continues to evolve.
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.
The legacy application will eventually be retired. Migration timelines and end-of-life dates will be communicated in advance.
Yes. The legacy application remains available and the migration date and end-of-life date will be confirmed and communicated in advance.
The Knowledge Base contains articles for both the legacy application and Early Access. Look for the section that matches the version you are using.
You can share feedback using the lightbulb icon in the bottom-right corner of the application, or request support through the Knowledge Base.
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.
Migration plans and timelines will be communicated clearly by your Account Manager and ahead of time, including any important dates and actions required.
Migration plans and timelines will be communicated ahead of time, including any important dates and actions required.
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