{"id":44874,"date":"2026-08-28T12:26:53","date_gmt":"2026-08-28T10:26:53","guid":{"rendered":"https:\/\/smartfense.com\/?p=44874"},"modified":"2026-08-28T14:39:06","modified_gmt":"2026-08-28T12:39:06","slug":"onboarding-instancia-nueva-cuenta-activa","status":"publish","type":"post","link":"https:\/\/smartfense.com\/en\/partners-blog\/onboarding-instancia-nueva-cuenta-activa\/","title":{"rendered":"Two ways to use Onboarding in a SMARTFENSE implementation"},"content":{"rendered":"

Two ways to use Onboarding in a SMARTFENSE implementation<\/h1>\n

The most repeated question in an implementation is what is still left to configure. The manual explains how each thing is done, but it says nothing about the state your instance is in right now, and that gap between the documentation and the actual account is what stretches a rollout.<\/p>\n

What is the Onboarding section?<\/h2>\n

Onboarding is the section of the platform<\/a> that brings every configuration of an implementation into one place, recognises the ones already done and flags the ones worth reviewing.<\/p>\n

What sets it apart from a manual is state. When you open it, the platform has already checked whatever it can check on its own and hands you a view of where you stand, rather than a list of everything that exists.<\/p>\n

Onboarding is split into independent sections, and each one advances at its own pace depending on what you configure. There is no mandatory top-to-bottom order.<\/p>\n

How Onboarding is organised<\/h2>\n

Each section groups the configurations of one stage: the initial ones, simulation delivery, user management, the mail server, the end-user view, gamification, integrations and the first campaign. Overall progress updates as you go, and green marks what is complete. A section with no green is the signal that something is pending there.<\/p>\n

\"The<\/p>\n

The buttons change according to what the platform can verify by itself:<\/p>\n