Organize your integration assets by use case, department, app, or process, and control who has access to them. A project is like a repository for your integration assets. A project holds the related set of assets for your integrations, including recipes, connections, and subfolders.
You can view the integration assets from the Project view, as demonstrated in the screenshot below. The Project view also contains Smart folders, which enable you to view a list of the recipes or connections that you have access to.
A project can contain the following assets:
- Folders and subfolders
Connections can be shared across multiple Projects.
# Best practices for using projects
- Organize the projects in your workspace by department, use case, or project. For example: Example of organizing by use case
- Recipe Lifecycle Management: Before you import a project into the target workspace, check that the target workspace has a project into which you can import the exported project.
If there isn't a target project, create one with the same name as the exported project. Then import the project into the newly-created target project.
Otherwise, if you choose to import into the All projects destination, each folder will be converted into a separate project and the root-level assets will be imported into the Home assets project.
# Home assets
If your workspace existed before the projects feature was introduced, a Home assets project is automatically created in your workspace. For users with assets in the Home folder, those assets will be migrated to the Home assets project. Users who do not have assets in the Home folder, will have an empty Home assets project, which they can delete if they have the necessary permission.
The Home assets project is not automatically created in new workspaces.
When importing assets via Recipe Lifecycle Management: If you select the All projects import destination and the import package contains assets at the root level, those root-level assets will appear in the Home assets project. If the workspace does not have a Home assets project, it will be automatically created.
# Smart folders
Smart folders show you only the assets you want to see. You can see all the recipes or connections that you have access to, or narrow the list to only active recipes, recently stopped recipes, or connected connections.
# Setting up and working with Projects
As an Admin, you must give users permission to create/edit/view/delete specific projects by assigning them the admin, analyst, or a custom role. See projects permissions.
When a user receives access to a project, they also gain access to the recipes, conenctions, and folders in that project.
As a user with access permission, you can:
# Create a project and folder
Create a project to organize the integration assets for a department or use case.
Since recipes and connections must be stored in a folder of a project, the following steps walk you through the process of creating both a project and a folder.
Create a new project by doing either of the following:
- In the Projects menu, click Create project.
- In the All projects page, click Create project. Create project
Enter a name for the project and optionally a description.
Click Create project. Your new project appears in the All projects menu. Next, create folders to organize the assets in the project.
Create a new folder in the new project by doing either of the following:
- In the Create recipe drop-down menu, click Create folder.
- In the Project view, click Create folder.
Enter a name for the folder and select the project name in the Location field.
Click Create folder. The new folder appears in the All projects menu, as a sub-folder of the project. Next, create more folders in the project, or proceed to creating recipes and connections.
# Move assets (folders/recipes/connections)
You can move folders, recipes, and connections across projects or to other folders. Drag the asset to the desired location. Dependencies are resolved automatically after a resource is moved.
Move recipe to different folder
# Delete a project
You can only delete a project with no active assets.
When you delete a project, the connections are removed permanently and the recipes are saved to the trash folder. You can restore the recipes by restoring the deleted project, or you can restore a recipe to a new project.
If you delete a connection that is used in other projects, that connection dependency is removed from those projects too.
Delete a project by doing either of the following in the All Projects page:
- Drag the project to the Trash folder in the Projects menu. Delete by dragging the project
- Click the ellipses in the top-right of the project, then click Delete project. Click Delete