Summary

BigBlueButtonBN extensions (subplugins) currently lack the ability to define and enforce global settings at the site level. Since some of the settings introduced by extensions should be configurable by default for the institution and, in some cases, hidden from teachers or editing users, it is necessary to extend the support for global settings within extensions.

Issue Details

• Current Limitation: While BigBlueButtonBN itself supports global settings, subplugins/extensions do not have a structured way to integrate with these settings.

• Need for Default Values: Some extension settings should have predefined default values that apply across all instances.

• Need for Enforced Settings: Administrators should be able to lock certain settings, preventing modification at the instance level.

• Role-Based Visibility: Some settings should be hidden from teachers or other editing users while still being enforced globally.

Proposed Solution

1. Extend the Moodle global settings system (config_plugins) to support BigBlueButtonBN extensions/subplugins, allowing them to:

• • Define site-wide defaults for extension-specific settings.

• • Implement enforced (locked) settings that prevent instance-level changes.

• • Control visibility of settings based on user roles and capabilities.

1. Modify the extension settings framework to:

• • Allow subplugins to register global settings within BigBlueButtonBN’s admin settings.

• • Provide a mechanism for hiding settings in the instance form while applying them automatically.

• • Ensure inheritance of global settings when a new instance is created.