Development Panel Client

Every panel running in development must authenticate through the IAM client named panel, regardless of its role or runnable process name. Do not declare accounts.client in a panel settingsOverride.json; let shared panel infrastructure select the client for the environment and role.

Philosophy

All development panels share one IAM client while their roles continue to control authorization.

Correct

{}

Incorrect

{ "accounts": { "client": "adminPanel" } }
{ "accounts": { "client": "userPanel" } }
{ "accounts": { "client": "panel" } }

Fix

Remove accounts.client from the panel settingsOverride.json and let shared panel infrastructure select the IAM client.