Summary

Grouped reference for the scoped app-settings read / write filters. Each follows the same pattern as mam_app_settings_get_setting — one filter per scope. Use these when you need a typed read of a specific settings family rather than the generic key-by-key cascade.

Read filters

Generic read signature:

$value = apply_filters(
    $filter_name,
    $default,
    string $role
);

Write filters

Admin UI extension hooks

Example: read the layout for the active role

$layout = apply_filters(
    'mam_app_settings_get_layout_settings',
    array(),
    mam_current_request()->user_role()
);

Example: override form colors per role

add_filter( 'mam_app_settings_get_form_colors', function ( $colors, $role ) {

    if ( $role === 'subscriber' ) {
        $colors['primary'] = '#FF5722';
    }

    return $colors;
}, 10, 2 );

Gotchas

• All hot path. Same caveats as mam_app_settings_get_setting — early-return when not applicable, cache aggressively.
• Per-scope option keys. Each filter resolves to a different option key; don’t try to construct keys yourself.
• The cascade is in the data manager. Don’t try to re-implement.
• Frozen contracts. Many call sites depend on the existing signatures and cascade behavior.

Related articles

• Settings cascade overview
• Per-button and per-role settings
• Hook: mam_app_settings_get_setting
• Hook: mam_app_settings_get_buttons
• Hook: mam_app_settings_get_tab_bar_settings

Metadata