Application scope

Application Scope controls which Android application users receive certificate/keybox compatibility or identity properties.

Where to find it: Dashboard / Apps. Where is each feature?

What to do

Keep keybox scope and identity scope separate.
Use Apps for target lists; use Profiles for named app assignments.
Global Keybox covers eligible apps; broad identity changes may require reboot.

Details and limits

Setting	Result
`target.txt`	Keybox targets when Global Keybox is off.
`identity_target.txt`	Targets for optional identity; kept separate from keybox scope.
`global_mode`	Global Keybox: eligible non-system apps. On by default; live change, no build-property rewrite.
`global_attestation_mode` / `global_telephony_mode`	Broader attestation/telephony targeting, off by default; separate from the required Global Identity properties.

Package Manager resolves the caller UID. Packages sharing a UID share its decision; a matching package affects the shared caller. Valid rules and named profile assignments can target an app directly. Security Patch is independent from optional identity. Changes to boot-captured values take effect after reboot.

Zygisk is optional for the module. While Identity is enabled on Dashboard, Global Identity stays enabled and cannot be turned off separately. Enabled Build, Region and Custom properties apply device-wide; disabling Identity disables these changes. Zygisk is recommended for app-specific Identity profile overrides. Security Patch remains independent.

Back to all guides

The same ZIP installs the optional CleveresTricky Identity (Optional Zygisk) companion as a separate module. The core module never requires Zygisk. Without an active provider, the companion starts disabled; enable Zygisk and then enable the companion in your root manager for app-specific overrides. Companion disable choices survive updates. Removing the core removes its companion, and a disabled, removed or mismatched core prevents companion hooks.