Virima Self-Service Portal: Features & Capabilities

The Virima self-service portal gives end users, IT teams, and stakeholders direct access to the infrastructure data Virima already maintains — configuration items, asset records, service dependencies, and discovery results — without routing every lookup through a ticket. Features and capabilities span CI search, asset record visibility, ViVID™ service map access, and request submission that flows into your existing ITSM platform with full infrastructure context attached.

The portal isn’t a standalone product. It’s the access layer on top of the Virima platform — automated hybrid discovery, an always-accurate CMDB, and ViVID service mapping working together — so the data people see when they self-serve reflects the real, current state of your environment. And because Virima integrates with ServiceNow, Jira Service Management, HaloITSM, Ivanti, Xurrent, and Hornbill, the portal complements your ITSM self-service experience rather than replacing it: users find what they need faster, and the requests they do submit reach IT with the CI, dependency, and ownership context already attached.

This page walks through what the Virima self-service portal includes, what end users and IT admins can do with it, how it fits into the broader platform, and how it connects to the ITSM tools you already run.

What the Virima self-service portal is

The Virima self-service portal is an access surface on the Virima platform — the place where end users, IT practitioners, and stakeholders can directly query the configuration data Virima already maintains. Instead of opening a ticket every time someone needs to know who owns a server, what an application depends on, or whether a service is healthy, they go to the portal and look it up themselves.

Behind the portal is Virima’s automated discovery and always-accurate CMDB, continuously updating CI data across hybrid environments — on-premises systems, cloud platforms, virtualized infrastructure, and containers. Every record someone pulls up in the portal reflects what’s actually deployed, not a snapshot from the last manual update.

Virima’s portal complements your ITSM self-service portal — it doesn’t replace it. ServiceNow, Jira Service Management, HaloITSM, and other ITSM tools continue to own ticket workflows, service catalog, and approvals. The Virima portal sits alongside them as the infrastructure visibility layer.

Who the Virima self-service portal is for

The portal is designed around three audiences with different needs.

End users and stakeholders. Employees, application owners, and business users who need to look up an asset, check ownership, view a service map, or submit a request without filing a generic ticket and waiting for an IT analyst to surface the right context.

IT practitioners and operators. Engineers, IT operations teams, and SREs who use the portal to search the CMDB, pull dependency maps, check discovery results, and investigate operational events without jumping between tools.

Asset and configuration managers. The people responsible for keeping the CMDB accurate, the asset register clean, and audits passing. The portal gives them quick access to lifecycle data, ownership records, and configuration details across the environment.

Access is role-based, so each audience sees only what’s relevant to their work.

Key features of the Virima self-service portal

The portal exposes the Virima platform’s data through a focused set of features.

CI search and lookup Search the CMDB by CI name, type, owner, application, or service. Results return live records pulled from automated discovery — not stale entries from a manual import.

Asset record access View full asset records— hardware, software, license entitlements, contracts, and lifecycle information — for assets within a user’s role-based scope.

ViVID™ service map viewing Open service maps that visualize how applications, services, and infrastructure relate. Maps display dependencies, recent changes, open incidents, pending changes, and known vulnerabilities mapped to the specific CI each one affects.

Request submission with infrastructure context Submit a request — access, change, report — and the portal attaches the relevant CI, dependencies, owner, and recent change history before the request reaches your ITSM platform.

Status visibility See open incidents, pending changes, and operational events on the assets and services a user is associated with.

Role-based access controls Configure who sees what. End users see assets and services in their scope. Operators see broader CMDB and service data. Auditors see lifecycle and ownership records.

What end users can do in the portal

For a typical end user, the portal removes the “open a ticket to ask a question” loop. They can find a CI or application without knowing the exact name by searching by owner, service, or tag. They can see what assets and services they’re associated with as owner or user. They can open a service map to understand what an application depends on before requesting a change. They can submit a request — access, change, report — that arrives at the IT team with CI, dependency, and ownership context already attached. And they can check the status of an existing request or a service they rely on.

The outcome is fewer routine tickets, faster answers, and IT requests that land with enough context for an agent to act on immediately.

What IT admins and operators can do in the portal

For IT operators and admins, the portal is a fast lookup and triage surface. They can pull CI records and dependency maps without opening the full Virima console. They can publish curated service maps to stakeholders so business owners see their applications. They can configure role-based access so end users get the right scope of visibility. They can expose discovery data to requesters, so requests arrive with infrastructure context. And they can cross-check operational events — open incidents, recent changes, vulnerabilities — against the CIs they affect.

The admin view is also where ITSM integration behavior is configured: which requests route where, what context attaches automatically, and how the portal connects to the rest of the service stack.

How the Virima self-service portal connects to your ITSM platform

Virima doesn’t replace your ITSM platform. ServiceNow, Jira Service Management, HaloITSM, Ivanti, Xurrent, and Hornbill continue to own ticket workflows, service requests, approvals, and the ITIL processes your service desk runs on. What Virima does is enrich the data those workflows depend on — and the self-service portal is one of the places that enrichment shows up.

When a user opens the Virima portal to find a CI, view a service map, or submit a request, they’re working against live data from Virima’s automated discovery and CMDB. If they submit a request — say, access to a server, a change to an application, or a report of a degraded service — the request flows into your ITSM platform with the configuration item, owner, dependencies, and recent change history already attached. The ITSM agent picking up the ticket doesn’t have to chase context. It’s already there.

A concrete example: an employee submits a request to access a reporting application. Virima’s portal captures the request, attaches the application’s CI record, its upstream and downstream dependencies from the ViVID service map, the application owner, and any recent changes or open incidents pulled from your ITSM tool. That packaged context lands in ServiceNow (or Jira Service Management, HaloITSM, etc.) as a ticket the agent can resolve without three rounds of clarifying questions.

The division of responsibility looks like this:

The two portals work side by side. Users go to the ITSM portal for service catalog requests and knowledge base articles. They use the Virima portal — or the Virima context surfaced inside the ITSM portal via integration — when they need to see what’s actually there: which CI is affected, what depends on it, who owns it, what changed recently. That separation is deliberate. ITSM platforms are built for service management. Virima is built for infrastructure visibility. The integration is what makes both better.

For the full list of supported ITSM platforms and how each integration is configured, see Virima’s ITSM integrations page.

How the portal fits into the broader Virima platform

The portal is the visible part of a deeper stack. Underneath it, four layers do the work.

Hybrid IT discovery runs continuously across on-premises systems, cloud platforms, and distributed infrastructure using agentless discovery, agent-based discovery, and API integrations. It finds what’s there.

The Virima CMDB receives that discovery data and maintains an always-accurate record of every configuration item, application, service, relationship, and dependency in the environment.

ViVID™ service mapping turns the CMDB into visual service dependency maps and overlays them with operational context — open incidents, recent changes, pending changes, and vulnerabilities — pulled through Virima’s integrations with ITSM tools and NIST NVD.

The self-service portal is the access layer on top of all three. Every CI lookup, asset record, and service map a user sees in the portal is fed by the platform underneath.

This is why the portal is more than a UI. It’s the surface where complete IT visibility, dependency awareness, and operational accuracy become directly usable by the people who need them.

Use cases and outcomes

Faster incident response Engineers self-serve CI lookups and ViVID dependency maps during an active incident instead of waiting for someone to dig through the CMDB on their behalf. Time to root cause drops, and MTTR drops with it.

Reduced change risk Requesters see the full blast radius on a service map before submitting a change. Approvers see the same context attached to the request when it reaches ITSM. Fewer changes get approved without visibility into what they touch.

Audit readiness Asset records, CI data, ownership, and lifecycle information are accessible through the portal — useful for internal compliance reviews and external audits where evidence of infrastructure control is required.

Lower help desk load
One of the most measurable outcomes of the Virima self-service portal is its impact on help desk volume. When end users can look up CI ownership, see service dependencies, or check the status of a known incident on their own, the routine tickets that flood most service desks — “who owns this server,” “is this app down,” “what changed last night” — never get filed in the first place.

Combined with the request-with-context flow that pipes remaining tickets into your ITSM platform pre-enriched, IT teams resolve faster and field fewer escalations.

For a broader look at the strategies IT leaders use here — including knowledge base optimization, request automation, and shift-left — see our guide on how to reduce IT help desk tickets.

Frequently asked questions

Q: What is the Virima self-service portal?

The Virima self-service portal is an access layer on top of the Virima platform that lets end users, IT teams, and stakeholders look up configuration items, view asset records, explore ViVID service maps, and submit requests directly — without filing a ticket for routine information. It sits on top of Virima’s automated discovery and CMDB.

Q: What features does the Virima self-service portal include?

Core features include CI search and lookup, asset record access, ViVID service map viewing, request submission with infrastructure context attached, and role-based access controls. Requests submitted through the portal flow into your existing ITSM platform — ServiceNow, Jira Service Management, HaloITSM, Ivanti, Xurrent, or Hornbill — pre-enriched with CI and dependency data.

Q: Does Virima replace ServiceNow’s self-service portal?

No. Virima does not replace ITSM self-service portals. ServiceNow, Jira Service Management, HaloITSM, and other ITSM tools continue to own service catalog, ticket workflows, approvals, and ITIL processes. Virima’s portal is a complementary visibility layer that surfaces accurate CMDB, asset, and dependency data, and routes context-rich requests into your ITSM.

Q: Who can use the Virima self-service portal?

The portal is designed for three audiences: end users who need to look up assets, ownership, or service status; IT practitioners and operators who run CMDB queries and service map lookups; and asset and configuration managers who need lifecycle and audit data. Access is role-based, so each audience sees only what’s relevant.

Q: How does the Virima self-service portal integrate with ITSM tools?

When a user submits a request through the Virima portal, it flows into the integrated ITSM platform with the relevant configuration item, dependencies from the ViVID service map, owner information, and recent change history attached. ITSM agents receive tickets pre-enriched with infrastructure context, reducing back-and-forth and time to resolution.

Q: How is the Virima self-service portal different from a generic IT self-service portal?

Generic IT self-service portals typically pull from static CMDBs or rely on user input to identify assets. The Virima portal pulls live data from automated hybrid discovery and an always-accurate CMDB, so every lookup, service map, and request reflects the real current state of the environment — not what someone manually entered six months ago.

See the Virima self-service portal in action

The Virima self-service portal gives your IT organization a way to put accurate infrastructure data in front of the people who need it — without expanding ticket queues or routing every question through a service desk analyst. End users get answers. IT teams field fewer interruptions. ITSM workflows get richer context. And the platform underneath — discovery, CMDB, and ViVID service mapping — keeps the data current so the portal stays useful.

Book a demo to see the portal in action, or explore the rest of the Virima platform: ViVID service mapping, Virima CMDB, ITSM integrations.