---
# System prepended metadata

title: Teams

---

[docs.crisis.network](https://docs.crisis.network)


---

# Teams
Teams cannot (and should not) stop any member from publishing their own proposal. However, they can advocate for or against any proposal — like any other member. Teams should help members review and improve proposals in their respective areas of expertise.

1. The primary responsibility of each teams is to write proposals in their respective areas and executing them once their proposal has passed.
1. Teams will set their own internal operating rules such as quorum, what, how, and when to write proposals, subdivision of teams, etc.
    1. All team documents are by default public to the DAO, but the team may choose to make its document private.
    2. If documents are made private, the team must disclose the existence of the private document to the DAO. This is known as the "Secret Document Rule"
4. New teams can be formed by the passage of a full DAO proposal.
    1. Team members can be added or removed by the passage of a full DAO proposal.
6. A team can be disbanded by the passage of a full DAO proposal.
    1. A team member may resign at any time.
    2. The DAO must vote in a replacement through the passage of a full DAO proposal if the team membership falls to two. However, the team may continue to operate with only two members while a proposal is pending.
    3. If the team membership falls to one member or fewer, the team will be temporarily merged with another team until the team has three or more members. 
    4. The SECURITY team will determine which of the teams to merge with.
10. Minimum number of members per team is 3, the maximum is 6.
    1. A team cannot be created with fewer than 3 initial members.
    2. A team must pick a coordinator as the primary contact to streamline communication, but a coordinator has no special powers unless granted by the team by vote.


# Permanent Teams
These permanent teams will operate unless disbanded by the passage of a full DAO proposal:

## SECURITY
1. In charge of operational security of the DAO and its assets including member data privacy.
2. Has power to halt all token issuance, transfers, transactions, acquisitions, and sales to the extent possible for up to 72 hours due to security threat or risk of exploit. Hereby known as the "Emergency Lockdown."
    1. An Emergency Lockdown may be extended beyond the initial 72 hours by the passage of a full DAO proposal.
    2. An Emergency Lockdown may not be extended indefinitely.
3. Manages the multisig and its list of members for the DAO wallets.
    1. However, changes to any multisig members or thresholds requires the passage of a full DAO proposal.

**Members:**
Harper (coordinator), Shazow, Seanbonner, Huh, Tricia Wang, WhatAsherThinks

## MEMBERSHIP
1. Vetting new members, proposing members, quits, bans, rules, and behaviors.
1. Acts as the final decision-maker on member ethics and behaviors. Issues regarding the MEMBERSHIP team's behavior will be resolved by the OPERATIONS team.
1. Acts as a private channel to discuss problems or issues with current or proposed members from other current or proposed members.
1. Membership team documents regarding private member issues are exempt from the Secret Document Rule and the existence of these documents are not required to be disclosed to the full DAO.

**Members:**
HT (coordinator), TaraTiger, Jacob, WhatAsherThinks

## SCOUTING
1. Finds external projects to buy, partner, or work with.
1. Manages the process for vetting project and especially helps identify risks.
1. Responsible for defining when and how to acquire and/or sell an asset and executing the transaction.

**Members:**
Seanbonner (coordinator), leonc, ǝʞᴉɯ, micah, Tricia Wang


## OPERATIONS
1. Sets rules and rates for member and non-member compensation.
2. Sets the rules for expenses and approves them.
3. Manages the treasury to achieve a high return at the minimal acceptable risk.
    1. All new treasury investments or changes to existing investments must pass a full DAO proposal.
4. Creates docs, templates, education materials, brand visuals, and content, including a comms manual.
5. Decides on tools and applications the DAO will use, build, and/or support.
    1. The SECURITY team may ban any tool if it poses a security risk.

[**Operations Team Page >>**](https://hackmd.io/JJ5ZZMRHT-ychXqlYA08vQ)

**Members:**
Huh (coordinator), leonc, Tolar

# Temporary Teams
Will work until a more detailed charter is approved:

## CHARTER (temp)
1. Propose a new Operating Agreement (currently at docs.crisis.network) until a one passes.

**Members:**
Nicwn (coordinator), Huh, TaraTiger, HT, Hadjar


---
**Crisis DAO** : [Docs](https://docs.crisis.network) | [Twitter](https://twitter.com/crisisdao) | [Snapshot](https://snapshot.org/#/crisisdao.eth) | Discord (Invite-only) |