DOCSEARCHbyAlgolia
Submit Docs

FydeOS Enterprise Policy Documentation

website·Indexed 33 days ago

https://enterprise.fydeos.com/wiki/

Enterprise policy guides for FydeOS, covering device and browser configurations. Includes documentation on network settings like DNS-over-HTTPS, system-wide tracing, high efficiency mode, and sign-in screen accessibility options such as screen magnifiers, dictation, and high contrast settings.

Tokens
138.7K
Snippets
294
Records
969
Agent score
52%

What's inside FydeOS

  2. Overview of Managed Guest Sessions

    Managed Guest Sessions provide a shared browsing environment controlled by enterprise policies. They are ideal for shared workstations, loaner devices, and reception computers where users do not need to log in with an enterprise account. Note: If the device should only run a single full-screen application, use Kiosk mode instead of Managed Guest Sessions.

  3. Overview of Open Network Configuration (ONC) in FydeOS

    Open Network Configuration (ONC) is a JSON-based format used by FydeOS (based on Chromium) to describe network settings including Wi-Fi, Ethernet, VPN, proxies, and certificates. These configurations are deployed via the FydeOS Cloud Management Platform under Business+ $\rightarrow$ Network Configuration to specific organizational units.

    Key Constraints:

    • Activation: Network restrictions take effect after the user logs in. They cannot be used for initial device registration or first-boot connectivity (which requires pre-configuration in the registration image or manual setup).
    • Case Sensitivity: ONC is case-sensitive for both field names and constant values (e.g., WiFi must not be written as wifi).
    • Compatibility: Supported fields depend on the Chromium ONC documentation and the installed FydeOS version. The management platform may reject fields not supported by the current validator or target OS version.

  4. Overview of the FydeSign digital signage workflow

    FydeSign is the digital signage process within the FydeOS cloud management platform. The recommended implementation sequence is: Register Device → Auto-launch FydeSign → Add Assets → Create Playlist → Assign Device → Verify Playback.

  5. FydeOS Cloud Management Platform functional overview

    The admin console is divided into the following functional areas:

    • Dashboard: Overview of the enterprise, licenses, devices, and quick-start guides.
    • Kiosk: Management of Kiosk images, applications, auto-start, and runtime settings.
    • FydeSign: Management of signage devices, asset libraries, playlists, and device assignments.
    • Business+: Policies for users, devices, guest sessions, applications, networks, and certificates.
    • Private Android Apps: Uploading and maintaining private APKs.
    • Devices: Basic device management, device overview, managed device lists, and registration images.
    • Organisational Units: Defining the scope for users, devices, applications, and policies.
    • Users: Managing members, invitations, join requests, roles, and OU assignments.
    • Enterprise Settings: Enterprise profiles, login security, and administrator roles.
    • Subscriptions: License counts, usage, availability, and renewal dates.
    • Notification Centre: In-platform and email notifications.

  7. Monitor enterprise status using the Dashboard

    The Dashboard provides a high-level overview of the enterprise environment. It displays the enterprise name, total member count, total device count, and the next billing date. Crucially, it shows the purchased, used, and available quantities for each license type. Administrators should check license availability before deployment to prevent device registration failures or incorrect license assignments.

  8. Understand FydeOS Business+ policy scopes

    Before editing policies, identify the correct scope to ensure changes affect the intended target:

    • Device Policies: Apply to the managed device itself.
    • User Settings: Apply to enterprise users who have logged in.
    • Guest Session Settings: Only effective within that specific guest session.

  9. Manage User-Agent Client Hints via UserAgentClientHintsEnabled policy

    The UserAgentClientHintsEnabled policy controls whether the browser sends detailed request headers providing information about the user's browser and environment.

    • Enabled (or Not Set): User-Agent Client Hints are active and sent to websites.
    • Disabled: User-Agent Client Hints are unavailable.

    Caveats:

    • This policy was removed in M94 and was intended as a short-term adaptive measure.
    • Some websites that restrict characters in request headers may not respond correctly when these new headers are sent.

    Technical Details:

    • Data Type: Boolean
    • Dynamic Policy Refresh: True
    • Per-profile setting: False

  10. Control the visibility of Privacy Sandbox prompts

    The PrivacySandboxPromptEnabled policy determines whether users see the Privacy Sandbox prompts designed to inform them about Privacy Sandbox settings.

    • True (or Not Set): Google Chrome determines if the prompt should be shown and displays it when applicable.
    • False: Google Chrome will not show the Privacy Sandbox prompt to users.

    Important Constraint: This policy must be disabled (set to False) if any of the following policies are configured:

    • PrivacySandboxAdTopicsEnabled
    • PrivacySandboxSiteEnabledAdsEnabled
    • PrivacySandboxAdMeasurementEnabled
    {
  "PrivacySandboxPromptEnabled": false
}

  12. Understand FydeOS policy enforcement and user types

    FydeOS policies can be configured in two ways: as mandatory policies that users cannot change, or as default values that users can modify.

    Policies generally apply to two types of users:

    1. Affiliated Users: Users whose account and the FydeOS device they are logged into are managed by the same domain.
    2. Unaffiliated Users: Users who log into a device managed by a different domain (e.g., user@domainA.com on a device managed by domainB.com) or users on unmanaged devices.

    Policies that apply exclusively to one of these user types are explicitly labeled in the management console.