Nexus SoftSphereDocumentation
Documentation › Nexus BSS/OSS › Securing

Securing Nexus BSS/OSS

Roles, module permissions, and the API paths each permission governs.

How access is decided

Every request passes three gates, in order. A failure at any gate is a refusal, and a later gate never widens what an earlier one denied.

  1. Authentication — a valid session. See Identity and sign-in.
  2. Entity scope — the request is bound to the company the user is signed in to. Someone with access to two entities still cannot read across both in one call.
  3. Module permission — the role must grant the action on the module that owns the route, per the table below.
Granting Administration is not the same as granting every module. Administration governs users, roles and configuration; transactional modules are granted individually.

Module permission matrix

14 modules. The last column lists the API paths each module actually governs, taken from the enforcement map inside the application rather than from documentation.

ModuleKeyActionsGoverns
Customers & CRMcrmview create edit delete/customers /engagements
Product Catalogcatalogview create edit delete/plans
Orders & Fulfilmentordersview create edit delete/orders /prov
Servicesservicesview create edit delete/services
Billing & Chargingbillingview create edit delete/invoices /payments /fx /collections
Revenue Assurancerevenueview create edit delete/ra
Network Inventoryinventoryview create edit delete/sites /elements /ip-blocks
Gateways & Backbonepartnersview create edit delete/partners
NOC, Faults & Performancenocview create edit delete/alarms /metrics /network
Ticketing & Supportsupportview create edit delete/tickets
Field Servicefieldview create edit delete/workorders
Automation & AIautomationview create edit delete/automation /ai
Reports & BIreportsview create edit delete/reports
Administration & Settingsadminview create edit delete/users /settings /activity