At the moment, the workspace is created as soon as the bot is added to the server, and must be configured by the server owner with the /config command.

We're planning on changing this to an onboarding system. We'll create a multi-step onboarding process which guides the workspace owner through Kyro's features, enabling them to configure core settings throughout the process (eg admin/staff role, log channel). We'll prompt them to update everything else (/config & all modules).

The workspace should be deactivated until the onboarding process has been completed. We're considering allowing server members with the 'manage apps' permission to complete the onboarding process, however, this may not be implemented due to security concerns.