Projects
Projects are the primary way to organize your integration assets in Adeptia, grouping related configurations and resources so they are easier to manage, share, and control access to.
What projects do
A project acts as a container for your integration work. By placing assets inside a project, you can apply consistent ownership and access rules across everything in that group, and you can navigate or search your assets more efficiently as your integration landscape grows.
Projects also connect to other platform capabilities. Each project can be associated with a dedicated queue for processing and a deployment, both of which are visible and navigable directly from the project details view.
Creating a project
When you create a project, you provide two pieces of information:
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Up to 30 characters; certain special characters are not permitted |
| Description | Yes | Up to 256 characters; certain special characters are not permitted |
The platform checks that the name you choose is not already in use before saving. If a duplicate is detected, the name field is highlighted with an error and focused so you can correct it before the project can be created.
Editing a project
You can update a project's name and description at any time. The same validation rules that apply when creating a project also apply when editing it, including the duplicate-name check.
Viewing project details
Selecting a project opens a details panel that shows:
- The project's unique identifier
- Its description
- Creation date and the user who created it
- Last modified date
- The dedicated queue associated with the project (clickable, navigates to queue management)
- The deployment associated with the project (clickable, navigates to deployments)
Managing partner access
You can control which partner networks have access to a project. The access management view lets you toggle access on or off for each partner individually. You can search partners by name or description, and switch between a tile view and a list view to find what you need quickly.
Moving project assets
When you need to reorganize, you can move project assets from one project to another. To do this, you select a target project and then choose a target user within that project who will take ownership of the moved assets. The user list is filtered to show only users who already have access to the target project.
Clearing configuration cache
If your project uses a secrets manager or a Git-based configuration repository, you can clear the cached configuration data for either or both of those integrations. This is useful when you have updated credentials or configuration values externally and want the platform to pick up the latest data without waiting for the cache to expire naturally.