# Proposal Life Cycle

The user flow for a Web3 community organization can vary depending on the specific implementation and the goals of the community and admins involved. Here is a general overview of a typical user flow for a DAO:

1. **Setup and Onboarding** 

   1. **dTerminal** offers two primary roles: Admin and Moderator. While both roles have Moderator-related features, the Admin role has additional privileges to modify crucial settings. Admins can configure token gating rules, manage categories and tags, add or remove other admins and moderators. For more details, please refer to the [**User Structure**](/dterminal-user-guide/user-guide/user-structure.md) section above.
   2. In a DAO, members typically own tokens that represent their stake in the organization. These tokens can be obtained through various methods, such as contributing to the community or purchasing them on a cryptocurrency exchange. dTerminal allows gating certain functionalities based on a user's token holdings. For instance, posting or voting may be restricted unless the user possesses a sufficient number of tokens as defined in the gating rules.
   3. Once users become members of the tokenholder community, by connecting their wallets and setting up profiles, they gain the ability to engage in the organization's governance. This includes proposing changes, voting on proposals, and providing feedback on community decisions through **dTerminal**.

2. **Submission of a new Idea**

   1. A DAO member (Author) creates a new discussion topic and proposes a new idea to the DAO community.
   2. The idea gets verified by a DAO admin before making it visible to the community. The admin team ensures that the proposal is relevant and meaningful to the DAO ecosystem and its development and otherwise meets community guidelines.
   3. The admin opens the topic to the community.
   4. The community members engage with the topic and the author/team to gather feedback and initial support informally.
   5. The admin approves or rejects the topic based on the feedback received from the community.
   6. Approved topics go through the next step. 

   <figure><img src="/files/oStXXXA5md8JpgYu45Ch" alt=""><figcaption></figcaption></figure>

3. **Review and Analysis of Formal Improvement Proposal**&#x20;

   1. The admin creates a draft proposal template and assigns a unique IP (improvement proposal) number to the draft proposal, which will be used throughout all stages of the proposal lifecycle.
   2. The admin asks the Author to add the necessary details and ask questions if certain areas of the proposal are unclear.
   3. Once the admin team has reviewed the IP, identified the operations and risks, and met support levels, the proposal, and analysis are presented to the Special Counsel.
   4. The Author may ask the admin to withdraw the proposal at any stage during this phase.
   5. A formal IP (Proposal on [Snapshot](https://snapshot.org/#/)) is created from the draft proposal if it passes the review process conducted by the admins, moderators, and special counsel team.&#x20;

   <figure><img src="/files/fBeyKvZ8eVihpQmammoz" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/Lw3CdDrOVyYWAK5LvbMZ" alt=""><figcaption></figcaption></figure>

4. **Proposal Voting**

   1. The admin team can create the Formal IP before voting is opened.
   2. If the Formal IP (Proposal on [Snapshot](https://snapshot.org/#/)) has been approved for voting by the Special Council members, it is then posted for community voting.
   3. The community members can vote on the IP until it's active and open for voting.
   4. Any token holder can delegate their vote, provided that, in the absence of an IP approved at a later date, the admin may establish guidelines for token voting delegation.
   5. The DAO admins take necessary actions once the IP is closed for voting.

   <figure><img src="/files/ypldTAMjbQvKViPZ1vNO" alt=""><figcaption></figcaption></figure>

The full proposal life cycle can be seen here:

<figure><img src="/files/ZqIJZSkuE5BNNaaEyIQn" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dterminal.io/dterminal-user-guide/user-guide/proposal-life-cycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.