Concepts and terminology
This page defines the terms used throughout Switera. Use these names in your team runbooks and support docs so everyone speaks about the product in the same way.
Builder
A Builder is the person or team using Switera to create and operate a SaaS product.
Builders configure apps, choose services, manage organizations, invite team members, create API credentials, review audit logs, and connect external systems.
App
An app is the main product container inside Switera. Each app has its own:
- organizations
- end users
- Auth settings
- email configuration
- webhook endpoints and event catalog
- API keys
- OAuth client settings
- audit logs
Treat each app as a separate SaaS product or product environment. If two products need different user bases, sign-in rules, webhook destinations, or audit histories, create separate apps.
End User
An End User is a person who signs up for or uses the Builder's SaaS product. End Users are usually managed through Auth and may belong to one or more organizations.
Do not confuse End Users with Builders. Builders operate Switera. End Users use the product that the Builder is creating.
Organization
An organization is the customer account, workspace, company, or team inside a Builder's app. Organizations are the natural boundary for:
- members
- invitations
- domains
- groups
- organization roles
- directory sync mapping
- SSO role mapping
Some technical APIs may use the word tenant for this same concept. In the user interface and public docs, use organization.
Auth
Auth is the Switera service for sign-in and end-user access. It includes:
- password and passwordless sign-in
- magic links and OTP
- passkeys
- social login
- enterprise SSO
- MFA
- session policy
- bot prevention
- branding
- legal consent
- Auth Hooks
- directory sync
App Credential
An App Credential is a machine credential scoped to one app. Use app credentials from your backend or trusted server environment. Never embed secret keys in browsers, mobile apps, public repositories, or documentation.
Webhook Service
The Webhook Service sends events from Switera to your backend or workflow tools.
Events can come from Switera platform activity, managed services, or events your own backend emits through the Switera API. A webhook endpoint chooses the event types it receives.
Email Service
The Email Service controls app-level email identity and delivery behavior. Use it to configure sender profiles, sender domains, delivery providers, workflow timing, invitation templates, managed emails, suppressions, and runtime delivery history.
Activation milestone
An app reaches its activation milestone when it has enough setup to deliver real value. For many apps this means:
- an app exists
- at least one organization exists
- Auth has a usable sign-in method
- email invitations or managed messages are ready
- API credentials and webhook endpoints are configured if the app depends on backend integration
Use the Activation checklist before inviting real users.