I cannot find an answer to this question, and it’s annoyed me enough now to ask the community.
I have various workspaces set up for our projects (one for our assigned team member with info we don’t want the client to see, one introducing our client to their assigned team member, and sometimes one for third party vendors).
When I move a project along in the states through automations or archive it, why doesn’t it also move it along in the workspaces? I mean I get that there can be multiple stages for the same project, but you’d think when I archive the main project it would at least archive all the workspaces. Instead, I have to manually go in and either delete the other workspaces or move them to archive too.
This is becoming an issue as we approach our busy season and I still see archived/lost projects showing up on our calendar because the other workspaces didn’t get archived.
Suggestions?
Best answer by Alicia Bauer
@Denise O'Malley - You're definitely not alone in noticing this! At the moment, HoneyBook treats each workspace as its own entity—even if they’re part of the same overarching project. That means when you archive or update the stage of the primary workspace, the connected or secondary workspaces won’t automatically update or archive alongside it.
While this setup does allow for flexibility (especially when you’re collaborating with third-party vendors or keeping internal notes), it does add some manual work for multi-workspace users—like needing to archive each one individually or clean up your calendar view during busy seasons.
✨ If this functionality would be helpful to you (and it sounds like it would!), we highly recommend submitting it to the Ideas section in the HoneyBook Community. That’s the best place to make sure the product team sees your request, and other users can upvote it if they’d like to see the same improvement. The more demand it gets, the more likely it is to be added to the development roadmap.
@Denise O'Malley - You're definitely not alone in noticing this! At the moment, HoneyBook treats each workspace as its own entity—even if they’re part of the same overarching project. That means when you archive or update the stage of the primary workspace, the connected or secondary workspaces won’t automatically update or archive alongside it.
While this setup does allow for flexibility (especially when you’re collaborating with third-party vendors or keeping internal notes), it does add some manual work for multi-workspace users—like needing to archive each one individually or clean up your calendar view during busy seasons.
✨ If this functionality would be helpful to you (and it sounds like it would!), we highly recommend submitting it to the Ideas section in the HoneyBook Community. That’s the best place to make sure the product team sees your request, and other users can upvote it if they’d like to see the same improvement. The more demand it gets, the more likely it is to be added to the development roadmap.
@Denise O'Malley - You're definitely not alone in noticing this! At the moment, HoneyBook treats each workspace as its own entity—even if they’re part of the same overarching project. That means when you archive or update the stage of the primary workspace, the connected or secondary workspaces won’t automatically update or archive alongside it.
While this setup does allow for flexibility (especially when you’re collaborating with third-party vendors or keeping internal notes), it does add some manual work for multi-workspace users—like needing to archive each one individually or clean up your calendar view during busy seasons.
✨ If this functionality would be helpful to you (and it sounds like it would!), we highly recommend submitting it to the Ideas section in the HoneyBook Community. That’s the best place to make sure the product team sees your request, and other users can upvote it if they’d like to see the same improvement. The more demand it gets, the more likely it is to be added to the development roadmap.
Thanks for this explanation and I admit the voice in my head thought “oh for pete’s sake!”
I’ll submit to the ideas section as sometimes I have 5 workspaces set up for one project.
