Permissions and capabilities
HealthBridge permissions answer what your product requests. Provider capabilities answer what the active platform can do. Check both before enabling an optional feature.
Configure the minimum access
Section titled “Configure the minimum access”Open Tools > HealthBridge > Permissions or Project Settings > Plugins > HealthBridge. Every permission row contains:
- A unified data type ID.
- A read toggle.
- A write toggle.
Read access does not imply write access. Request only the types and directions needed by a user-visible feature.
Gate features by capability
Section titled “Gate features by capability”Use UHealthBridgeSubsystem::SupportsCapability in Blueprint or the active
provider’s Supports method in C++. Capability-gate features such as:
- Workout import and writing.
- Generic reads and writes.
- Heart-rate monitoring.
- Workout routes.
- Record deletion.
An unavailable optional feature should produce a disabled or explanatory UI, not a button that silently fails.
Understand platform consent
Section titled “Understand platform consent”Apple does not expose every per-type read decision. Initialization may succeed even when a read type was denied, and the read can return an empty successful result. Treat empty data as ambiguous and provide a route to iOS Health privacy settings.
Android
Section titled “Android”Health Connect reports granted and denied permissions. The final Android
manifest must declare every requested android.permission.health.* permission
before Health Connect can display it.
Write permissions
Section titled “Write permissions”Workout writes require exercise write access. Optional workout fields can
require additional write permissions for their underlying data categories.
Generic writes require both registry write support and configured platform
permission.
Permission-safe UI pattern
Section titled “Permission-safe UI pattern”- Explain why the feature needs the data before opening a system prompt.
- Initialize HealthBridge.
- Inspect permission resolution and provider capabilities.
- Enable only supported, granted features.
- Provide a settings or retry path for declined access.
- Keep the rest of the game usable when optional access is unavailable.
Privacy boundary
Section titled “Privacy boundary”Never log permission payloads with health records or identifiers. Store the minimum state needed to operate the feature and follow your product’s consent, retention, and deletion rules.