Understanding the Structure — Workspace, Projects & Versions
Written By Team BugSmash
Last updated 22 minutes ago
Why it’s useful
Understanding how BugSmash organises feedback helps to keep your workflow clean, structured, and easy to manage as the projects grow.
The hierarchy avoids confusion by properly separating clients, projects, and feedback.
How it works (Hierarchy)
1) Workspace (Top level)
A Workspace is the main umbrella for your organisation.
It contains:
Members
Collaborators / Guests
Folders
Projects
Workspace-level settings
Add-ons
Billing and plans
2) Folders
Folders help to organise projects in a structured way.
Each folder can contain:
Multiple projects
Multiple subfolders (folders within folders)
You can use folders to separate clients.
Example:
Client A → Folder A
Client B → Folder B
3) Projects
A Project is a dedicated feedback space for a specific deliverable.
All comments, reviews, and versions are attached here.
Projects can be created for:
Websites (Supports AI review)
HTML (Supports AI review)
Widget
PDFs (Supports AI review)
Videos
Images (Supports AI review)
Audio's
Emails
PPTs
Mobile Apps
3D Models
4) Versions
Versions help to manage different stages/updates of the same project in one place.
Each time you upload an updated file/design, a new version is created, for eg, (v1, v2, v3...)
5) Comments
Comments are where all feedback and annotations get added inside a project.
Each comment remains linked to the specific version where it was originally added, making it easy to track feedback across different versions.
6) Replies
Replies help teams to continue discussions inside the same comment thread.
Instead of creating separate comments, users can reply directly to an existing comment to discuss updates, fixes, or clarifications.
Each reply stays connected to its comment, keeping the feedback workflow clean and organised.
(Note: You can also add private replies, which are only visible to the internal team, which includes owners, admins and members.)
Tips
- One workspace per company.
- Separate client deliverables into projects or folders. You can also have 1 folder per client.
- Move old projects into archived folders instead of deleting — keeps version history intact.