Overview
Swif provides customer support for device management, policy enforcement, enrollment, compliance, Live Terminal, Remote Desktop, and other MDM-related workflows.
Because Swif is an MDM platform, some support scenarios may require privileged access to the Swif control plane or customer-approved access to an enrolled device. This article explains when Swif support may access your organization, who can provide support, and how customer permission is handled.
Who Provides Swif Support
Swif support access is limited to a small group of authorized personnel, including:
Swif CEO
Swif CTO
Swif MDM engineers
These team members help customers troubleshoot device enrollment, policy behavior, compliance reporting, agent behavior, and remote support workflows.
When Swif Accesses a Customer Organization
Swif support only accesses a customer organization when the customer specifically requests help.
Examples include:
A customer opens a support ticket
A customer asks Swif to investigate a device issue
A customer requests help debugging an MDM policy
A customer asks Swif to assist with enrollment or unenrollment behavior
A customer requests Live Terminal or Remote Desktop troubleshooting
Swif does not log in to customer organizations without customer permission.
Customer Permission Requirement
Swif support access is permission-based.
Before accessing a customer organization or device for troubleshooting, Swif requires a customer request or explicit approval through an approved support channel, such as:
Intercom
Email support
Slack support channel
Scheduled support call
Written approval from a customer administrator
Support access is used only for the issue the customer asks Swif to investigate.
What Swif Support May Do During Troubleshooting
Depending on the support request, Swif support may review or assist with:
Device enrollment status
Device check-in status
Policy configuration
Policy deployment results
Compliance status
Device command history
Agent logs or diagnostics
Live Terminal sessions, when approved
Remote Desktop sessions, when approved
For example, if a customer asks Swif to troubleshoot why a Linux device is not applying a policy, Swif support may review the device record, inspect relevant policy settings, and request logs or Remote Terminal access to debug the issue.
What Swif Support Does Not Do
Swif support does not:
Access customer organizations without permission
Open Live Terminal sessions without customer approval
Start Remote Desktop sessions without customer approval
Make unrelated policy changes outside the requested support scope
Browse customer data unrelated to the support request
Perform enrollment, unenrollment, lock, wipe, or other high-impact actions unless requested or approved by the customer
Live Terminal and Remote Desktop Access
Live Terminal and Remote Desktop are powerful troubleshooting tools.
Swif support will only use these tools when:
The customer requests troubleshooting help
The customer approves remote access
The access is needed to investigate the reported issue
These tools are typically used for cases such as:
Agent service debugging
Linux authentication troubleshooting
Policy enforcement verification
Enrollment or unenrollment diagnostics
Log collection
Configuration validation
Customers can end the support session or revoke access at any time.
High-Impact Device Actions
Some MDM actions can affect device availability, user access, or data security.
Examples include:
Lock device
Wipe device
Unenroll device
Remove management profile
Push security policy changes
Reset passwords
Run commands through Live Terminal
Swif support will not perform these actions unless they are part of the customer-approved troubleshooting request or explicitly approved by the customer administrator.
Recommended Customer Approval Format
For clarity, customers can approve support access using a message like:
I authorize Swif support to access our Swif organization to troubleshoot [issue description]. Approved scope: - Device(s): [device name or serial number] - Action(s): [review logs / inspect policy / use Live Terminal / use Remote Desktop] - Time window: [date and time range]
For high-impact actions, use explicit approval:
I authorize Swif support to perform the following action on [device name]: [approved action] This approval is limited to troubleshooting [issue description].
Auditability
Swif device actions and commands are visible in the Swif console where applicable.
Admins can review device command activity from:
Device Details > Commands
This helps administrators confirm what actions were sent to a device and whether they succeeded or failed.
Customer Control
Customers remain in control of their Swif environment.
Administrators can:
Decide when to request Swif support
Define the troubleshooting scope
Approve or deny remote access
Limit support to specific devices
Ask Swif support to stop an investigation
Review device command history
Swif support access is intended only to help resolve customer-reported issues.
Security Notes
Swif support access is limited to authorized Swif personnel.
Swif does not proactively log in to customer organizations.
Swif does not access managed devices without customer permission.
Live Terminal and Remote Desktop are used only when requested or approved.
High-impact device actions require customer request or approval.
Summary
Swif support may assist with privileged MDM troubleshooting, but only when requested by the customer.
Swif does not access customer organizations or enrolled devices without permission. Support access is limited to authorized Swif personnel and is used only to resolve the issue the customer asks Swif to investigate.