Platform / In development
A connected view of services, people, and operational context.
Vantage is developing a client and MSP operations platform that relates service scope to devices, knowledge, support, and commercial activity. The goal is a clearer path from a question to the records and people needed to resolve it.
Service relationships, illustrated. Not live monitoring.
Begin with the client’s work.
A client workspace should make it easier to understand subscribed services, find relevant support, and review commercial information without navigating provider-only administration.
The design connects service details, support requests, reports, and billing context. A proposed interaction is not a completed production workflow; existing account access continues through the current client sign-in.
Read health alongside freshness and coverage.
Device context is useful when it explains what was observed, when it was observed, and which part of the estate it represents. A connected provider and an up-to-date device observation answer different questions.
The existing RMM source includes cached health information. The platform direction builds on that distinction so a successful connection is not mistaken for a fresh result or a completed remediation.
Make knowledge and support easier to navigate.
A guide can help someone understand a process; a support request can carry the context when that process needs assistance. The platform direction relates knowledge, service context, and support without treating every question as an isolated ticket.
Native portal knowledge tools and OPS_SRC KB workspace access are distinct. Workspace provisioning, an enabled user, and successful sign-in remain separate requirements from a subscription.
One provider account. Distinct client responsibilities.
An MSP manages its own operational account and serves separate clients. A client, a service instance, a connected provider, and an individual user are different records with different responsibilities.
The developing model keeps those relationships explicit. Provider integration administration and credentials belong to operator workflows, not public marketing or a shared customer view. Actual access is determined by implementation and grants, not a role label in a concept.
Keep the agreement attached to the work.
Service, order, quote, billing, and support records should explain how an engagement fits together: what was requested, what was agreed, and what still needs a decision.
Portal source work covers these areas, while production parity and individual end-to-end flows require their own verification. A page or status label alone does not establish an order, payment, provisioning result, or entitlement.
Explore the direction with a real use case.
Durable operational workflows and real-time operator views are development goals, not a delivery-date commitment. Bring a use case such as reviewing a device issue, coordinating an approved change, or giving a client access to service information.
A useful platform discussion starts with the people involved, the decisions they can make, and the evidence each needs to see.
A clearer view of the work ahead.
Discuss your needsQuestions & answers
Does RMM health mean the information is live?
Not necessarily. The existing RMM source includes cached health information. Check the last successful observation, the resources included, and the source of the result. A connected provider or a refreshed page does not by itself establish fresh device data.
Does an active KB subscription mean every user can sign in?
No. Workspace readiness, an appropriately enabled user, and the sign-in prerequisites are separate from subscription status. Confirm those requirements and the effective workspace entitlement before assuming access is available.
Is the platform preview a production service?
The platform is in development. A preview explains the proposed client and MSP experience; it is not proof of production parity, a completed workflow, a live connection, or a delivery date. Use the current client sign-in for existing account access.
Is an MSP account the same as a client workspace?
No. The provider account, each client, individual service instances, users, and provider connections are distinct relationships. A proposed role label or connected tool does not establish a client's entitlement or a person's access.