In the Provisioning tab in Tenant Administration, you can configure the Service Provisioning default settings which apply when new Nimbus services are created.
| Default OU for MS Teams creation | Sets the default Organization Unit (OU) for new services during their first provisioning. 🔍 Please Note:
|
|---|---|
| Allow service provisioning via MS Teams | Set the minimum roles required to Provision a new Nimbus team directly from the MS-Teams UI. Settings are:
💡 This setting does not prevent users from installing the Nimbus Personal App. 🔍 Non MS-Teams synched Service types can still be provisioned via the backend by any administrator, regardless of the setting made here. ☝ Users without the permission to Provision new services may still remove the Nimbus tab from MS Teams (as Nimbus cannot impact or restrict the default MS Teams interface). However, they can not trigger a removal of the service itself and its data and the Nimbus tab can be re-added.
|
| Default Team Owner Role | The default role assigned to a new user when a new Nimbus team is provisioned directly from the MS-Teams UI. Options are:
💡 Existing services are not affected by this change and changing this setting will only affect future services provisioned via MS Teams. |
| Enable Multihoming |
💡This field is read-only as Multihoming must be set up for your Tenant by a System Administrator and in cooperation with Luware Customer Success. This feature is meant for large Tenants with users working from different locations. ✅ For Tenant Administrators: Enabling Multihoming on multiple clusters has clear benefits, but also underlies strict technical limitations. Before deciding to roll out this feature:
|
