How Netxus fits together

Netxus brings financial planning, purchasing, delivery and IT operations together for one Organization. Each business Module owns its records. Core supplies shared access and coordination; Personal Workspace keeps an individual's private work separate.

These guides explain the current product workflows. Your installation may run an earlier release or have different licensed Modules, permissions and integrations. Use the controls actually available in your installation; contact your administrator when a documented workspace is absent. This public website does not connect to your installation or display its records.

Choose the record's owner

WorkspaceUse it for
CoreUsers, Groups, Roles, organizational Positions, licensing, logs, search and notifications.
Personal WorkspaceYour encrypted Notes, Tasks and Calendar events.
Key ManagementShared credentials, private keys and certificates, with separately authorized reveal.
FinancialBudget Requests, Budget Codes, approval policy, funding and actual spend.
ProcurementSuppliers, sourcing, Agreements, Purchase Orders, Delivery Notes and commercial payments.
Project ManagementProject charters, participating Teams, work items, milestones and Scrum delivery.
Asset ManagementEquipment identity, serials, models, installed hardware and lifecycle.
Facilities ManagementSites, Equipment Rooms, Racks, room layouts, placement and recorded capacity.
Structured CablingPanels, endpoints, physical connections, patch routes and termination history.
HostingCompute platforms, Hosts, workloads, placement and capacity.
NetworkNodes, members, interfaces, addressing, topology and discovery review.
Service MonitoringAvailability checks, device performance, logs, traffic summaries and incidents.

Follow a connected journey

  1. Prepare and approve funding in Financial. Where the funding-handoff feature is available, an authorized Project user explicitly creates or links a Project from the approved offer.
  2. Record delivery accountability in Project Management, and prepare purchasing and receiving evidence in Procurement.
  3. Accept each eligible delivered unit into Asset Management by registering a new Asset or linking the correct existing one.
  4. Record the physical placement in Facilities, the connection in Cabling, and any compute or connectivity role in Hosting or Network.
  5. Configure Monitoring to observe the relevant service or device. Review observations and incidents without treating them as changes to inventory.

The result is connected evidence with clear owners. These are deliberate handoffs, not an automatic chain: approving funding does not create a Project, a Delivery Note does not itself create an Asset, and a Monitoring observation does not reconfigure its target. Work can also begin in an individual Module without completing this whole journey.