Skip to main content

Sign in and navigate Switera

Use this guide when you are opening Switera for the first time, returning to a workspace after an invitation, or helping a teammate understand where common setup work happens.

Sign in​

Open Switera and choose the sign-in method enabled for your Builder account. The sign-in page is separate from the app workspace so you can authenticate before Switera loads any app data.

Switera Builder login page with email and password fields
Use the same Builder identity your team invited to the workspace. If your account uses social sign-in or passwordless sign-in, choose that method instead of password.

After a successful sign-in, Switera opens the dashboard. If you arrived from a specific invitation, setup, or hosted flow, Switera may continue that flow after authentication.

Create or recover access​

If you do not have an account yet, use the registration page. If you forgot your password or cannot enter with the current credentials, use account recovery instead of creating a second Builder identity.

Switera registration page
Register only with an email address your team expects to use for Builder access.
Switera account recovery page
Recovery keeps the existing account and avoids duplicate workspace memberships.

Some accounts must verify their email before all flows are available.

Switera email verification prompt
Complete verification from the same email account used for Builder access.

Read the dashboard first​

The dashboard gives the workspace-level view across apps. Use it to see whether the workspace is empty, which apps need attention, and where you should continue.

Switera workspace dashboard with app status cards
Dashboard is the safest first stop because it summarizes app readiness before you change settings.

From the dashboard you can:

  • open the apps portfolio
  • create a new app
  • jump into an app that already needs attention
  • compare setup status across apps
  • return to the last app you operated

Choose the right app​

Most Switera work is app-scoped. Before changing Auth, email, webhooks, API keys, organizations, or users, confirm the selected app in the app switcher.

Switera apps portfolio showing app cards and recommended actions
Use the apps portfolio when you manage more than one SaaS product or environment.

Open an existing app when you are changing the same product. Create a new app only when you need a separate product boundary, separate customer population, separate Auth setup, or separate integration credentials.

Understand the main navigation​

Switera console with a single sidebar, app switcher, product links and visible API Keys
Navigation in the Northstar sample app. Check the app name before changing settings.

Inside an app, the left navigation groups work by operating area:

AreaUse it for
AppOverview, the Services catalog, and customer Organizations.
ProductsAuthentication, Email, Billing, Search, Realtime, Feature Flags and Webhooks.
DeveloperAPI Keys and Audit Logs.

The breadcrumb names the current app and product. Use Current app in the sidebar to switch apps, or All apps to return to the app list. On a phone, open the navigation menu to reach the same destinations.

Mobile app menu with Search, Realtime, Feature Flags and Developer links
The mobile menu has the same product links. Scroll for Documentation and Sign out.

In Authentication, common tasks are visible immediately. More settings contains Branding, Organization Access, Enterprise SSO, Auth Hooks, Directory Sync and Compliance. On small screens, use the Authentication section selector. Existing links to individual settings still work.

Expand SDK integration on the Authentication or Email overview when you need integration examples. Keep secret API keys on your backend.

For a new app, follow this order:

  1. Open Dashboard.
  2. Create or choose the app.
  3. Read the app Overview.
  4. Create the first organization if your product is B2B or team-based.
  5. Configure Products > Authentication.
  6. Prepare Products > Email before inviting users.
  7. Add Products > Webhooks only when a backend needs events.
  8. Copy Developer > API Keys only into trusted backend secret storage.
  9. Review Developer > Audit Logs after the first setup pass.

Continue with Create your first app.