Read accepted scope
The published VM Start with Managed OS schedule gives the customer root access and application responsibility, and assigns specified OS and VM work to Novasean. Check the accepted matching order.
Check the accepted order and support terms before assigning firewall, package or deployment work. Use an agreed application-scoped agency account; other services or exceptions may set different permissions.
Virtualizor lists possible end-user controls, but visibility in a panel is not a substitute for the contract. A button shown in software documentation does not establish entitlement or the safe person to use it.
Comparing Novasean services before an order? Review the VM Start + Managed OS configuration and service documents, then check which operating-system tasks are included and which application tasks remain with your team. The accepted order and terms govern the service you receive.
Identify the people and assets
Record the customer organisation, named application owner and substitute, Novasean support contact, domain controller and any separate mail or external-service owner. The agency normally owns application code, content, releases and compatibility tests. The operator owns the OS and platform work specified in the accepted schedule; check that schedule for application and web-stack scope. A domain registrar, CDN or third-party mail sender may sit outside both hosting accounts and needs its own named owner.
Keep this list in the handover record and update it when staff or agencies change. A former contractor’s access should be reviewed through the account owner and operator, not assumed to expire with a web-host move.
Route a privileged change with a test and rollback
For a firewall rule, OS package, PHP-FPM configuration, backup restore or VM resize, describe the intended outcome, affected site, maintenance window, risk and application test. Ask the named operator to confirm whether the request falls within the purchased scope. If it does, agree who performs the change, who tests the application and how to reverse it. If it does not, obtain a separate scoped decision before work begins. Do not exchange a root password or turn a deployment account into a general administrator to work around the boundary.
For application-owned changes, the agency can use the agreed deployment path and its least-privilege credentials, then record the release and smoke test.
Illustrative change request: specify the VPS ID, proposed OS package change, application owner, maintenance window and rollback plan. Ask who performs the OS step and who tests the application under the accepted order.
Check access and recovery after handover
Test that the agency can deploy the intended application files without accessing other accounts or changing system services. Confirm the operator can perform the agreed platform checks and that the support route reaches a named team. A backup entitlement, restore request or response window must be taken from the actual accepted terms; this guide does not create one. Record any exception, expiry and access removal date.
If the provided permissions are too broad or too narrow, pause the handover and ask support to reconcile the service record rather than sharing credentials informally.
Customer root access does not make an agency's deployment account an administrator. Agree application permissions and managed OS coordination separately.
Frequently asked questions
Can I use root on VM Start with Managed OS? The published schedule says the customer retains root access. Check the accepted order and coordinate changes affecting the agreed OS work.
Who fixes a broken application after an OS patch? The operator and application owner should compare platform evidence and application tests under their agreed responsibilities, then decide a safe rollback or fix together.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.