Advise for Separate Workspaces or Under One Workspace for Projects Created from a Blueprint

susanmgfin

Our blueprint is ready to go. Each project is for an external client. We plan to share some of the sheets/reports/dashboards with the clients (I've already got a client specific role with a workapp for them).

Is it best to put each client project in a separate workspace if all the sheets come from a blueprint? I understand security measures but not everyone internally using the tool understands the criticality of what they share with whom.

I wish the sharing permissions could be done at the folder level within a workspace more easily. Just want to start out with the workspace and folder structure correctly.

Thanks.

kowal

hi @susanmgfin

this statement "not everyone internally using the tool understands the criticality of what they share with whom" lack of knowledge now can be disastrous if you have hundreds of projects in one workplace shared among dozens of customers… if your customers will figure one day someone unwanted has access to their sensitive data like (finances etc.) you would be in very very big trouble also legally.

Why not create multiple blueprints (create and duplicate) and for every customer there will be individual workspace that only they will have access - also if it goes for Intake Sheet and Summary Sheet and Portfolio do all the customers can see each other data in those 2 files as well?

susanmgfin

The clients will never see or use the intake sheet or the portfolio summary. They will access everything via a workapp and the budget sheet will not be shared with them - only the external facing dashboard, plan, raid log, and team roster. I would not want a different blueprint for every customer; that defeats the purpose of being able to use control center and global updates for changes. I think the that the best approach is just creating a separate workspace for each client but it will still be based off the same blueprint.