Skip to content

Using the Wizard in Daily Practice

What the wizard is

The Tenant Wizard is a guided setup flow, not just a form. It is designed to help users make the right decisions in the right order.

Typical wizard behavior includes:

  • step-by-step navigation
  • validation before moving forward
  • conditional fields depending on setup choices
  • direct connection tests
  • contextual explanations

How to work through it

The most reliable approach is:

  1. choose the correct setup type first
  2. enter CPI connectivity carefully
  3. complete Edge details only when really needed
  4. define a realistic monitoring scope
  5. review the full configuration before saving

Avoid rushing through the early steps. Small mistakes there usually affect everything that follows.

Help inside the product

The wizard offers help directly where users need it.

Typical help usage:

  • read the short inline help when a field is unclear
  • use the larger documentation entry when you need more context
  • compare your current choice with the later operational impact

The most useful moment to read help is before selecting setup mode, authentication, and monitoring scope.

Operationally important points

Some wizard choices have a stronger effect than others.

Pay special attention to:

  • setup type
  • authentication method
  • certificate handling
  • query and download strategy
  • hot window and attachment behavior

These choices influence not only setup success, but also later:

  • monitoring quality
  • system load
  • user visibility
  • ongoing maintenance effort

Typical use cases

First productive onboarding

Use the wizard to create the initial tenant with safe defaults, then fine-tune later in Tenant Settings.

Landscape change

If a tenant changes from CPI-only to hybrid requirements, the wizard helps make the structural decisions visible before operations start.

Handover between teams

The guided steps reduce the risk that important settings are forgotten when one team prepares the tenant and another team operates it later.

Good habits

  • run available connection tests before finishing
  • keep the first configuration simple
  • avoid enabling every option on day one
  • use the review step as the final plausibility check
  • document special edge or certificate assumptions outside the wizard if they matter operationally

Common mistakes

  • treating the wizard like a quick technical checklist
  • using copied values without checking tenant and environment
  • selecting a complex setup although a simpler one is enough
  • tuning for maximum detail before stable connectivity exists

What comes after the wizard

After the tenant is created, daily maintenance usually moves to:

  • Tenant Settings for ongoing adjustments
  • Alerting for notification behavior
  • operational views for monitoring and troubleshooting