> For the complete documentation index, see [llms.txt](https://builderman.theravenhub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://builderman.theravenhub.com/commands/developer-commands/processing-suggestions.md).

# Processing suggestions

### General Information

Once a suggestion has been approved by your Team, it will be sent to the already configured todo-channel ([/todo-channel](/commands/owner-commands/todo-channel.md)). There a Developer or higher can process the suggestion.

### Requirments

* The User must have either the Developer ([/dev-role](/commands/owner-commands/dev-role.md)) or Manager Role ([/manager-role](/commands/owner-commands/manager-role.md)), or be an Administrator

### How to use

Once a suggestion has been sent to the ToDo-Channel it will look something like this: 

![](https://media.discordapp.net/attachments/731166978806644827/937554645008650260/Suggestions_To-Do_Channel.gif?width=790\&height=702)

1. **Reserve the Ticket**\
   Developers can reserve the suggestions. This is mainly for organizational purposes. In addition, when an update is published, the developer is credited for implementing the suggestion.
2. **Send it in the publishment Queue** \
   As soon as a suggestion is implemented by a Developer, they can move it to the publishment queue. This deletes the suggestion from the channel and moves it to the final stage. As soon as a game update is now published, this suggestion is attached as implemented. This action can not be undone.
3. **Publish it immediately**\
   Unlike the "Publish Queue" button, this is not intended for game updates but rather for game hotfixes. The suggestion is published directly as a single update.
4. **Delete the suggestion**\
   If the developer decides that you do not want to implement the suggestion, you can delete it using the "Delete" button. **Important: The user will not be informed that the suggestion has been deleted.**