Project Space Overview
This page provides a high-level overview of how to understand your Project Space in CommCare.
About Project Spaces in CommCare
A Project Space in CommCare is a secure, web-based space where all data related to your CommCare applications is stored, managed, and accessed. It serves as a centralized hub that enables organizations to efficiently develop, deploy, and oversee and use the applications for data collection and case management.
Project Space Functionality
Many CommCare users have one project space to run their own programs. Within a project space, you can do the following:
Project Customization
You can set permissions related to your project space. This includes
Project Space Naming: Customize the project space name without affecting the access URL.
Custom Branding: Apply logos, color schemes, and themes to match organizational branding.
Automated Workflows: Set up scheduled tasks for data processing, automatic case updates, or notifications.
Security Settings: Set security settings specific to your project space (e.g. two-factor authentication)
Multi-Application Management
Each project space allows users to develop and manage their own applications. You can manage multiple applications within one project space in CommCare. You can read more about developing applications here: https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143946283
Data & User Management Control
Project spaces provide built-in reporting tools that allow users to track and analyze various data points efficiently, as well as store any collected data from the application.
You can read more about these at https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143954690 & https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143957751 and
You can also manage a pre-set number of authorized users for your specific project space, including grouping them into different groups and granting them role-based access control. Beyond user management, you can also set security measures in your project space.
You can read more at https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143947032.
When to Consider Separate Project Spaces
Each project space is distinct and isolated, ensuring that data remains separate between different spaces unless explicitly shared by inviting users. This isolation enhances security, facilitates streamlined workflows, and allows teams to manage multiple projects independently without interference.
Although a single Project Space can accommodate multiple applications and segmented user groups, there are cases where splitting into separate Project Spaces is beneficial:
Testing / Training Needs | To ensure data integrity and security, you may want to split out your project spaces from live data and testing data. Many programs may have one project space set up for their live instance of CommCare, and use another project space for testing and training. |
Access Permission Concerns | If different teams or program administrators should not have access to each other’s data, separate Project Spaces ensure complete separation. |
Different Project Needs | You can manage different applications and programs within one project space, including setting different user permissions. However, there are things that all project spaces share, such as https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143955032, https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143955074 , Security Settings, at the Project Space level. If you are supporting different programs that have different needs for these, you may benefit from having multiple project spaces. |
Connecting Project Spaces
While project spaces are separate by default, certain features allow limited connectivity between them:
Linking Project Spaces | Organizations can create a parent-child structure where a parent space distributes applications or configurations to child spaces. This may be useful for managing global vs. country-specific applications. Multi-Environment Release Management or Enterprise Release Management (ERM) is the solution for organizations that need centralized control, version consistency, and structured updates across these spaces, ensuring seamless deployments while minimizing disruptions. Learn more at https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143955665 or https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143955137 |
Application Copying & Sharing | Applications can be copied from one project space to another, enabling reuse while keeping data separates. Learn more at https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143955454 |
Multi-Space Reporting | Data from multiple project spaces can be consolidated externally (e.g., in Power BI or Tableau) using https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2198503499 . Additionally, External tools can pull or push data between multiple project spaces using CommCare’s https://dimagi.atlassian.net/wiki/spaces/commcarepublic/pages/2143957366 |