Shared Presets
Reuse obfuscation configurations across your team and choose a shared starting configuration.
Share a preset
Only the team owner can publish shared presets. Configure the obfuscation options, open Custom Presets, and select Save Current. Give the preset a name, enable Share with my team, and select Save Preset.
To share an existing preset, open its menu, choose Rename, and enable sharing. To update its options, save the current configuration under the same name and confirm the overwrite.
Load or customize a shared preset
Members can find shared configurations under Team presets and use Load preset to apply one. Only the owner can change or delete the shared original. Choose Duplicate to my presets to create an independent personal copy that you can edit.
Set a team default
The owner can choose Set as team default from a shared preset’s menu. Only one preset can be the team default. Members can adjust their options after it loads. When the owner updates a shared preset, load it again to pick up the changes.
Choose Remove team default to stop using it as the default while keeping it shared. Turning off sharing also removes its default status.
Enforce the team default
A team default is normally a starting point that members can change. A team owner can instead lock it. Open Settings → Team, turn on Enforce team default preset, and choose which preset to enforce. While enforced, members' options are read-only and every obfuscation (the dashboard, member API calls, and team service tokens) uses the enforced preset. Turn the switch off to return to a soft default. See Version pinning to enforce a version the same way.
Use the configuration in CI
Team defaults apply to the dashboard. For API builds, send the required options explicitly in each request. Keep separate configurations for functional tests and defended production builds. For functional test settings, see Testing and CI.