Forms
Collect structured responses — applications, feedback, reports — through a page where members sign in with Discord.
Forms let you collect structured responses from your members — staff applications, feedback, bug reports and more. You post a form to a channel, members click through to a page, sign in with Discord, fill in your questions and submit. Every answer is saved for you to review.
You build forms in the dashboard under Forms → Form Panels. Each form is an embed plus a list of questions.
Create a form
- 1
Open Forms
In the dashboard sidebar, go to Forms → Form Panels and click Create form. New forms start as a Draft, so they aren't live yet.
- 2
Build the embed
Set the title, description and colour of the message that's shown with the form when you post it.
- 3
Add questions
Add each question with a Label, a Type and a Required toggle. You can add up to 25 questions per form.
- 4
Set it to Active
Switch the form from Draft to Active once it's ready to receive responses.
- 5
Send it to a channel
Pick a channel and press Send form. Rimpllee posts it so members can start submitting.
Question types
Each question has a Label, a Type that decides how members answer, and a Required toggle that forces an answer before they can submit.
| Type | How members answer |
|---|---|
| Short answer | A single line of text |
| Paragraph | A longer, multi-line block of text |
| Multiple choice | Pick exactly one option from a list |
| Checkboxes | Pick any number of options from a list |
| Dropdown | Choose one option from a dropdown menu |
How members submit
- A member clicks the posted form.
- They sign in with Discord so you know exactly who answered.
- They fill in your questions and press Submit.
View responses
Open the form's View submissions page in the dashboard to read every response. Each submission shows who answered, when they submitted, and every question paired with its answer.
All submissions in one place
Forms → Submissions collects the responses from every form panel at once. Filter by panel or by status, and search on user ID or name. Entries you have already handled fold themselves shut, so what still needs you stays on top.
Approve or deny a submission
Submissions start as Pending. Open Forms → Submissions (or a single panel's submissions page) and decide on each one. Approving hands the member the roles you configured; denying lets you add an optional reason. Either way they get a DM, and the decision is final so nobody is reviewed twice.
- 1
Pick the roles
Under Send to channel, choose the roles an approved member should get. Roles that sit above Rimpllee's own role are greyed out, because it could not hand them out anyway.
- 2
Write the two messages
Press the gear next to the roles to write the approved and denied DM. Leave one empty to send nothing for that outcome.
- 3
Review
Approve or deny from the dashboard. The card folds up and shows who decided, when, and which roles were given.
Placeholders in those messages
Both messages accept {user_name}, {user_mention}, {user_id}, {form_name}, {guild_name} and {staff_name}. The approved message can also use {roles}, and the denied message {reason}. Type a reason while denying and it always reaches the member, even if your message never mentions {reason}.
Roles are handed out by the bot
If Rimpllee cannot give a role (it sits too high, or it was deleted), the decision still stands and the dashboard tells you which role failed, so you can add it by hand. A member with closed DMs is reported the same way.
Log channel
Give a form a submission log channel and every new response is posted there, with a button that takes you straight to that exact submission on the dashboard. Set it under Send to channel, and it can be a different channel per form.
Forms vs. intake questions
Forms are standalone submissions members fill in on a page. If you instead want a quick popup when someone opens a ticket, use ticket intake questions — those appear right inside Discord as a member opens a ticket.
Components V2 (Premium)
Premium servers can switch a form panel into Components V2, the same drag-and-drop layout system as ticket panels. Stack text, sections (text + thumbnail), image galleries, separators and containers with accent colours instead of one embed.
Drop in the Button component to say where the form button goes. Its label, emoji and colour stay in the Form button section, and it opens the same web page or Discord popup as before. Leave it out and the button is still added at the bottom, so a posted form can always be opened.
Components V2 replaces the context text and the embed with a custom layout. It's a Premium feature, see Plans & limits.