Project / application actions

Legacy projects.*, applications.*, environments.* actions, dashboard aggregates, and migration helpers.

Written By Zoro

Last updated 3 days ago

dFlow is moving customers from legacy Projects to Applications and Environments.

Server actions still use Payload collections named projects and services alongside applications and environments. Names below match actionName metadata and getActionAccess in packages/core/src/lib/permissions/config.ts.

Legacy Projects (Payload `projects`)

Primary implementation: packages/core/src/actions/project/index.ts. Dashboard aggregates: packages/core/src/actions/pages/project/index.ts.

`actionName`	`Permission keys (from getActionAccess)`
`createProjectAction`	`servers.read`, `projects.create`
`updateProjectAction`	`projects.update`
`deleteProjectAction`	`projects.delete`, `services.delete`
`getProjectDatabasesAction`	`services.read`
`getProjectDetails`	`projects.read`, `services.read`
`getProjectBreadcrumbs`	`projects.read`

createProjectAdminAction exists in project/index.ts for operator-style creation; confirm current RBAC in code if you rely on it.

Applications

Primary implementation: packages/core/src/actions/application/index.ts.

`actionName`	`Permission keys (from getActionAccess)`
`getApplicationsAction`	`applications.read`
`getApplicationByIdAction`	`applications.read`
`getApplicationByMigratedProjectIdAction`	`applications.read`, `projects.read`
`createApplicationAction`	`applications.create`
`updateApplicationAction`	`applications.update`
`deleteApplicationAction`	`applications.delete`
`activateApplicationFlowAction`	`applications.update`, `environments.update`, `projects.read`, `projects.delete`, `services.update`
`setDefaultEnvironmentAction`	`applications.update`
`migrateProjectToApplicationAction`	`projects.read`, `projects.delete`, `services.read`, `applications.create`, `environments.create`, `applications.update`, `services.update`
`migrateProjectServicesToApplicationAction`	`projects.read`, `projects.delete`, `applications.update`, `services.update`
`getEnvironmentForProjectComputeAction`	`projects.read`, `environments.read`

Customer docs: Migrate from legacy Projects to Applications under Migration and Release Notes in the sidebar.

Environments

Primary implementation: packages/core/src/actions/environment/index.ts.

`actionName`	`Permission keys (from getActionAccess)`
`createEnvironmentAction`	`environments.create`
`updateEnvironmentAction`	`environments.update`
`deleteEnvironmentAction`	`environments.delete`
`getEnvironmentByIdAction`	`environments.read`
`getEnvironmentServiceDeploymentSummariesAction`	`services.read`
`getEnvironmentServiceDeploymentSummariesBatchAction`	`services.read`
`checkEnvironmentComputeReachabilityAction`	`environments.read`
`getEnvironmentComputeLiveStatsAction`	`environments.read`
`checkApplicationComputeReachabilityAction`	`applications.read`

Dashboard cross-cuts

`actionName`	`Permission keys (from getActionAccess)`	Notes
`getProjectsAndServers`	`servers.read`, `projects.read`	`pages/dashboard/index.ts`
`getDashboardOverview`	`projects.read`, `services.read`	`pages/dashboard/index.ts`

Learn more

Applications overview and Environments overview
Legacy Projects vs Applications
Service actions for workloads inside an Environment.