# MSP HUB Autom Mate introduces a major evolution in multi-tenant automation management — redefining how Managed Service Providers (MSPs), administrators, and technicians operate across distributed customer environments. The **MSP Hub** now serves as a central command center that unifies control, visibility, and governance across all tenants, technicians, and resources — ensuring security, scalability, and operational excellence. This release brings end-to-end enhancements across tenant management, technician experience, AI Agent integration, dashboard visibility, and license enforcement — making Autom Mate’s multi-tenant architecture truly enterprise-grade. *** ## **What is MSP Hub and Why It Matters** The MSP Hub is the control layer for multi-tenant environments, enabling a single MSP or organization to manage multiple customer workspaces (tenants) under one unified platform. Each tenant operates in full isolation, with its own users, Automations (Automs), dashboards, and data.\ The MSP Hub bridges these separate worlds, giving administrators complete oversight while preserving strict data boundaries. The result is a **secure, modular, and highly maintainable automation ecosystem** where MSPs can: * Manage hundreds of tenant environments from one interface. * Delegate operational access to technicians safely. * Monitor tenant activity and license consumption in real time. * Enforce data isolation and compliance automatically. This design significantly reduces overhead for service providers and ensures reliability, even at massive scale. *** ## **MSP Admin Role** The **MSP Admin** is the highest authority within the Autom Mate environment. This role has full control over all tenants, technicians, dashboards, and system configurations — functioning as the central administrator for every managed environment. The MSP Admin role is **protected by default**: it cannot be deleted, modified, or reassigned. This protection ensures system integrity across all tenant structures and prevents accidental privilege mismanagement. #### Core Responsibilities The MSP Admin oversees: * Creation, update, and deactivation of tenants * Technician assignments and permission management * Dashboard creation, duplication, and cross-tenant monitoring * Brand and identity management (logos, themes, corporate colors) * AI Agent and Vault access policies * MSP license verification and tenant usage tracking When an MSP license is activated, the system automatically upgrades the existing “Administrator” user to “MSP Admin.”\ At that moment: 1. The platform displays an **MSP License Activation Notice**, 2. A **Default Tenant** is created automatically, 3. All relevant records are linked to tenant-aware contexts. This streamlined process ensures the MSP environment is fully ready for multi-tenant operations from the first moment of activation. *** ## **Technician Management and Experience** Technicians are the operational backbone of MSP environments — the users responsible for executing automation, monitoring alerts, and maintaining tenant systems. In version this version, the entire technician lifecycle has been redesigned for clarity, isolation, and ease of use. ### Creating a Technician Technicians are created and managed directly from the **Technician Management Page** in MSP Hub.\ Each technician record defines: 1. Personal information (name, contact details, login credentials) 2. Tenant assignments (which customers they can access) 3. Role-based permissions per tenant (view, create, update, delete) ### Access Control and Visibility Technicians can only view and act on resources within their assigned tenants: * They see dashboards, alerts, and Automs belonging to those tenants only. * Cross-tenant access is blocked by default. * Sensitive operations (like API key generation) are disabled for technician-level accounts. This model enforces strong **Role-Based Access Control (RBAC)** while maintaining an intuitive workflow. ### Seamless Tenant Switching Multi-tenant operations often require rapid context changes. With **Tenant Switch**, technicians can now move between tenants instantly — no logout, no session loss. A new **searchable dropdown menu** in the sidebar lets users switch tenants on the fly. The system updates context automatically, refreshing dashboards, permissions, and data views based on the selected tenant. This feature dramatically increases productivity for technicians handling multiple client environments. *** ## **Tenant Management** Tenant management in Autom Mate has been rebuilt from the ground up for automation, performance, and compliance. The **Tenant Management Page** allows MSP Admins to create, configure, and monitor all tenants from a single control surface. ### Tenant Creation and Configuration Creating a tenant is now a one-click process. The system automatically: * Assigns a unique tenant ID * Links the tenant to its license configuration * Initializes default tables and permissions ### Tenant Visibility * MSP Admins have full visibility across all tenants. * Technicians see only their assigned tenants. * The tenant list supports search, pagination, and the new **Sort By** capability for large-scale deployments. ### Role and Access Control Tenant-level roles are completely independent. System roles (MSP Admin, Technician) remain hidden within tenant environments — ensuring that tenant administrators cannot modify or override MSP-level permissions. ### License and Limit Enforcement Tenant licenses are now validated dynamically. Each tenant’s Autom, user, and resource limits are monitored in real time. When limits are exceeded, the system automatically halts new Autom creation and alerts administrators. This preserves fairness, prevents resource exhaustion, and simplifies license compliance across all tenants. *** ## **AI Agent and Vault Management** AI and automation now operate under strict tenant boundaries. All AI Agents and Vault credentials are **tenant-scoped** by design. ### Vault Service Each tenant’s Vault content is fully isolated. Technicians or agents cannot access credentials outside their assigned tenant. MSP Admins, however, can review Vault configurations centrally for governance and auditing. ### AI Agent Architecture * Every AI Agent record includes a `tenant_id`. * MSP Admins and Technicians see only tenant-relevant AI Agents. * Agent services, migrations, and duplication workflows have been updated to respect tenant boundaries. This structure eliminates data leakage risks and enforces airtight separation of knowledge and automation logic across tenants. *** ## **Dashboards and Reporting** The dashboard system has been re-engineered to deliver **tenant-specific analytics, faster rendering, and cross-tenant visibility** for MSP Admins. #### Key Improvements * **Dashboard Duplication:** Clone existing dashboards to other tenants effortlessly. * **Tenant Summary Service:** Generate consolidated reports showing performance, usage, and Autom activity per tenant. * **Tenant-Based Filters:** Dashboards now automatically filter results to match the selected tenant. These features turn the MSP Hub into a true **analytics hub**, giving administrators actionable insights at scale. *** ## **Licensing and Access Governance** Licensing now integrates deeply with tenant information. Every license check includes tenant context to prevent misconfiguration or overuse. The new **Tenant Count Feature** displays real-time tenant usage under the MSP license, making it easy to monitor allocation and limits. If any tenant exceeds its allocated Autom or user quota: * Autom creation is paused automatically. * The system issues a clear, descriptive warning. * Administrators can expand the license or adjust tenant limits to continue. This ensures full alignment between contractual licenses and technical enforcement — reducing audit friction and preventing misuse. *** ## **Branding and White-Label Management** MSP Admins can now customize the Autom Mate environment with their own branding elements. Through the **Logo Upload and Update Service**, administrators can: * Upload a custom logo directly from the Hub interface. * Apply it globally across login, dashboard, and tenant views. * Maintain consistent branding across all customer portals. The system automatically embeds the new logo into the JWT configuration, guaranteeing seamless integration across tenants — a perfect fit for MSPs operating under white-label agreements. *** ## **Security, Isolation, and Compliance** Security in Autom Mate is not a feature — it’s an architecture. Every interaction, dataset, and service call now operates under strict tenant isolation rules. * Each tenant’s data (Vault, AI Agent, Autom, Alerts, and Users) is fully segregated. * Backend APIs perform tenant-aware data retrieval exclusively. * Cross-tenant operations are programmatically impossible. * The MSP Admin role is immutable and fully protected by the system kernel. This isolation model aligns with **GDPR**, **SOC 2**, and enterprise compliance frameworks, ensuring customer data remains protected and auditable at every layer. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.autommate.com/userguide/product-features/msp-hub.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.