Projects and sharing
Personal vs shared Projects, member roles, and how to move an app between Projects.
A Project is the space your apps and their case data live in. Every account starts with one personal Project: a private space that's just you, and you can create shared Projects to collaborate with teammates.
Personal Projects are private
Your personal Project is yours alone. The apps and case data in it are visible only to you, and it can't be shared: there's no way to invite anyone to it. To work with other people, you move an app into a shared Project and invite them there.
Shared Projects
Create a shared Project from the Project switcher at the top of the page. In a shared Project you can invite teammates (Dimagi email addresses only), and everyone in the Project sees the same apps and the same case data. What each member can do is set by their role:
| Role | What they can do |
|---|---|
| Viewer | Open and preview the Project's apps and case data. No edits. |
| Editor | Build and edit the Project's apps and case data. No member management. |
| Admin | Everything an Editor can do, plus invite members, change their roles, and remove them. |
| Owner | Whoever created the Project, everything an Admin can do, plus renaming the Project. Can't be removed. |
Deleting a Project isn't available to anyone yet, including its Owner. A Project holds apps, case data, media, Project data tables, and conversation history, and Nova won't offer a single control that removes all of it until that lifecycle is fully audited. Move or delete the apps you no longer want instead.
If someone changes your role while an app is open, Nova pauses editing and refreshes the app and your access together. Changes that were already waiting to save stay in that browser tab. They resume saving automatically if your current role can edit; with Viewer access, they remain paused while you can continue exploring and previewing the app. If your access is removed entirely, Nova closes the workspace instead of showing data from a Project you can no longer view.
Moving an app between Projects
On the home page, each app card has a Move to another Project control. Pick a destination and choose Move app: Nova moves the app in one protected operation, so it either arrives complete or stays exactly where it was.
You'll see the control when you're an Admin or Owner of the Project the app is in, and the destination list shows only the other Projects where you hold Admin or Owner access too. If you don't have that access on both ends, the move isn't offered.
What moves with the app
Everything Project-scoped travels with it:
- the app itself and its full edit history,
- its case data,
- its media (logos, images, audio), and
- its chat conversations, including files attached in chat.
Everyone in the destination Project can see all of it, at whatever their role allows, so treat a move as sharing that data with those members.
When a move waits
- A Solutions Architect run is in progress. An app being built or edited can't move; try again once the run finishes.
- Someone still has the app open in an older browser tab. Nova asks you to have them refresh first, so no one is left editing an app that has moved out from under them.
- Every Owner of the current Project must already be a member of the destination. This keeps an app from moving somewhere its Owners can't follow.
Apps that use Project data tables can't move yet, those shared tables would be left behind. Nova blocks those moves rather than splitting an app from its data.