diff --git a/docs/framework/setting.md b/docs/framework/setting.md
index 06f5a151121174bc5b1861cc2e1ce419bf396957..5f0fa5bba6b573969aabf3f238796ede1539e4ca 100644
--- a/docs/framework/setting.md
+++ b/docs/framework/setting.md
@@ -153,6 +153,7 @@ As with core settings, all settings declared in extensions should have appropria
 1. Provide that the settings folder is declared [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/multisite.php#L268).
 2. Declare settings as in the same standard as CiviCRM Core [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/settings/Multisite.setting.php).
 3. Create Settings form, a [good example of generic metadata based setings form in an extension](https://github.com/eileenmcnaughton/nz.co.fuzion.civixero/blob/master/CRM/Civixero/Form/XeroSettings.php) - note that only the setting filter is non-generic
+4. Use `cv api system.flush` or `Admin → System Settings → Cleanup Caches` to flush CiviCRM caches and register your new settings metadata.
 
 ## Adding Setting Config to Admin Forms.