Ask anything official about AppDefender.dev. I only answer from approved knowledge. I do not invent capabilities, and I do not enforce policy.
Newsroom
Four seats, no self-approval, two environments
Maker 1, Maker 2, Checker 1, Checker 2. Super Admin enables Sandbox or Production before a Client can open it.
AppDefender.dev splits people the same way it splits catalogs. Super Admin grants the workspace. Client Admin then works in four seats: two makers, two checkers.
Sandbox is where a Client proves initialize, launchSecurityCheck, and ATS envelopes. Production opens only when Super Admin enables it. Credentials stay prefixed and shown once. rnsh_sbx_ never becomes rnsh_prd_ by editing a string.
Production policy needs two checkers. A maker cannot approve their own change. That is the control banks already expect on payments — applied to the security catalog that decides BLOCK.
If you want a walkthrough of the seats, request a workspace. The console is open for Client onboarding.