Skip to content

Deprecating network_users #320

@lupael

Description

@lupael

Refactor Directive: Deprecating network_users

Context

We are refactoring our Multi-Tenancy & Role System. The term network_users is officially deprecated and must be replaced with Customer.

The Critical Shift

Historically, "Customer" was incorrectly treated as a "Level 100" operator. We are moving to a strict 11-role administrative hierarchy (Levels 0-80).

  • Customers are now defined as external subscribers (Internet/PPP/Hotspot/CableTV).

  • Customers do not have a hierarchical level and are removed from the administrative tree.


Objectives

  1. Rename & Purge: * Replace all instances of network_users with Customer (and network_user_id with customer_id) across the database schema, models, controllers, and API routes.

  2. Role Isolation: * Strip Customer of all management capabilities.

    • Ensure the Customer model does not inherit from administrative classes or traits (e.g., HasPermissions, IsOperator).

  3. Validation Logic: * Operators (Level 30) and Sub-Operators (Level 40) manage Customers as assets/subscribers, not as sub-admins.

    • Block all Customer access to administrative dashboards and management API endpoints.

    • The roles table must stop at Level 80 (Staff). Customers must be identified by a type flag or a specific is_subscriber boolean rather than a level.


Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions