Config Management
Lists the config values stored in the selected Tenant's own record; you edit them one by one, add new keys, or replace them all with the Account's or the Platform's values.
For: Tenant administrator
What's on this screen
- Each config key in the Tenant's own record, with its JSON value. If the value came from a copy, the row shows
source: accountorsource: platform. - The Take defaults box: the Take from Account and Take from Platform buttons.
- The Add a new config key form.
- A Tenant switcher, if you are a member of more than one Tenant.
What you can do
- Change the value in a row as JSON and press Save: a number
30, on/offtrue, text"required". - For a new key, type the key name and the JSON value and press Add.
- To replace all values at once, press Take from Account or Take from Platform.
Keep in mind Take defaults doesn't ask for confirmation: all of the Tenant's own values are deleted and the values in the chosen scope's own record are copied. The copy isn't a link.
How it differs from the Configuration screen
This screen shows only the values the Tenant stores itself. A setting in effect from the Account or Platform doesn't appear here at all, so an empty list doesn't mean "no settings". It picks the Tenant from your membership selection, not from the console's scope switcher, and it doesn't know the configuration definitions.
The Configuration screen does the same two write actions, with the whole definition catalog and where each value comes from.
Keep in mind When a save is rejected, this screen always says "enter a valid JSON value"; but the reason may also be an attempt to loosen a floor set by the parent scope. If the reason isn't clear, try the same value on the Configuration screen; there the rejection reason is spelled out.
Tip Seeing it needs config.read in this Tenant; changing it needs config.write.