Configuration Templates

A Configuration Template is a predefined set of settings and parameters that enables administrators to efficiently create, manage, and maintain consistent configurations for networks, venues, and services across RUCKUS One.

Feature Overview

Configuration Templates in RUCKUS One provide a consistent and efficient way to define, apply, and manage configuration settings across networks, venues, and services. Using templates helps reduce configuration time, maintain uniformity, and minimize manual errors.

Functional aspects of implementing Configuration Templates include:

  • Drift detection: Identifies differences between a template and its applied instances.
  • Synchronization: Allows differences found during drift detection to be corrected.
  • Enforcement: Ensures applied instances strictly follow the defined template. When enabled, configurations become read-only at the applied instance level and can be modified only at the template level.
  • Manage Tags: Assign, update, or remove descriptive tags to improve organization and filtering.
    ACX-103139: Config Template 5 - Tagging
  • Bundles: Provides a way to view and manage logical groupings of dependent templates. The Bundles approach helps streamline operations and improve visibility of dependencies by transitioning from a flat list to a structured, hierarchical organization while retaining backward compatibility. Bundles inherit all existing template functionalities such as drift detection, synchronization, and enforcement, allowing these operations to execute seamlessly at the Bundle level, while preserving the granularity of individual template management.
    ACX-104024 - Bundles in R1

Requirements

To access and configure Configuration Templates, the following conditions must be met:

  • The RUCKUS One tenant account must have the Professional subscription tier license.
  • The user must have Admin or Prime Admin permissions.

Considerations

Consider the following when configuring and using this feature:

  • Each template type supports only one applied instance at a time, except Venue templates, which can be applied multiple times.
  • Applying templates is supported for all configuration template types, while the override functionality is supported only for Venue templates.
  • When applying templates from the Bundles page, only the top-level template can be selected to apply the configuration bundle; the downstream templates are read-only.
    ACX-104024 - Bundles in R1
  • Cloning is supported for selected template types, including Wi-Fi Network, Venue, DPSK, and Wi-Fi Calling templates.

    AP Group cloning is triggered by the venue clone process. When you clone a venue instance, all its non-default AP Groups are automatically cloned as part of the venue cloning workflow. AP Group configuration templates cannot be directly, manually cloned.

    Upcoming Feature: Config Template 5 - Clone Venue in R1 (ACX-102797) The next revision condition is applied. Before publishing, add it after "Cloning is supported for selected template types, including Wi-Fi Network, Venue, DPSK, and Wi-Fi Calling templates".
  • Enforcement is supported for selected template types. When enforcement is enabled, applied instances become read-only.
  • Drift detection and synchronization are available only for templates that have been applied.
  • When an account is downgraded to a lower tier, the feature is disabled, previously applied templates are automatically unlinked from networks and venues, and configurations must be managed manually.
    Note: Downgrading does not delete existing templates; they remain inactive until the account is upgraded again.
    ACX-101650 - Config Template 5 - REC Tier Downgrade SME - Zam Huang

Limitations

Note the following limitations regarding this feature:

  • MSP End Customer (MSP-EC) accounts are not eligible to use this feature.
  • Identity Group configurations are not supported in templates.
  • Viewing configuration details is unavailable for Switch CLI Profile and Switch Regular Profile templates.
  • Enforcement applies only to instances created from the template; template details remain editable.

Best Practices

  • Create all dependent templates first to ensure successful application and enforcement (for example, create Network templates before Venue templates).
  • Regularly check the Drift Status and use the Sync option to maintain consistency.
  • Enable enforcement only after confirming configurations are finalized.
  • Use meaningful template names to simplify identification and management.
  • Use the Clone feature to create new templates quickly while reusing existing configuration settings.

Prerequisites

This feature has no prerequisites for enablement or usage.

V1 (ACX-89186 -17/10/25) and V2 (ACX-104024 - 21/1/26) – Editorial Review completed.

In this section:

  1. Adding and Managing Configuration Templates
    Administrators can create and manage configuration templates with predefined settings and variables to simplify and standardize network setup across the tenant.
  2. Applying a Configuration Template Bundle
    You can use configuration template bundles to organize and manage related templates in a hierarchical view, where each top-level (root) template is linked to one or more downstream templates. The feature supports multiple viewing modes and provides top-level (root) actions to apply, monitor, or manage configuration templates efficiently across the network.