Clarify onboarding workflow: agents land in queue, technician must audit and enroll before any activity
Some checks failed
Regenerate Documentation Index / regenerate-index (push) Failing after 7s
Some checks failed
Regenerate Documentation Index / regenerate-index (push) Failing after 7s
This commit is contained in:
parent
0969fee03e
commit
b6a6797b70
1 changed files with 8 additions and 5 deletions
|
|
@ -55,13 +55,16 @@ Supports x86_64, ARM64, and i686 architectures. Requires systemd.
|
|||
|
||||
## What Happens Next
|
||||
|
||||
Your computer will appear in our management system within a few minutes. From there, we can:
|
||||
After installation, your device is placed into our **onboarding queue**. It will not be actively managed right away.
|
||||
|
||||
- Monitor your computer's health (disk space, updates, performance)
|
||||
- Push security updates and patches
|
||||
- Provide remote support when you need help
|
||||
Here is what to expect:
|
||||
|
||||
You do not need to do anything else. The agent runs automatically in the background.
|
||||
1. Your device appears in our system and waits in the onboarding queue.
|
||||
2. A digiBandit technician reviews the device, confirms it is linked to your account, and audits its current state.
|
||||
3. Once verified, the technician registers the device and enrolls it in the appropriate services for your plan.
|
||||
4. From that point on, your device is actively managed: health monitoring, security updates, and remote support.
|
||||
|
||||
No automated changes, updates, or monitoring will occur until a technician has reviewed and approved the device. This ensures everything is set up correctly for your specific environment.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue