Crate bitwarden_managed_settings 

Bitwarden Managed Settings

Provides ManagedSettingsClient, the SDK’s read handle onto the settings an organization’s IT administrators enforce through the host operating system’s Unified Endpoint Management (UEM) channel.

The host application constructs a ManagedSettingsClient at startup with ManagedSettingsClient::new, acquires a ManagementProfile from the host platform, and pushes it in with ManagedSettingsClient::update_profile. Passing None clears the profile. Clones of the handle share one profile, so an update pushed through any clone is observed by all of them, as does the shared cell returned by ManagedSettingsClient::cell.

Consumers read a value with ManagedSettingsClient::get for the raw JSON-encoded string, or decode it into a concrete type with ManagementProfile::get_as on the profile returned by ManagedSettingsClient::current_profile. Guard writes to the corresponding state with ManagedSettingsClient::is_managed, only writing when the key is not administrator-forced.

The first profile push is asynchronous on every platform, so a consumer may not observe a managed setting immediately after startup.

A managed setting overrides user and global state and built-in defaults. It carries no automatic precedence over an enterprise policy — where a policy and a managed setting both bear on one effective setting, the consuming feature is responsible for resolving the conflict.

Not yet wired into bitwarden-core. Attaching this handle to a Client, so SDK feature crates read the profile the host pushes, lands in a follow-up alongside the WASM and UniFFI bindings.

Modules

managed_settings_client 🔒

Structs

ManagedSettingsClient

Handle to the host system’s Unified Endpoint Management profile.

ManagementProfile

A point-in-time snapshot of administrator-forced configuration for this client.