# Hybrid Custody **URL:** \ **Category:** Product & Ideas\ **Tags:** account-model\ **Created:** [January 5, 2023, 10:03pm UTC](https://forum.flow.com/t/hybrid-custody/4016 "2023-01-05T22:03:53Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![bluesign](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/bluesign/32/1359_2.png) [@bluesign](https://forum.flow.com/u/bluesign)\ **Post date:** [January 6, 2023, 7:30pm UTC](https://forum.flow.com/t/hybrid-custody/4016/4 "2023-01-06T19:30:51Z")
This has many benefits, I was a bit hesitant in the beginning about security side of things, but after reading about use cases and motivation, I think it can be implemented securely without losing any of the benefits. Some benefits I see: - This will be great for developers: Capability model was too confusing to many of the newcomer developers, actually it was even complex for all ( me included ) - Can provide great isolation between dapps. - Not requiring signing and allowing dapp to run action on behalf of the user without interaction is great UX. This can even make FCL obsolete. - it is great for onboarding but also makes dapps to have no excuse to have walled gardens anymore, so this has great benefit for users. - Wallets even auto create temp accounts when a dapp connected, link to main account, and add dapps public key ( so dapp and wallet can use the account at the same time ) - Another good benefit is: now there is a misconception about `each account is a user` and `each tx is user interacted`, I think this will help to clear that misconception. - If we can somehow tag this child accounts to dapps, I think it can be a valuable metric about dapp usage etc. > [@dete](#): > > Critically, the account granting the delegation (the “child”) must explicitly provide this access, and can revoke this access at any time for any reason. I think here “Irrevocable access” can be also equally true. If dapp ( let’s say TopShot) will onboard me to a child account, I would like my parent account ( let’s say blocto ) should have irrevocable access to that child account ( unless I want to break the relation ) In general I am really excited about things we can do with this child accounts. --- _[View the full topic](https://forum.flow.com/t/hybrid-custody/4016)._