EloView Deployment Best Practices for Enterprise Users

This article outlines best practices for deploying content, OS updates, and account-wide changes in EloView to ensure stability and performance across large device fleets.

Deployment Limits

• Limit deployments to 5,000 devices or fewer per action.
• Use Filters or Groups to segment deployments.

Deployment Timing

• Allow at least 5 minutes between deployment actions.
• For Scheduled Content:
  • Separate start times by at least 5 minutes

OS Update Best Practices

• Keep devices on the latest EloView version.
• Always test updates before full rollout.
• Apply updates in batches of ≤ 5,000 devices.

Account-Wide Changes

• Changes apply immediately to all devices.
• Perform updates during non-peak hours:
  • 11 PM – 5 AM
  • Prefer weekends
• Allow 5 minutes between changes.

Bulk Operations Guidelines

• Do not run bulk operations from multiple browsers or machines.
• Maintain a 5-minute gap between operations.
• Notify support with:
  • Action type
  • Number of devices
  • Scheduled time

Monitoring & Validation

• Review Activity Logs after:
  • Content deployments
  • OS updates
  • Account-wide changes
• Report any issues to support immediately.

Performance Best Practices

• Wait for devices to fully load after login.
• Use portal navigation instead of browser back/refresh.
• Submit actions once and wait for confirmation.

Advanced Controls

Batch Approvals

• Restrict how many devices users can target per action.
• Prevents accidental large-scale deployments.

API Automation

• Coordinate with Elo before implementing automation.
• Follow best practices to avoid system strain.

EloView Account Setup & Scaling Guide

This article provides best practices for setting up, managing, and scaling EloView accounts in enterprise environments.

Account Setup Best Practices

Use a Generic Admin Email

• Create a shared admin account (example: eloviewadmin@yourcompany.com).
• Ensures continuity when personnel changes occur.

Device Licensing

• Each device requires a license.
• Maximum: 30,000 devices per account.
• Monitor under: Accounts → Account Settings.

Scaling Options

Sub-Accounts (Recommended)

• Extend capacity under a primary account.
• Share users across accounts.
• Centralized license management.

Secondary Parent Accounts

• Create a new account using a different email.
• Use only if Sub-Accounts are not feasible.

Content Management

• Maximum upload size: 500MB per file.
• Contact support for larger content packages.

User Roles & Permissions

• Assign permissions based on least access required.
• Available roles:
  • Admin
  • Registered User
  • Viewer

Reset Exception Feature

• Preserves application data during Enterprise Reset.
• Recommended for enterprise deployments.

Monitoring & Logs

• Review Activity Logs regularly.
• Validate system behavior after major changes.

Reporting Issues

• Use the Software Bug Reporting Form for suspected bugs.
• Provide detailed information:
  • Organization name
  • Admin email
  • Device serial numbers
  • Description of issue

Contact Support

• 📧 support@eloview.com
• Provide:
  • Organization name
  • Action details
  • Device count
  • Scheduled timing