- Basics
- About Knox
- Knox licenses
- Knox white paper
- Sign up for Samsung Knox
- Latest release notes
- General Knox FAQ
- General Knox KBAs
- Submit a support ticket
- User Acceptance Testing
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Introduction
- Get started
- Features
- License management
- Release notes
- Troubleshoot
- Wearables
- Shared Device
- FAQ
- KBAs
- Mobile
- Knox Capture
- Welcome
- Overview
- How-to guides
- Manage licenses
- Scanning profiles
- Apps and activities
- Scan engine settings
- Keystroke output and data formatting
- Export configuration and deploy through EMM
- Set the camera scan trigger
- Connect a hardware scanner
- Configure the output path
- Check a configuration in test mode
- Use intent output
- Knox Capture AR
- Get started
- How-to videos
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Capture: Scandit Edition
- Introduction
- How it works
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Create a new profile
- Assign profiles to groups and organizations
- Enroll devices
- Shared Android device quickstart
- Non-shared Android device enrollment quickstart
- Android Management API device enrollment quickstart
- Apple User Enrollment quickstart
- View device information
- Apply profiles to organizations
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
Scanning profiles
Knox Capture acts as a wedge by translating barcode data into keystrokes that can be sent to a business application. But how does Knox Capture know what barcode types to scan, how to interpret scanned data, and which business applications to pass the data to? For Knox Capture, the Scanning profile defines the app's core behavior.
A Scanning Profile is a configuration file that gets created or modified by an IT admin using the Knox Capture application. The profile defines how Knox Capture performs a barcode scan, and primarily consists of the following parameters:
- Apps and activities — define which applications that can launch the Knox Capture scanner.
- Scanner engine settings — specifying the barcode technologies (QR, Code 128, UPCA, etc.), scanning methods (single barcode, multi barcode), and camera behavior (enable flash, allow camera zoom).
- Keystroke output rules — specifying how barcode data gets converted into keystrokes (append Tab or Enter character to each barcode, add prefix or suffix characters, convert output to hex characters, etc.)
About Default scanning profile
Out-of-the-box, Knox Capture includes a default scanning profile that gets automatically associated with all apps on the device. In other words, when Knox Capture is launched, any app can trigger the camera scanner and receive barcode data in the form of keystrokes. This makes it easy to use Knox Capture for basic scanning purposes without any additional setup.
When using the default scanning profile, IT admins can change the profile's scan engine settings and data processing rules, however they cannot change the default profile's apps and activities behavior. For example, an IT admin can modify the default profile to append a Tab key at the end of each barcode, but they cannot change which apps can trigger the scanner.
About Custom scanning profiles
While the default scanning profile allows Knox Capture to be used right away without any configuration, IT admins may want to use a custom profile to better suit their needs. With a custom profile, IT admins control which apps and activities can trigger a barcode scan.
Note — Any apps that you don't select in the custom profile will follow the default behavior in that the barcode scanner is active for all apps not specified in the custom profile.
Creating custom scanning profiles
Custom profiles can be created by modifying the default profile settings, or by creating entirely new profiles altogether.
- Tap the + button near the top of the app UI to open the profile creation options.
-
Select Create profile to start a profile from scratch, or select Duplicate existing profile to copy the settings from an existing (custom or default) profile.
- Alternatively, you can create a custom profile by clicking Create profile without clicking the + button.
- Provide a profile name, then tap Done. The new profile appears in the profiles area below Defult scanning profile.