Admin console: dashboard, campaigns, and org tools
What security and HR admins can do in the SmishAlert web console—the day-to-day SecOps view of workforce exposure.
The SmishAlert admin console is the day-to-day SecOps view of social engineering reaching your workforce. After you sign in, admins get the dashboard, campaign correlation, reports, user management, integrations, and billing. This article summarizes the main areas; exact options depend on your role and plan.
Sign in
Go to smishalert.ai and use Log in (or a link from an invite). If your organization requires domain verification or claim-org onboarding, follow the prompts until your account is attached to the right org.
Dashboard & campaigns
The dashboard surfaces active campaigns, reported and captured messages, exposure patterns, and affected employees. SmishAlert correlates lookalike reports into named campaigns so you act on campaign-level context instead of singleton tickets. Drill into a campaign to see the timeline, targeted employees, and recommended action.
Settings (organization)
Organization settings typically include member and invite management, domain verification, user-based billing through Stripe (add users, pay per user), bulk onboarding via CSV, and user lists. Admins manage who belongs to the org and how user licenses are purchased or adjusted.
Optional training add-ons
If your organization enables training add-ons, admins configure and run those campaigns from the web console. Core detection, reporting, and intelligence workflows do not depend on this add-on.
Integrations and signals
Depending on your plan, you may configure webhooks and SIEM/SOAR routing (Standard tier and above) and review signals or reports so correlated campaign signal flows into your existing stack. Navigation items such as Integrations, Signals, Reports, Campaigns, or Users appear when your org is entitled to them. See SIEM, SOAR, and webhook integrations in the Integrations & reporting section.
Mobile apps vs web
Employees use the mobile apps to report and receive dispositions; the deployment mode (Personal or Workforce) is set via MDM. Security and HR teams use the web console to configure the program, review org-level exposure, run reports, and connect downstream systems. Teams manage policy on the web; end users interact primarily on-device. See Deployment modes for what each mode captures.