Product updates
Projects: Keep One Workspace Clean Across Many Products
Imagine you run design for a company with a mobile app, a marketing website and an old internal tool nobody wants to talk about. You connect all of them to DesignGuard, because of course you do. Now you open the dashboard, and it says you have 212 findings.
Which ones are about the app? Which are about the website? You can't tell. Every chart, every list and every score is the whole company blended together, and a number that blends everything tells you almost nothing.
This is the problem Projects solve.
Before · everything mixed
212 findings
Mobile, website and the old prototype, all in one list
Which of these are mine?
You scroll and guess
Now · pick a project
Project: Mobile app
Pick it once in the header
61 findings
Only the mobile app. Every screen follows.
What a project is
A project is a simple group. You put the Figma files and GitHub repositories that belong to one product into it. That's all it is.
One workspace · your team, your plan, your standards
Project: Mobile app
- • Figma: Mobile UI kit
- • GitHub: acme/mobile
Project: Marketing site
- • Figma: Website designs
- • GitHub: acme/website
Default project
- • Everything not moved yet
A workspace is still your team: who is a member, what plan you're on, and which standards are approved. Projects live inside it. You can think of the workspace as the office, and each project as a team's desk in that office.
Pick a project once, and every screen follows
Once you have a second project, a project dropdown appears in the header. Choose one, and the screens you use every day narrow down to it:
- The dashboard and health history
- Findings and audits
- Coverage, mappings and product flows
- Figma imports and GitHub repositories
Choose "All projects" and you get the full picture again. Your choice is remembered, so you don't have to pick it each time you come back.
If you have only the default project, the dropdown stays hidden. There's nothing to choose, so we don't add clutter.
Setting it up takes a few minutes
- Open Settings, then Projects.
- Create a project and give it a name, like "Mobile app".
- Move the Figma files and GitHub repos that belong to it. Everything that was already scanned from them moves along, so you don't have to re-import anything.
- Done. Anything you haven't moved stays in the default project, so nothing is lost or hidden.
New Figma imports go into whichever project is selected in the header at the time. We don't create projects behind your back. A project exists only because you made one.
What stays shared across the whole workspace
Some things are about your team or your design language, not one product, so they stay workspace-wide on purpose:
- Approved standards and rules
- Team members and roles
- Billing and plan
- Single sign-on and security settings
The idea is that your design language is one thing, and projects are just different lenses on how well each product follows it.
Workspace or project?
A quick rule of thumb. If it's a different team, a different bill or a different set of standards, make a new workspace. If it's the same team looking after a different product, make a project. Most organisations need one workspace and a handful of projects.
A few honest details
- Only workspace owners and admins can create, rename or archive projects. Everyone can look at them.
- The default project can't be archived. It's where anything unassigned lives.
- A Figma file or repo belongs to one project at a time. Moving it changes where its findings show up.
It's a small feature on the surface. But when your dashboard says something about the product you're actually building this week, the numbers start to mean something again.
See it on your own design system
Run a DesignGuard AI audit against a real Figma frame or repo.