diff --git a/ExistingProjects/ERP5.mdwn b/ExistingProjects/ERP5.mdwn
index efd9588d5d812d0fffc819a917ff7906900c488c..21cbf717de3c45d835fb3b5215efd5e348139b22 100644
--- a/ExistingProjects/ERP5.mdwn
+++ b/ExistingProjects/ERP5.mdwn
@@ -63,9 +63,12 @@ So all of them below are basically possible.
 
 ### Evaluation of [[Fund Accounting|UseCases/FundAccounting]] UseCases
 
-- [[Fund-only View|UseCases/FundAccounting#fund-view]]
-- [[Funds as part of whole org View|UseCases/FundAccounting#fundless-view]]
-- [[Ignore Funds for operations|UseCases/FundAccounting#fundless-view]]
+My intuition tells(although it is necessary to think the design carefully) that this can be done by
+implementing a security model based on project/group category with hierarchical structure. Since ERP5 accounting supports hierarchical structure to manage data, non-profit org can be parent and all fiscal sponsorship users can be children. This way, non-profit org can view everything and each fiscal sponsorship user can view only his data.
+
+- [[Fund-only View|UseCases/FundAccounting#fund-view]] Possible
+- [[Funds as part of whole org View|UseCases/FundAccounting#fundless-view]] Possible
+- [[Ignore Funds for operations|UseCases/FundAccounting#fundless-view]] Possible
 
 ### [[UseCases/Collaborating]] evaluation
 - [[Simultaneous Editing of Ledger|UseCases/Collaborating#simultaneous-ledger-edits]]: FIXME