Initial Tenant Onboarding
Add a Cisco Spaces tenant and clone its initial location hierarchy.
Before you begin #
Initial Cisco Spaces tenant onboarding is currently restricted to internal administrators. From the tenant details in Cisco Spaces, collect the tenant name, tenant ID, region, and a current sys-token. The supported regions are AMER, EMEA, and APJC.
Add the tenant #
- Open Tenants and select Add Tenant.
- In Add Tenant (Spaces Onboarding), enter the tenant name and Cisco Spaces tenant ID exactly as shown in Spaces.
- Select the tenant's Cisco Spaces region. WaSense saves this choice and uses it to resolve regional Spaces API hosts.
- Paste a current Cisco Spaces sys-token.
- For lightweight initial onboarding, leave Location ID blank and do not select Include floor plans.
- Select Start onboarding and confirm that the tenant opens with its location hierarchy available.
If Spaces collection fails, WaSense removes the newly created tenant rather than leaving a partial onboarding record.
What initial onboarding creates #
The initial pass clones the location hierarchy and lightweight supporting tenant data so that the deployment scope can be selected. It deliberately omits floor-plan maps and scoped AP placements. After onboarding, sync only the campus or building that is the target of the deployment to retrieve those heavier items.
Onboarding does not create a monitoring profile, monitoring configuration, IoT intent profile, IoT deployment, or published device intent. Monitoring and IoT intent remain independent, optional post-onboarding choices.
The onboarding sys-token is used for this collection. Do not assume it is stored for later monitoring, synchronization, or IoT operations; a current token may need to be supplied again.