Hey there! I’m part of a professional services team that implements software with external clients. We want the option to share the project schedule with customers, without including the minutiae of everyday tasks and time tracking.
My initial thought is to create two projects, one internal with all the in-the-weeds task information and one external, a 10,000 ft view of the project. Ideally, these projects would update simultaneously, e.g., a task hosted on the internal project is linked to the external project and once completed, reflects that information accordingly.
My ask is - is there a way to scale the creation of these two projects with workflow/rules? Or is there another solution that I am just not seeing?
2 Likes
Hi @Kayleen_Tombarello, great question! The most scalable approach is to use one internal project as your source of truth and share only high-level work with customers using multi-homing, rather than maintaining two fully separate projects. You can add milestone or phase-level tasks to both an internal and an external project so updates (due dates, status, completion) automatically stay in sync, while detailed subtasks, time tracking, and internal comments remain in the internal project.
To scale this, use project templates for consistent setup and rules (for example, when a task is marked “Customer-visible,” add it to the external project). This keeps the external view clean without duplicating work.
1 Like