<aside> <img src="/icons/unlock-keyhole_purple.svg" alt="/icons/unlock-keyhole_purple.svg" width="40px" /> Needs are objects designed to be shared beyond the container they are created in, they are shared with the entire ecosystem. Only write needs you are comfortable sharing with the ecosystem of the container you create the need in. What is an ecosystem?
</aside>
<aside> <img src="/icons/clothes-button_purple.svg" alt="/icons/clothes-button_purple.svg" width="40px" /> A Need is an ask for support. The purpose of a need is to be distributed outside the container it is created in in order to find someone with the right expertise or resources to pick up the need.
</aside>
<aside> <img src="/icons/shorts_purple.svg" alt="/icons/shorts_purple.svg" width="40px" /> On the container page, use the shortcuts “add” button or the shortcut “create” button at the top of your screen
</aside>
When you create a need it’s crucial to fill in the fields properly: remember you are asking something from someone who is looking for a good opportunity to spend their time on. They will be looking at other opportunities.
<aside> <img src="/icons/lock_purple.svg" alt="/icons/lock_purple.svg" width="40px" /> In the Manage section of the container, in the privacy and security tab, container admins can decide who can create needs. It can be either admins only, or all members.
</aside>
A Need is visible by Ecosystem members. If a user can see the need they can participate in the needs' discussion.
e.g., if a project is linked to a community and a hub, its needs will be shared with the community and the hub, even if the project is set to visibility for members only.