Root Access Model And Composite Profiles
Understand how Noderax models elevated access and how composite profiles simplify repeated operational choices.
Root Access Model And Composite Profiles
Root access in Noderax is an explicit operational policy surface.
Direct flags
The system can model low-level root capability directly, but direct flags become hard to reason about at scale.
Composite profiles
Composite profiles package root-access expectations into operator-facing choices. This keeps the dashboard and node policy flow easier to audit than a loose set of independent toggles.
Operator-visible profiles include off, operational, task, terminal,
operational_task, operational_terminal, task_terminal, and all.
Root access influences terminal capabilities, package actions, diagnostics actions, and any other node-side workflow that needs privilege.
Composite profiles make privileged behavior legible. They let operators reason about access intent without hand-assembling a matrix of low-level flags.
Why it matters
Root access influences:
- terminal capabilities
- package actions
- certain bootstrap and diagnostics flows
- operator expectations when targeting nodes
The recommended pattern is to use composite profiles where possible and reserve ad hoc overrides for deliberate exceptions.
Root access is not merely cosmetic gating in the UI. The product treats it as an operational policy that must reconcile across API intent, agent-applied state, and surface-specific action checks.
Tasks, Packages, Schedules, And Notifications
Coordinate operational work across nodes with tasks, package actions, schedules, and outbound notifications.
Terminal Sessions And Transcript Behavior
Open browser terminals safely, understand reverse session flow through the agent, and know what transcript retention means operationally.