# FLIP: Capability Controllers

**URL:** <https://forum.flow.com/t/flip-capability-controllers/2796>\
**Category:** 🏄🏻‍♀️ Cadence\
**Created:** [February 8, 2022, 11:02pm UTC](https://forum.flow.com/t/flip-capability-controllers/2796 "2022-02-08T23:02:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheOneSock](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.flow.com/theonesock/32/185_2.png) [@TheOneSock](https://forum.flow.com/u/TheOneSock)\
**Post date:** [February 8, 2022, 11:02pm UTC](https://forum.flow.com/t/flip-capability-controllers/2796/1 "2022-02-08T23:02:19Z")

</div>

Hi everyone,

I would be really interested in your opinion of this [FLIP: Capability Controllers](https://github.com/onflow/flow/pull/798).

The FLIP argues that the current system of creating, sharing and managing cadence capabilities is unwieldy and difficult to grasp, and proposes a possible solution to make capabilities easier to control.

Comments are very welcome!

---

<div class="post-metadata">

**Author:** ![AskAlice](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@AskAlice](https://forum.flow.com/u/AskAlice)\
**Post date:** [February 8, 2022, 11:44pm UTC](https://forum.flow.com/t/flip-capability-controllers/2796/2 "2022-02-08T23:44:24Z")

</div>