The account owner defines custom onboarding fields per Toolset — specific to the niche the Toolset serves. These are not generic fields. The account owner decides what information matters for their use case (e.g., for a brewery Toolset: brewery name, flagship brews, taproom details, brand personality, social platforms, target customer, distribution footprint). The end user fills these out once when they first log into the Toolset. From that point forward, every SmartForm and CoPilot inside the Toolset has that context automatically. The end user never re-explains who they are. This is what makes a Toolset feel like software that knows its user, not a collection of disconnected forms.