Automatic Onboarding
By default, when a new project (e.g. a Data Product) is registered in Witboost, an automatic onboarding mechanism assigns a project owner at registration time, whenever Team Roles is enabled for that project type.
This process fetches the projectOwner field (or dataProductOwner, or owner) declared in the project's catalog-info and automatically assigns the user found there as Full Project Owner.
This mechanism ensures that there is always a responsible user as soon as a project is registered, without requiring manual intervention in the Team Roles panel.
If the auto assignment fails (e.g. team role is not properly configured or any internal error) a warning is logged. If the project does not become available in the catalog within the timeout window, the auto-assignment process is skipped and an error is logged. The mechanism will not retry again, but the project can be manually onboarded via the Team Roles panel at any time.
This mechanism applies only to newly registered projects. For projects that already existed when Team Roles was enabled, onboarding must be performed manually via a one-click onboarding process described here.
Automatic Onboarding Configuration
Automatic onboarding is controlled by two properties in your Witboost instance's values.yaml:
ui:
appConfig:
mesh:
builder:
teamRoles:
autoOnboarding:
enabled: true # Enables/disables automatic onboarding (default: enabled)
timeoutMs: 300000 # Timeout in milliseconds (default: 300000, i.e. 5 minutes)
| Property | Type | Default | Description |
|---|---|---|---|
ui.appConfig.mesh.builder.teamRoles.autoOnboarding.enabled | boolean | true | If true, enables the listener for new project registration events. If false or not specified, the mechanism is completely disabled |
ui.appConfig.mesh.builder.teamRoles.autoOnboarding.timeoutMs | number | 300000 ms (5 min) | Maximum waiting time (in milliseconds) for the newly registered project to become available in Witboost. If Witboost does not respond within this time window, the auto-assignment is aborted. The retry interval is fixed at 500ms |