Project Catalogs
Overview
The Project Catalogs section is used to manage data catalogs assigned to a specific Project within the DataFloem platform.
While the global Catalogs Module defines top-level logical containers for schemas, namespaces, and tables, those catalogs must first be assigned to a Project before they can be utilized by the Jobs, Code Flows, or SQL Queries within that specific Project.
When a new Project is created, its Catalog list is empty. Users with appropriate permissions can assign required pre-registered catalog configurations to the project scope or unassign existing ones as needed.
Access Requirements
To access and manage this page, the user must have the required management permissions for the specific Project and its associated Catalogs.
Users without the required permission cannot view this page and will receive an authorization error. Users with access can monitor their permission level via the Access Status column for each assigned catalog.
Managing Project Catalogs
This page displays all Catalogs currently assigned to the Project.
From this page you can:
- View all assigned Catalogs and their default warehouse mappings.
- Search and filter the assigned Catalog list.
- Assign existing global Catalogs to the project using the Assign Catalog button.
-
Remove (unassign) Catalogs from the project using the action menu (
...). - Toggle between list and grid views for optimal layout visibility.
Catalog Information Table
The table displays the following information for each assigned Catalog:
| Column | Description |
|---|---|
| Access Status |
Indicates whether the project has been successfully granted access
to use this catalog (e.g., Granted).
|
| Name |
Displays the unique identifier and display name of the catalog
(e.g., Catalog1).
|
| Description | Contextual description outlining the purpose or target scope of the catalog. |
| Default Warehouse |
The target warehouse assigned to execute queries and manage
storage for this catalog (e.g.,
s3://test,
Test Warehouse).
|
| Create Date | Timestamp indicating when the catalog was created. |
| Update Date | Date and time when the catalog assignment or configuration was last updated. |
| Status |
Operational status of the Catalog (e.g.,
Active).
|
| Actions (...) |
Action menu (...) allowing users to
perform project-level actions such as Unassign.
|
Key Features & Actions
Assign Catalog
Clicking the Assign Catalog button opens the catalog assignment interface where you can select and link pre-configured global Catalogs to the current project.
Unassigning a Catalog
Selecting Unassign from the action menu (...) removes the Catalog connection from the current project scope. This
action does not delete the global Catalog configuration from the platform;
it only revokes its availability for the current project.
Notes
- Assigning a catalog to a project links an existing global catalog configuration to the project scope; it does not create a new catalog instance.
- Unassigning a catalog only removes it from the current Project's scope. It remains available in the global Catalogs Module for other projects.
-
Ensure that assigned catalogs have an Access Status of
Grantedand an operational Status ofActiveto prevent execution errors in project workflows.