Feature Request: Support Project-Specific Notification Channels

What problem will this feature address?

Currently, notifications in Dokploy are configured globally and apply to all projects within an instance.

In environments with multiple projects, teams, or customers, different projects often need to send notifications to different channels. For example:

• Production applications → Production alert channel
• Internal tools → Engineering team channel
• Customer projects → Customer-specific channel

At the moment, all project notifications are routed through the same notification configuration, causing notifications from different projects to be mixed together. This makes it difficult to organize alerts, increases notification noise, and becomes challenging to manage as the number of projects grows.

Describe the solution you'd like

I'd like Dokploy to support project-specific notification channels.

One possible approach would be to allow notification providers to be assigned to specific projects.

For example:

• Notification Channel A → Project A, Project B
• Notification Channel B → Project C
• Notification Channel C → Project D, Project E

Alternatively, each project could have a Notification section where users can select one or more notification providers.

If no project is specified, the notification channel could continue to apply to all projects (current behavior).

This would make it much easier to manage notifications in multi-project, multi-team, and multi-tenant environments while reducing notification noise and improving alert organization.

Describe alternatives you've considered

Currently, the only workaround is to create separate Dokploy instances for different projects or teams so that each instance can have its own notification configuration.

Another option is to send all notifications to a single channel and manually filter or organize them based on project names. However, this quickly becomes difficult to manage as the number of projects increases.

I've also considered using external automation tools to route notifications to different destinations, but this adds unnecessary complexity and maintenance overhead for what could be handled natively within Dokploy.

Project-specific notification channels would provide a much cleaner and more scalable solution.

Additional context

No response

Will you send a PR to implement it?

Yes

Start by locating Dokploy's current global notification configuration and the project model or settings entry points that would need to reference providers. Compare the proposed assignment approaches and define how fallback to the current global behavior should work. Done should include project-specific routing, multi-project provider assignments, and coverage for the existing default behavior.