diff --git a/14/umbraco-cms/tutorials/multisite-setup.md b/14/umbraco-cms/tutorials/multisite-setup.md
index b68e34ed446..d29e8438b69 100644
--- a/14/umbraco-cms/tutorials/multisite-setup.md
+++ b/14/umbraco-cms/tutorials/multisite-setup.md
@@ -56,5 +56,6 @@ While such a setup might be handy, it also comes with drawbacks. It is important
 * Might increase resource usage.
 * Could interfere with editors' workflows, especially if there are multiple people working on both websites at once. That is because the solution will still use one database for both websites.
 * Limit your options in regards to developing new features and making schema changes.
+* If the project has any issues, this will affect all websites.
 
 On Umbraco Cloud-hosted sites we recommend using the [Baseline](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) functionality - which comes with added benefits, and offers increased stability compared to the multisite solution in a single project.