diff --git a/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx b/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx
index 68c3a5a282..069df6cc81 100644
--- a/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx
+++ b/packages/twenty-docs/user-guide/legal/how-tos/legal-faq.mdx
@@ -108,4 +108,18 @@ No, Twenty is in the process of becoming HIPAA compliant.
 </Accordion>
 </AccordionGroup>
 
+## Licensing
+
+<AccordionGroup>
+<Accordion title="If I change the code to add features only for internal use by my team, do I have to publish those changes?">
+No. Running a modified version for your own team is not distribution, so no publication obligation arises. The AGPL's network clause applies when people outside your organization interact with your modified instance over the network.
+</Accordion>
+<Accordion title="If I create a separate front end and use Twenty as a backend as-is, do I have to publish those changes?">
+No. Your front end is your own, separate work, and talking to Twenty through its APIs does not change that. Since Twenty itself is unmodified, there is nothing to publish.
+</Accordion>
+<Accordion title="If I change the code to add features to re-sell it, do I have to publish those changes?">
+Yes, since you're modifying code to distribute it to others, you're required to publish those changes. If you don't want to publish your changes, you can obtain Organization license.
+</Accordion>
+</AccordionGroup>
+
 If you have more questions, please check our [Terms and Conditions](https://twenty.com/terms), [Privacy Policy](https://twenty.com/privacy-policy) and [Trust Center](https://trust.twenty.com/). If your questions are still unanswered, send them to [contact@twenty.com](mailto:contact@twenty.com) or via support chat.