diff --git a/README.md b/README.md
index 82b0e75d35..48aaeaa579 100644
--- a/README.md
+++ b/README.md
@@ -42,9 +42,13 @@ script/zed_with_local_servers --release
 
 If you trigger `cmd-alt-i`, Zed will copy a JSON representation of the current window contents to the clipboard. You can paste this in a tool like [DJSON](https://chrome.google.com/webstore/detail/djson-json-viewer-formatt/chaeijjekipecdajnijdldjjipaegdjc?hl=en) to navigate the state of on-screen elements in a structured way.
 
+### Internal Only Features
+
+Many features (e.g. the terminal) take significant time and effort before they are polished enough to be released to even Alpha users. But Zed's team workflow relies on fast, daily PRs and there can be large merge conflicts a feature branch diverges. To bridge this gap, there is an `internal` field in the Settings struct that is set to `true` if the user is Zed staff and `false` otherwise. Note that this field is only read once, on startup, and is only set when a user has logged in to github. Once a staff member logs into github from the Zed application, they must restart Zed for the internal feature flag to be set to true.
+
 ### Experimental Features
 
-A feature flag can be added to Zed by:
+A user facing feature flag can be added to Zed by:
 
 * Adding a setting to the crates/settings/src/settings.rs FeatureFlags struct. Use a boolean for a simple on/off, or use a struct to experiment with different configuration options. 
 * If the feature needs keybindings, add a file to the `assets/keymaps/experiments/` folder, then update the `FeatureFlags::keymap_files()` method to check for your feature's flag and add it's keybindings's path to the method's list.