Get started

Before you begin: obtain your Organization's Netxus installation address and account from its administrator. This documentation address is not your product sign-in page. Confirm which Group and Module you will work in.

Sign in and find your work#

1. Open the installation address, sign in with your Netxus username and password or your Organization's identity provider when offered, then enter an authenticator or recovery code if multi-factor authentication is enabled. Open Account security to turn on optional multi-factor authentication and store your recovery codes. Keep your login credentials separate from the Personal Workspace passphrase.
2. Open a Module from the navigation rail. Its submenu contains Dashboard and its working subjects; Dashboard summarizes that Module's authorized data.
3. If a Working Group selector appears, choose the intended Group before creating or changing a record. A selector can be omitted when only one Group is available.
4. Open the relevant subject and use its related tabs or table links. Search and filters help locate records; row Settings contains the supported actions for an existing record.

Expected result: the page shows the selected workspace and authorized Group. A record in another Group is not made accessible by guessing its address.

Save a change you can verify#

1. Use the creation action beside the owning table, or open the record's Settings and choose the required action.
2. Choose named catalog entries from the selectors. Check the selected record, Group, dates and units before submitting.
3. Wait for the success or error message. After success, verify the changed record in its table or detail page. Typing into a field alone does not save it.
4. If the page says the record changed, refresh and review the latest values before starting a new action. If a failed request retains a reviewed retry, use that retry rather than creating duplicate records.

Understand an unavailable action#

A Module must be licensed and locally enabled, and you must hold the appropriate Role capability and record scope. Group membership alone is insufficient. When the license has expired or has not been verified recently, Modules can become read- and export-only: records stay readable, but changes, jobs, discovery, monitoring and integrations pause. The Protected Administrator manages the platform but observes ordinary business records read-only.

An empty table, an unavailable service, a restricted peer record and an unconfigured observation mean different things. Read the displayed state; do not treat missing data as zero or delete related records to bypass a blocker. When requesting help, provide the Module, action, time and visible error, without passwords, secret contents or private record exports.