Which role can configure access to beta features in Mosyle?

The primary administrator holds the highest level of authority within the Mosyle management framework and is responsible for defining and managing overall system configurations, including access to beta features. This role is crucial in determining which users can utilize new or experimental functionalities that are not yet fully released. By allowing the primary administrator to configure access, Mosyle ensures that these features are managed by someone who has a comprehensive understanding of the organization's needs and how these beta features can affect the environment.

In contrast, the secondary administrator typically has limited permissions compared to the primary administrator and may not have the authority to alter settings related to beta features. Meanwhile, end users are usually granted limited access based on their roles and cannot make administrative changes. Technical support is generally focused on providing assistance and troubleshooting, rather than configuration tasks related to system features. Therefore, the primary administrator is the logical choice for managing access to beta features within the Mosyle ecosystem.