Nice find, and you're right. That group isn't really hidden. The Apps permissions doc says "Anyone in my organization can use" simply gives CAN USE to the All account users group, which shows up as account users when you pull the app with the CLI.
The reason it keeps resetting is that a bundle deploy sets the app's permission list to exactly what's in the bundle. Anything you toggle in the UI that isn't in the YAML gets replaced on the next deploy. So put both grants in the bundle:
resources:
apps:
my_app:
name: my-app
source_code_path: ./app
permissions:
- level: CAN_MANAGE
group_name: my-team
- level: CAN_USE
group_name: account usersAfter each deploy the UI should show "Anyone in my organization can use", and your team keeps CAN MANAGE for logs and insights. Two notes from the docs: users still have to sign in through your identity provider (apps can't be made public), and if the workspace uses PrivateLink, access can fall back to workspace-level authentication.
Docs: https://docs.databricks.com/aws/en/dev-tools/databricks-apps/permissions