I have `config.write` but I can't change the configuration
The account's Configuration screen is read-only. Values can be written at the platform and in a tenant, not at an account.
What happened
You opened the account's Configuration screen. You see the values and their sources but cannot edit them. The screen says that the product has no path yet that writes at the account scope.
Why it happens
In inlorus today, configuration values are written at the platform (its Configuration screen) and in a tenant. The account screen exists to show where a value comes from. The screen being read-only even though you have the permission is not a permission problem; that path does not exist yet.
What inlorus does
- Even if you have the permission, it shows no write control, because there is nowhere for it to write.
- It says so in a sentence separate from a permission refusal and states where the value can be changed.
What you do
- If the value you want to change is for a tenant, switch to that tenant and write it from the tenant's Configuration screen.
- If a value should be the same for every tenant, set it at the platform on the platform's Configuration screen (Set a value at the Platform); tenants inherit it unless they set their own.
How to keep it from happening again
- Before changing a setting, read on the Configuration screen where it is written and where it is inherited from.