PLATFORM ADMINISTRATION / ACCESS CONTROL
Accounts & beta access.
Manage existing ACS accounts, review account status, and control BapStack beta invitations.
What does it cost?
One user. The whole stack.
Provisional month-to-date USD in UTC. AWS billing can lag 24+ hours; billing reads are cached six hours. One user is a planning assumption. ChatGPT/Codex subscription fees are not included.
Your products
Administrator sign-in
Sign in with your BapStack DEV account. Platform administrator access is required. Product accounts without that role cannot manage beta access.
Invite a beta tester
Enter an email address to bypass the request queue. An invitation email will explain how to create a verified ACS account and access the beta. Only this exact verified email receives the invitation.
Pending applications
Public applications require your approval. Approving a request whitelists its email and sends an invitation; declining doesn't grant access.
Select an account
Accounts must be created in ACS before you can assign beta access.
Manage BapStack access
No tester selected
Select an existing ACS account to inspect its identity status and manage product-specific beta access.
Loading verified account status…
Identity is sourced from the existing Cognito user pool. Passwords are never stored in this console.
Review Cognito-tracked sessions across BapStack applications and revoke a compromised session when enabled. This is separate from the inactivity timeout.
Send this user a password reset code through their verified Cognito recovery method (email or eligible SMS). This does not change beta access.
Entire ACS suite
One invitation enables beta access to all six ACS applications. Product-specific grants remain stored independently.
Individual products
Choose exactly which applications this tester can access.
Suite access overrides individual product restrictions while it is enabled. Removing suite access restores each product's separately saved selection.