mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #2393] [Feature Request] - Automatic Site Assignment for Agents Based on Domain #3415
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#3415
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pyvnoaim on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2393
Is your feature request related to a problem? Please describe.
When deploying a new agent to a client PC via the agent deployment link, there’s no automatic way to assign it to the correct site based on the client’s domain. This requires manual sorting of agents into the appropriate site or creating a lot of unique links for each customer, which is time-consuming and error-prone.
Describe the solution you'd like
Add a “Domain” field to each site. When a new agent is deployed, Tactical RMM would detect the agent’s domain and automatically assign it to the corresponding site. This ensures agents are properly grouped without manual intervention.
Describe alternatives you've considered
Additional context
This would streamline onboarding for new clients, reduce errors, and save time for MSPs managing multiple sites.
@P6g9YHK6 commented on GitHub (Jan 21, 2026):
have a task running as onboarding asking the api to move the current agent to a new site :3