Running it day to day
- Written for
- + Written for
- Deprecated
- + Deprecated
- Applies to
- + Applies to
Part 6, the final part of the visual dashboard tour. These are the screens you'll open once your app is live — to keep it secure, see what's happening, add teammates, and manage your bill. All no-code.
Security
Open Security. This is your incident-response console — the switches you reach for when something's wrong, plus the everyday hardening.

Kill switches — big, deliberate controls: Block all sign-ins, Block all sign-ups, or Force a challenge on every sign-in. These stop real users, not just attackers, so they're for emergencies.
IP allowlist — restrict which networks can reach this instance (useful for internal tools).
The tabs — Restrictions, Rate limits, Adaptive MFA, Network ACLs, Managed WAF, Bot signals — cover automatic defences that mostly look after themselves but can be tuned here.
Logs
Open Logs. Every meaningful event in your instance is recorded here — a complete, exportable audit trail.

Each row is one event — a user created, an organization created, a membership added, a sign-in — with who or what it was about and when. You can filter by event type, by a specific user or resource ID, and by time window, then Export CSV for your records or a compliance request. The Data requests and Log streams tabs handle privacy requests and piping logs to your own tools. When you need to answer "what happened to this account?", this is the screen.
Usage
Open Usage. The trend view — sign-ins, sign-ups, emails sent and active users over time.

Switch between 7-, 30- and 90-day windows to see how your numbers are moving. This is the screen to check for growth, or to spot an unusual spike that might mean a problem.
Team
Open Team. This is your team — the colleagues who help you manage this app in the Atlas dashboard. (Don't confuse it with Users, which is your app's end-users.)

Invite a colleague by email and pick their role. They'll be able to manage this app's auth, but — unless you allow it — they won't see account billing. Remove someone here the moment they leave.
My account
Open My account. Your own admin login and preferences.

Here you choose which email notifications Atlas sends you (security alerts, billing, team, product updates), rename or delete the applications this account owns, and set or change your own password and two-factor authentication. Securing your own admin login with MFA is the single best thing you can do for your account's safety.
Platform keys
Open Platform keys. A higher-tier, advanced key (psk_…) for teams that manage many apps programmatically.

Where a normal secret key works with one app, a platform key can create new apps and rotate their secrets across your whole account over the platform API. It's a root-level credential — most teams never need one, and if you do, treat it like a master password.
Billing
Open Billing. Your Atlas plan and subscription, handled securely by Stripe.

The Free plan covers all the auth, users, orgs, connections, webhooks, keys and logs — on your own email/SMS provider, with unlimited monthly active users.
Pro ($25/mo per app) adds Atlas-managed email and SMS sending (no provider setup) and priority support.
Each paid subscription applies to one app; Upgrade to Pro on the app you want, and you can move a subscription between apps later.
---
That's the whole dashboard, screen by screen. You've now seen every feature Atlas offers, exactly as it appears when you sign in — from adding your first user to gating features by plan, securing the instance and reading the audit trail. Start at the beginning of the tour any time, or jump straight to the screen you need from the sidebar.