Vianordis
--:--:-- UTCVianordis / SUPPORT
business

Nodus

Available

Nodus gives sales and account teams a shared view of contacts, companies, opportunities, and follow-up activity. Use it to keep customer information current, track pipeline movement, and coordinate relationship work across the team.

Verified user manual

Nodus user manual

Manage accounts, contacts, leads, opportunities, pipeline stages, and customer activity in the Nodus 2.0 CRM workspace.

Manual
Version 1.0
Product
Nodus 2.0.0
Verified
July 15, 2026
Language
English · Source
Owner
Nodus product and support
Source
nodus-v2 · 0cc9186
Review cycle
90 days
Start here

Audience, scope, and prerequisites

Covers the Nodus browser workspace for customer records, pipeline work, activities, search, reports, and the optional read-oriented assistant. It excludes database administration and direct API integration.

Who this is for

  • Sales and account users
  • CRM operators
  • Managers and administrators

Before you sign in

  • A Nodus entitlement in the correct tenant
  • An agreed record-ownership and data-quality policy
  • Approval before importing, deleting, or exporting customer data
Access model

Roles and responsibilities

RoleAccessResponsibilities
ReaderView tenant CRM records and related activity.
  • Use records only for an approved business purpose
  • Report incorrect or over-broad visibility
WriterCreate and update accounts, contacts, leads, opportunities, and activities.
  • Search before creating records
  • Maintain ownership, status, and next actions
Operator or administratorAccess management surfaces such as Reports and controlled delete operations.
  • Review metrics and sensitive changes
  • Apply retention and correction procedures
Workspace map

Navigation

Dashboard

/dashboard

Review CRM metrics and recent work.

Search

/search

Search across supported CRM records.

Accounts

/accounts

Manage organizations and their related records.

Contacts

/contacts

Manage people and account relationships.

Leads

/leads

Qualify prospective customer records.

Pipeline

/pipeline

Review opportunities by pipeline stage.

Opportunities

/opportunities

Manage active commercial work.

Activities

/activities

Record calls, meetings, tasks, and follow-ups.

Reports

/reports

Review management reporting when the role permits.

Chapter 01

Create and maintain customer records

Search first, use a stable account as the relationship anchor, and avoid duplicate people or organizations.

Procedure 1.1

Create an account and contact

Create the organization first and link the person to it.

ForWriter
  1. 1
    Search for existing records

    Search by organization name, domain, email, and contact name.

  2. 2
    Create the account

    Open Accounts, select New account, and enter the approved identifying and ownership fields.

  3. 3
    Create the contact

    Open Contacts, select New contact, and choose the existing account from the picker.

  4. 4
    Review relationships

    Open the account and contact detail pages and verify each linked record.

  5. 5
    Add the next activity

    Record the next call, meeting, or follow-up from the related record.

Expected result

One account and one correctly linked contact exist with an accountable owner and a visible next action.

Procedure 1.2

Create and qualify a lead

Track an unqualified prospect until it is ready for the governed conversion or opportunity process.

ForWriter
  1. 1
    Open Leads

    Search for the person or company before selecting New lead.

  2. 2
    Record source and owner

    Enter the known identity, company, source, consent context, and responsible user.

  3. 3
    Set an accurate status

    Use the tenant’s agreed qualification status rather than optimistic placeholders.

  4. 4
    Log qualification activity

    Record the conversation or task that supports the status.

  5. 5
    Review before progression

    Confirm account/contact matching and required fields before creating an opportunity or using a conversion action.

Expected result

The lead shows its source, owner, qualification state, and supporting activity without duplicating an existing customer record.

Chapter 02

Manage opportunities and pipeline

Pipeline data is useful only when value, stage, ownership, timing, and activity remain current.

Procedure 2.1

Create an opportunity

Link commercial work to the correct account, contact, pipeline, and stage.

ForWriter
  1. 1
    Open Opportunities

    Select New opportunity from the list or Pipeline page.

  2. 2
    Choose the account

    Select an active account; then choose a related contact when available.

  3. 3
    Set pipeline details

    Enter a meaningful name, pipeline, stage, value, owner, and expected close information.

  4. 4
    Save and open the detail

    Verify the linked account, contact, stage, and displayed value.

  5. 5
    Log the next activity

    Create a dated follow-up related to the opportunity.

Expected result

The opportunity appears in its selected pipeline stage with correct relationships and a traceable next action.

Procedure 2.2

Update pipeline stage and status

Move work only when the stage’s business criteria are met.

ForWriter
  1. 1
    Open Pipeline

    Locate the opportunity in the current stage or open its detail page.

  2. 2
    Review evidence

    Check recent activities, expected value, close date, and decision state.

  3. 3
    Change the stage

    Use the supported board or edit flow and select the stage that matches current evidence.

  4. 4
    Update related fields

    Correct probability, timing, ownership, or status when the stage change requires it.

  5. 5
    Record the reason

    Log an activity or note so reviewers can understand the change.

Expected result

The opportunity appears in the correct stage and the record explains why it moved.

Chapter 03

Record activity and review performance

Use activities as the durable chronology and reports as a review tool, not as a substitute for record verification.

Procedure 3.1

Log and complete an activity

Associate each call, meeting, task, or follow-up with the most relevant record.

ForWriter
  1. 1
    Select New activity

    Start from Activities or a related account, contact, lead, or opportunity.

  2. 2
    Choose the relationship

    Confirm the preselected record or choose the correct related item.

  3. 3
    Enter subject and timing

    Record an actionable subject, type, owner, due time, and required context.

  4. 4
    Save or complete

    Keep future work open; mark completed work accurately when finished.

  5. 5
    Verify chronology

    Open the related record and confirm the activity appears in its history.

Expected result

The activity is visible on both its detail page and the associated customer or opportunity record.

Procedure 3.2

Review dashboard and reports

Use filtered reporting to identify records that require action or correction.

ForManagerOperator
  1. 1
    Confirm reporting scope

    Verify tenant, period, ownership, pipeline, and filters.

  2. 2
    Review dashboard metrics

    Identify unexpected totals, stalled stages, or missing activity.

  3. 3
    Open Reports

    Use the management surface only when the operator role exposes it.

  4. 4
    Inspect source records

    Open a sample of contributing records before acting on an aggregate.

  5. 5
    Assign corrections

    Update ownership or create follow-up activity rather than editing metrics directly.

Expected result

The review produces traceable follow-up work and verified corrections to source CRM records.

Operating rules

Security and data handling

  • Keep personal and commercial data within the correct tenant.
  • Search before creating records and use approved correction or merge procedures for duplicates.
  • Grant writer or operator access only to users with a business need.
  • Verify filters and authorization before exporting or sharing CRM data.
  • Do not enter secrets, payment credentials, or unnecessary sensitive personal data into notes.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Nodus 2.0.0 scope and must be rechecked when the product changes.

  • Reports and delete operations are role-gated and may not appear for standard users.
  • Pickers load a bounded set of active records; search or data cleanup may be required before a relationship can be selected.
  • Ask Nodus is primarily read-oriented and cannot replace source-record review.
  • No automatic duplicate merge workflow was verified in the current 2.0 interface.
Problem solving

Troubleshooting

You cannot sign in to Nodus

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

An account or contact is missing from a picker

Likely cause: The record is inactive, outside the loaded result set, in another tenant, or the picker request failed.

  1. Open the source list and confirm the record and status.
  2. Search by exact name and verify tenant ownership.
  3. Reload the form after the source list succeeds; do not create a duplicate as a workaround.

An opportunity is absent from the expected pipeline stage

Likely cause: The wrong pipeline or stage is selected, a filter hides it, or the update did not complete.

  1. Open the opportunity directly and review pipeline and stage fields.
  2. Clear board filters and reload once.
  3. Record the ID and error before repeating a stage update.
Escalation

Contact support

Contact support when

  • A repeatable Nodus error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • A duplicate cannot be corrected without losing history
  • Pipeline totals or reports remain inconsistent with verified source records

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
Contact support