How can we help?
Start with the part of the project you are working in. If the guidance does not answer it, send the real context below.
Find the workflow before the workaround.
Getting started
Create a Free workspace, explore Villa Espresso, and bring one real project.
Open guidance →Projects & Rooms
Project identity, rooms, archived projects, and the Whole Project view.
Open guidance →Items / BOQ / sourcing
Lists, quantities, VAT, references, status, and URL Autofill.
Open guidance →Suppliers
Shared supplier records, contacts, websites, and project reuse.
Open guidance →Renderings & Versions
Current state, earlier revisions, review, and comments.
Open guidance →Documents
Technical PDFs, visibility, versions, and document comments.
Open guidance →Client Portal
Client-visible project context, shared lists, media, and documents.
Open guidance →Members & Access
Studio, client, and vendor roles with explicit project visibility.
Open guidance →Mobile
Responsive Studio and Client project access where the work happens.
Open guidance →Plans & billing
Users, active projects, storage, upgrades, and onboarding capacity.
Open guidance →Clear answers for current product behavior.
Can I create an account without contacting DesignerFlow?+
Yes. Create a Free workspace directly with one active project and no payment method.
Where should I start inside the product?+
Open Villa Espresso to understand a populated project, then create one real project and add only the structure it needs.
Do archived projects count as active?+
No. Archived projects leave the active Project Hub count and remain recoverable with their linked project information.
Can clients see internal studio information?+
Client access is curated. Only client-visible project content is presented through the Client Portal.
Can I review an earlier rendering or document version?+
Version history remains available while the current revision stays explicitly identified.
Where can I report a bug or confusing workflow?+
Use the Help & Feedback form below with the page, feature, and what happened.
Send the actual context.
Include the page or feature, what you expected, and what happened. That is more useful than a generic support category.