Lock Configuration

  • Published on Mar 10, 2026
  • 2 minute(s) read
Prev Next

Overview

Lock Configuration enables administrators to enforce settings across subgroups, ensuring Sanas usage aligns with organizational guidelines and compliance requirements.

When a configuration is locked:

  • Subgroups inherit the locked setting from the parent group, replacing any existing customizations.

  • Subgroup administrators cannot modify the locked setting.

  • Changes at the parent level propagate automatically to all subgroups below.

If a setting is enabled but not locked, subgroups retain the flexibility to modify it.

Best practices for locking configurations

Below are a few important points to consider before deploying the changes on the Portal:

  • Identify the right group: Locks flow downward to all subgroups. Plan your hierarchy before enabling.

  • Choose the right scope: Lock at the account level for organization-wide enforcement, or at a specific group for targeted enforcement.

  • Communicate changes: Subgroup administrators will lose the ability to modify locked settings; inform them beforehand.

  • Time it right: Lock changes take effect on the next automatic application sync for users. Avoid deploying while users are actively on calls to avoid interruptions.

How locking works

Lock Configuration is a toggle that appears next to supported settings in the Portal.

  1. Set the configuration to your desired state.

  2. Toggle on Lock Configuration.

Configuration settings for portal authentication with options to lock and save changes.

Once locked, the setting applies to all subgroups beneath the selected group.

What subgroup admins see:

  • Toggles and fields appear grayed out (read-only).

  • The Lock Configuration toggle is enabled and cannot be changed.

  • To modify a locked setting, they must contact the administrator who applied the lock.

Sample use cases

Follow the practical use cases below to understand different ways of implementing on your Sanas account:

Control product access organization-wide

Scenario: All users should have access to Sanas Accent Translation (AT).

  1. Navigate to Feature Management at the account level.

  2. Enable the access toggle for Accent Translation.

  3. Toggle on Lock Configuration and save your changes.

All groups inherit AT access, and no group-level administrator can disable it.

Enforce consistent configuration

Scenario: The same AI model configuration gets utilized for all groups.

  1. Navigate to Configuration at the account level.

  2. Set the desired parameters.

  3. Toggle on Lock Configuration for each setting.

Restrict a product from specific groups

Scenario: Accent Translation should not be available under a specific department.

  1. Navigate to Feature Management at the department's group.

  2. Disable Accent Translation.

  3. Toggle on Lock Configuration.

Subgroups beneath that department cannot enable it.

FAQ

Can I lock settings at any level, not just the account level?

Yes. Lock Configuration works at any level in the hierarchy and enforces the setting on all subgroups beneath it.

What happens if I unlock a previously locked setting?

Subgroups regain the ability to modify the setting. Their configuration stays at the inherited value until actively changed; it does not revert to what existed before the lock.

Support

Need help? Get in touch with our Support Team for assistance.