Overview
This workflow handles Biz Daemon permission alerts by checking the device, presenting a handling choice, and routing the case to remote help or on-site follow-up. It supports a repeatable response path for permission exceptions and ends with a final administrator update when on-site feedback is available.
The Problem This Workflow Solves
Teams responsible for monitored devices need a clear way to respond when Biz Daemon permissions are switched off. They must confirm the alert details, check whether the device is online, choose the right handling path, and follow up after on-site work when remote handling is not enough.
- Clearer triage. The workflow checks the alert details and device status before a handling choice is made.
- Defined handoff. It sends a targeted email and form to the administrator or on-site technician.
- Follow-up visibility. It sends a final result after the on-site technician submits feedback and the system rechecks permissions.
Who This Is For
- Device operations teams. They need a structured way to handle Biz Daemon permission alerts on monitored devices.
- Administrators with response responsibility. They receive the alert, choose the handling method, and review the follow-up message.
- On-site technicians. They receive the task when remote handling is not enough and submit the result after checking permissions.
What Sets This Workflow Apart
- Event validation. The workflow rejects alerts that lack device information, permission details, or a matching status.
- Conditional handling choices. It offers remote handling only when the device is online and the link can be generated.
- Timed follow-up. It waits for a technician response, then pauses briefly before rechecking permission status.
- Branch-specific results. It returns different end states for invalid alerts, no submission, remote handling, and completed follow-up.
How It Works
- Read and verify the alert
- The workflow reads the Biz Daemon permission alert, checks the device and affected permissions, and rejects unsupported events.
- Check device context
- It queries the device status, records the enrollment type, and decides whether remote handling can be offered.
- Wait for the administrator
- The workflow sends an email and waits up to 72 hours for the administrator to choose a handling method.
- Route the chosen path
- It opens the remote handling branch, sends an on-site technician task, or ends if no action is selected.
- Collect on-site feedback and recheck
- If on-site handling is used, the workflow waits for a result, pauses briefly, and checks Biz Daemon again.
- Send the final result
- The workflow emails the administrator with the follow-up conclusion or ends earlier when the branch is incomplete.
What You'll Need
- Alert source and valid device data
- The workflow needs a Biz Daemon permission alert with device information, affected permissions, and a matching deactivation status.
- Notification recipients
- You must enter valid administrator and on-site technician email addresses before the workflow runs.
- Authorized AirDroid Business and email connections
- The workflow needs working AirDroid Business access for device queries and a Gmail connection for email delivery.
How to Use
- Step 1. Configure the alert
- Step 2. Enter recipient addresses
- Step 3. Connect the required services
- Step 4. Link the template and run it
- Step 5. Review the follow-up email
Set the Biz Daemon permission switch status alert to watch all permissions and trigger when the status is off.
Add the administrator and on-site technician email addresses so the workflow can send the correct handling forms.
Make sure AirDroid Business device access and Gmail sending credentials are available for the workflow.
Attach this template to the alert, then let the administrator choose a handling method when the email arrives.
After on-site feedback and the later permission recheck, review the final result sent back to the administrator.
