diff --git a/FAQ.md b/FAQ.md
index ea41e30..838cf72 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -210,4 +210,8 @@ You can read the following section for more details: [Performance](https://tahoe
 **<a name="Q30_authorization">Q30:</a> How can I prevent intruders from using my Tahoe-LAFS web-interface? Even without knowing exact object caps they will be able to see statistics and be able to upload objects.**
 
 A: There is no such built-in authorization capability in Tahoe-LAFS. Security is based on secret object caps.
-Meanwhile you can forbid unauthorized access to your Tahoe-LAFS WUI by using firewall (iptables, ipfw etc.) and combining it with proxy-server authorization and redirection (nginx, apache, squid etc.)
\ No newline at end of file
+Meanwhile you can forbid unauthorized access to your Tahoe-LAFS WUI by using firewall (iptables, ipfw etc.) and combining it with proxy-server authorization and redirection (nginx, apache, squid etc.)
+
+**<a name="Q31_multiple_users">Q31:</a> I've got multiple users connected to same directory and their experience is really poor. What can I do?**
+
+A: If many people have write access to the same directories, then they'll probably get failures and stalls a lot, regardless of the frontend, and they might eventually if they keep doing it lose the data, if a bunch of servers get disconnected right when they are doing that. Currently we advise people to adopt a style of usage where each user gets exclusive write-access to one directory, and read-access to the directories of many other users. It is a limitation that we hope to lift in the future.
\ No newline at end of file