Managing Projects
The Projects and Resources page
To see the resources of every project in one list, click Projects and Resources under Manage in the sidebar. Only administrators and Mask Builders can use this page.
Each row shows a resource's type, name and project.
Built-in seed files are listed with a Global label.
To open a resource, click the edit
icon at the end of its row.
A file has a view icon instead, which opens the file on the Files page.
A library that you do not have permission to edit also has a view icon, which opens the library read-only.

To move resources to another project, select them with the checkboxes and click Move to project… (see Moving Resources).

Filtering and searching
- In the Project filter, choose the projects to show, or Global for built-in seed files.
- In the Type filter, choose the type(s) of resource to show.
- In the Search resources by name field, type something to filter the resources by name. Put a phrase in double quotes to match the whole phrase. This filter is not case-sensitive.
The filters are saved in the page's address, so you can bookmark or share a filtered view.
Create a project
Only administrators can create projects.
- On the Projects and Resources page, click New project….
- Enter a name and, optionally, a description, then click Create.
The name must follow the rules in Project names.
Rename a project
Only administrators can rename projects.
- On the Projects and Resources page, click Manage projects….
- In the Manage projects dialog, click the edit
icon beside the project. - Change the Name or Description, then click Save.

Renaming a project does not update references to it, such as Sales/phone_masks.
Bare names within the project still work.
See Renaming a project for what to update.
After the rename, each Git-synced resource in the project pushes to a new file under the new name, and the old file stays in the repository. Its auto-pull fails until you push it. A resource that still uses its file from before the upgrade keeps that file (see Git file locations). When the project has Git-synced resources, the dialog shows a warning, as in the example above.
The old name of a renamed project can be reused for another project.
Delete a project
Only administrators can delete projects. Deleting a project does not delete the resources in the project. Instead, all of its resources move to another project that you choose.
At least one project must always exist; you cannot delete the last project on the instance.
Important: Deleted projects cannot be restored.
To delete a project:
- On the Projects and Resources page, click Manage projects….
- In the Manage projects dialog, click the delete
icon beside the project. - In the Move resources to field, choose a destination project.
- Type the project's name to confirm, then click Delete.

When the project is deleted:
- Its resources and their runs move to the destination project (see Moving Resources).
- Deleted resources, and their runs, stay with the deleted project.
- References to the deleted project, such as
Sales/phone_masks, are not updated. You will need to edit any rulesets, discovery configurations, and so on that refer to the old names. - The deleted project's name can be used for a new project. Any reference that still names the deleted project then refers to the new project.
- The project's files in Git stay in the repository. A resource in a new project of the same name cannot auto-pull until you push it, and its push replaces the file.
Conflicts preventing a project from being deleted
When you choose the destination project, DataMasque checks that every resource can move into it. You cannot delete a project if the destination project already has a resource of the same type and name as one of the resources in the project being deleted. Rename one of them, or choose another destination.

The move can also fail because of files on disk:
- The destination project already has a file on disk where one of the resource's files would move to. Contact DataMasque support for assistance.
- The project being deleted has a file that belongs to none of its resources. Remove it from the DataMasque files directory on the host, then delete the project again.