Community Ideas

As an MSP, we’d like to request support for white labeling the Senteon Agent to improve user trust and reduce the likelihood of removal by end-users who recognize the branding as associated with external or unfamiliar organizations. Requested Features: Custom App Icon: Allow administrators to change the Senteon icon (as seen in the Windows Apps & Features list) to a custom logo. Custom App Name: Enable renaming of the Senteon Agent app in the installed applications list to reflect an MSP-specific or customer-specific name. Custom Service Name: Allow renaming of the underlying service from "Senteon Agent" to a white-labeled name that aligns with our branding. Use Case: End-users often uninstall or distrust applications they recognize as not being part of their own organization. Custom branding will improve retention and user confidence in the agent, especially in multi-tenant environments. Impact: Reduces accidental removal Increases end-user trust Enhances MSP service branding

Summary: Enable a native integration between Senteon and Hudu to sync endpoint data and/or generate automated executive summary reports, with direct links to Senteon for deeper visibility. Use Case: Many MSPs rely on Hudu as a centralized knowledge base and documentation system. Integrating Senteon would bring endpoint health and security data directly into the tools technicians already use on a daily basis. Currently, we use a custom PowerShell script to generate reports about Senteon data in Hudu—this could be streamlined and made more reliable with native support. There are many ways to build a native integration with Hudu, and working with the Hudu team would likely be the best route to establish best practices, but here are some ideas: Sync endpoint-level data into Hudu assets (matching by serial number) Auto-generate daily executive summary reports per client in Hudu (basic HTML) Embed links in the Hudu assets that go to the Senteon portal for full detail views Impact: Brings Senteon data into the MSP’s daily operational workflow Improves client reporting, documentation, and technician efficiency (can add Hudu assets to client portal) Enhances visibility AND USAGE of Senteon across the service team Example Scenario: A technician investigating a device in Hudu could instantly see the latest Senteon findings linked directly within the asset entry—no need to context switch. Meanwhile, account managers could review a daily updated summary of client security posture directly from Hudu.

It would be nice to have the ability to pull the reports via API.

Currently, when a user is invited, they are given access to no tenants by default. The admin cannot assign any tenant permissions until the user is fully provisioned—that is, until they have accepted the invite and completed signup. As a result, when users log into the Senteon portal for the first time, they see nothing and must reach out to the admin to gain access. Request: Allow tenant access to be configured during the user invitation process, using a table interface similar to the existing Edit Permissions screen (which is currently only available after the user is fully provisioned). This should include: A list of all tenants The ability to select/exclude individual tenants or all tenants via a "Select All" option Optional role/permission assignment per tenant (if applicable) These settings would be automatically applied once the user completes their signup. Benefit: Prevents user confusion and support tickets immediately after signup Mirrors an already familiar interface (Edit Permissions), reducing dev and UX overhead Consolidates onboarding steps for admins Enables more secure, intentional, and scalable user provisioning

Create Tenant For GET/Tenant - Would it be possible to add an XUID for cross platform integration, with the ability to POST to this as well

Summary: Like the Endpoints screen, the Baselines screen could support an “All Profiles” view—at both the Global and Tenant level. Currently, baselines can only be viewed one profile at a time, which slows down review and editing. Why It Matters: We often manage multiple profiles per tenant. Having to switch between them adds unnecessary clicks. An “All Profiles” view with the Profile Name shown as a column would let us quickly see which baseline belongs to which profile, improving clarity and efficiency. Example: When auditing baselines, we want to see all profiles in one list and easily identify them via a Profile column—rather than clicking through each profile individually to find the baseline we need.

Summary: Enable API access to retrieve the tenant/baseline specific installation code and/or corresponding PowerShell one-liner used to deploy the Senteon agent. Use Case: Currently, the installation code is only accessible via the Senteon web portal. For MSPs, this limits automation. We want to dynamically pull and sync installation codes into our RMM to support automated deployments, just like we do with other tools in our stack. Impact: Prevents full automation of agent deployment Requires manual steps, introducing friction and human error Limits scalability and integration with existing deployment workflows Request: Add API endpoint or add data to an existing endpoint that allows the retrieval of the installation code and PowerShell command per tenant, so it can be integrated directly into RMM or scripting pipelines. Example Scenario: We deploy agents via our RMM using install scripts. Today, we have to manually copy the code from Senteon. With an API, we could programmatically inject the latest code into client-specific configurations as clients are onboarded.

Summary: Allow MSPs to rename an existing tenant in Senteon without deleting and recreating it. Use Case: Clients—especially law firms—frequently change names due to partner changes or rebranding. For example, "Henderson & Goldstein LLP" may become "Goldstein Legal LLP" after a partner departure. Our MSP has a standardized name change process across systems, but Senteon currently does not support tenant renaming, which creates inconsistency. Impact: Inconsistent naming across integrated tools (RMM, PSA, backups, etc.) Extra administrative effort and potential confusion in reporting Request: Add the ability to rename a tenant via the UI or API while preserving all associated data and configurations.

SSO please!

So that the same drifted settings that are corrected can be removed from cluttering the UI. Consider adding a counter for each unique alarm so that it shows up on the first occurrence.