Dashboard Guide

Step-by-step walkthrough for managing teams through the Hoppla dashboard.

Logging In

1. Go to https://app.hoppla.dev
2. Enter your reseller email and password
3. Click Sign In

After logging in you'll see your own monitoring dashboard. The Teams section in the sidebar is only visible to reseller accounts.

Teams Overview

Navigate to Teams in the sidebar to see all your managed teams.

The teams list shows:

• Team name and slug
• Plan (Free, Hobby, Starter, Pro)
• Label (your internal reference)
• Created date
• Monitor count and health status

Use the search bar to filter teams by name or slug.

Creating a Team

1. Click Create Team in the top-right corner
2. Fill in the required fields:
   • Name — Display name for the team (e.g. "Acme Corp")
   • Slug — URL-safe identifier, lowercase with hyphens only (e.g. "acme-corp")
3. Optionally configure:
   • Plan — Select Free, Hobby, Starter, or Pro
   • Label — Internal note for your reference (not visible to the team)
   • Admin User — Pre-create an admin account for the team
     • Email, name, and password fields appear when toggled on
4. Click Create

The team is provisioned immediately. If you have webhook notifications configured, a team.provisioned event is dispatched.

Team Details

Click on any team name to view its details page:

• Overview — Team name, slug, plan, creation date
• Summary — Monitor counts (total, up, down, paused) and incident counts
• Usage — Monitor breakdown by type, check count over last 30 days

Viewing as a Team

To manage a team's monitors and settings:

1. Click View as this team on the team details page (or the eye icon in the teams list)
2. The dashboard context switches — you'll see a banner indicating you're viewing as another team
3. All pages (Monitors, Incidents, Status Pages, etc.) now show the team's data
4. You can create, edit, and delete monitors as if you were logged into the team's account
5. To return to your own account, click the team selector dropdown and choose Back to my account

Editing a Team

1. Go to the team details page
2. Click Edit in the top-right corner
3. Update the name, label, or plan
4. Click Save

The slug cannot be changed after creation.

Deleting a Team

1. Go to the team details page
2. Click Delete in the top-right corner
3. Confirm the deletion in the dialog (you'll be asked to type the team name)

Deleting a team is a soft delete with a 30-day grace period. The team and all its data — monitors, incidents, check results, notification channels, and users — are deactivated immediately but kept for 30 days. During that window you can restore the team (look for trashed teams in the teams list, or use the restore endpoint). After 30 days, the team and all associated data are permanently purged and can no longer be recovered.

A team.deleted webhook event is dispatched after deletion.

Branding & SMTP Settings

Navigate to Settings in the sidebar to configure white-label branding for your tenant.

Visual Identity

• Brand Name — Displayed in notification headers and emails
• Primary / Secondary Color — Used for accents in emails and the dashboard
• Logo URL / Dark Logo URL — Shown in email headers (dark logo for dark backgrounds)
• App Symbol URL — Square mark shown in the collapsed sidebar and next to your name on the portal login (at least 64 × 64 px). Without one, your favicon is used, then the first letter of your brand name; your customers never see the Hoppla symbol
• Favicon URL — Custom favicon for status pages
• Social Preview Image (OG image) — Image shown when your portal or status-page links are shared on social media and chat apps

Notification Branding

• Alert Prefix — Starts every notification subject and title (e.g. "Acme Alert!"). Without one, your brand name and a colon are used: "Acme: Checkout API is down".
• Notification From Name — Custom sender name for emails

Footer & Legal

• Footer Text / URL — Custom footer in notification emails
• Privacy URL / Imprint URL — Legal links in email footers
• Terms URL — Link to your own terms of service
• Hide Powered By — Remove Hoppla attribution (requires white-label branding plan feature)

Custom SMTP

Configure your own SMTP server to send emails from your domain:

1. Enter SMTP host, port, encryption, and credentials
2. Click Test Connection to verify
3. Click Save to activate

All notification emails (alerts, digests, invitations, password resets, email changes) will be sent through your SMTP server, From your configured from_address. If your server is unreachable, Hoppla falls back to the platform default.

Deliverability — avoid the spam folder

Portal emails are branded as you (your brand name, your portal links). If they go out from the platform sender ([email protected]) instead of your own domain, mailbox providers see "your brand, someone else's domain" and flag it as phishing → spam. The fix is to send from a domain you control and authenticate:

1. Configure Custom SMTP (above) with a from_address on your own domain (e.g. [email protected]). Emails then go out From: that address.
2. Authenticate that domain's DNS so the From aligns:
   • SPF — authorize your SMTP host to send for the domain (TXT, e.g. v=spf1 include:<your-provider> ~all).
   • DKIM — add the signing key your SMTP provider gives you (CNAME/TXT).
   • DMARC — v=DMARC1; p=none; rua=mailto:... to start; tighten later.
3. Send a test (Test Connection) and check the received headers show spf=pass, dkim=pass, dmarc=pass, with the From: on your domain.

Until Custom SMTP is set, portal emails send from the platform's authenticated [email protected] (which itself passes SPF/DKIM), but with your brand name — acceptable for low volume, but a domain you authenticate yourself is what reliably reaches the inbox. The from_address only takes effect with Custom SMTP active (without it, the platform address is used so platform authentication still holds).

Upsell / Monetization

If you sell monitoring as a paid add-on, you can turn on in-product upsell prompts that nudge managed-team users toward a higher plan — all under your own brand. Configure these in the branding settings:

• Upsell Mode — Turn upsell prompts on or off (and choose how prominent they are)
• Upsell Call-to-Action — The button label and link users follow to upgrade (point it at your own checkout or sales page)
• Plan Labels — Rename the plans your customers see (e.g. show "Starter" as "Business")
• Upsell Offers — Define the offers/tiers shown in the upgrade prompt
• Upsell Threshold — How close a team must be to a plan limit before an upgrade nudge appears

Because the prompts use your branding and link to your own checkout, the upgrade flow stays entirely within your customer relationship.

Provisioning Profiles

Provisioning profiles let you save a reusable "starter kit" for new teams — a plan, trial length, feature limits, branding defaults, and an optional monitor template — so you can spin up a fully configured team in one step instead of setting everything by hand each time.

1. Navigate to Provisioning Profiles in the reseller area
2. Click Create Profile and give it a name (e.g. "WordPress Hosting Standard")
3. Choose the plan, trial days, feature limits, branding defaults, and an optional monitor template
4. Save the profile, then select it when creating a new team

Monitor Templates

Monitor templates are reusable sets of monitors (with variables like the customer's domain) that you can apply to any managed team in one action — ideal when every customer should get the same baseline checks (homepage uptime, SSL, DNS, etc.).

1. Navigate to Monitor Templates in the reseller area
2. Create a template and add the monitors you want, using variables (e.g. ) where values differ per customer
3. Apply the template to a team and fill in the variables — the monitors are created instantly

Portal Settings & Custom Domain

The Portal Settings area lets you run a self-service signup portal under your own brand:

• Self-service registration — Let customers sign up directly on your portal; new signups are provisioned as managed teams automatically
• Registration defaults — Set the default plan and trial length for self-service signups
• Custom domain — Serve your portal (and your customers' status pages) on your own domain. Add the domain, follow the DNS verification steps shown in the UI, and verify it.

You can also set a custom domain for your own reseller account, which acts as the fallback portal domain for any team that doesn't have its own.

Reseller Tokens

Reseller management tokens (rk-…) are scoped API tokens for automating reseller operations (creating teams, managing branding, etc.) without using your personal login.

1. Navigate to Reseller Tokens in the reseller area
2. Click Create Token, name it, and select the scopes it should have
3. Copy the token — it's shown once and starts with rk-. After that the list only shows a masked stub (e.g. rk-...aB3d)
4. You can rotate, disable, or delete a token at any time

See API Reference — Reseller API Tokens for the full scope list.

Managed-Team Service API Keys

For a managed team that needs its own automation, you can issue a service API key (svc-…) scoped to that single team. The key lets the team (or your integration on their behalf) call the standard API for that team only.

1. Open the team details page
2. Open API Keys and click Create Key
3. Choose read or read/write access and copy the key — it's shown once and starts with svc-

These keys are separate from your reseller management tokens and only ever grant access to the one team they belong to.