Introduction to Projects
- What are projects?
- Project identification
- Permissions
- The active project
- Creating resources in a project
- Next steps
What are projects?
A project is a group of resources, such as connections or rulesets. For example, you might organise all resources used by one department in your organisation into a project named after that department.
Each of these resources belongs to one project, and can be moved between projects by the user:
- database and file connections
- connection filesets, Oracle wallets and Snowflake keys
- table references
- rulesets and ruleset libraries
- discovery configurations and discovery config libraries
- ruleset generation configurations
- seed files
Runs also belong to a project, but cannot be moved by the user. A run belongs to the project of its ruleset (for masking runs) or its discovery configuration (for discovery runs). A discovery run with no discovery configuration belongs to the project of its connection.
Built-in seed files belong to no project. They can be used in every project.
At least one project must always exist; you cannot delete the last project on a DataMasque instance.
You can manage all projects and resources on the instance through the Projects and Resources page.
Project identification
Project names
A project's name:
- can be up to 255 characters long, and can contain any printable Unicode characters, including spaces
- cannot be a single dot
. - cannot contain
/or.. - must not start with
DataMasque_, ignoring case - must be different, ignoring case, from the name of every other project
Characters outside plain ASCII, such as accented letters, symbols and non-Latin scripts, count as more than one character towards the 255-character limit.
Project names are not case-sensitive, so a project called Sales cannot coexist with one called sales.
A ruleset refers to a resource in another project as <project>/<name>
(see References Across Projects).
Project IDs
Each project has a unique ID (a small integer),
which can be used to identify it when using the API.
You can also specify the ID in slug form, which looks like <id>-<normalized name>, for example 10-sales.
You will see this form in page URLs when a project is selected in the project selector
(see The active project below).
Only the ID part is actually used; the name part of the slug is for display purposes only, and is ignored by the API.
Permissions
Projects only organise resources. A user's role gives them the same access in every project, so projects cannot be used to control who can see or use a resource.
- Every user can see every project.
- Only administrators can create, rename and delete projects.
- Administrators and Mask Builders can use the Projects and Resources page and move resources between projects. Moving a ruleset library or discovery config library also needs the Manage Ruleset Libraries permission (see Permissions).
The active project
The Active project selector at the top right of each page shows the project you are working in. Click it to choose another project, or All projects.

List pages, such as Database Masking, Ruleset Libraries, Files and Run Logs, show only the active project's resources. Under All projects, they show the resources of every project, with a label beside each name showing its project. When the instance has only one project, the project labels are hidden.

Built-in seed files are always shown in every project, with a Global label.
DataMasque remembers the project you choose in your browser. It also adds the project to the address of each list page, so a link or bookmark opens the same project.
On an editor or detail page, choosing another project does not change the page. The selection applies starting from the next page you open. Instead, an editor or detail page for a saved resource shows its project beside the page title. You can click on the project name, which takes you to the Projects and Resources page with that resource selected (see The Projects and Resources page).

Note: The selector is locked to All projects on the Projects and Resources and Audit Logs pages, as these pages have their own filtering options. It is also disabled for any pages that are not project-related, such as Settings.
Creating resources in a project
When you create a connection, ruleset, library, table reference or other resource, or upload a file, you must choose its project in the Project field.

The field is initially set to the active project, or the only project on the instance if there is only one. If the project selector is set to All projects and there's more than one project on the instance, it starts empty and must be filled in.
A ruleset generated from a discovery run starts in the project of that run.
The edit page of a saved resource shows its project in the Project field, which cannot be changed.
To change the project, click the move
icon at the right end of the field
(see Moving Resources).
Next steps
- Perform the post-upgrade steps on the Upgrading to Projects page.
- Manage projects on the Projects and Resources page.
- Move resources between projects.
- Learn how to reference a resource in another project.
- Import rulesets and libraries into their projects from an export.