Review member requests

Everything members send in waits under Rewards › Requests, with a count on each page and in the sidebar. Members can send things in only while levelling is on, and Colossus never messages them about a decision.

Decide a request

1. Open the page: Level claims, Member pictures or Personal roles.
2. Find the member with Find a member, or work down the list.
3. Press the decision on the row. There is no reason to fill in.

A claim or a picture can be decided again later from the list of what was decided.

Level claims

Members send these with /claim once claims are on; see Import from another bot. Each row shows the level claimed beside Level now. Check it against the old bot first, such as with its /rank on that member.

• Approve: the level counts as an imported one, and nothing is announced. If several of a member's claims are approved, the highest counts.
• Deny: the claim doesn't count.

A member has one claim waiting at a time; a new /claim replaces it.

Member pictures

On Titan, from members allowed to change their rank card. A member holds up to 3 pictures, and /rank leaves a picture off until it is approved.

• Approve: /rank draws it.
• Turn down: it comes off their card, but takes one of their 3 places until they delete it.

Reset a member's card drops every change a member made, so /rank shows the server's card again.

Personal roles

On Pro, from members given a personal role; see Give perks to supporters and boosters. Each row shows Design sent beside Live now.

• Approve: Colossus makes or changes the role and gives it to the member, with only the parts their perks allow.
• Turn down: the role keeps its approved look. The member can send another.
• Reset: deletes an approved role from Discord and drops the member's designs, at once.

Who can decide

Manager and Admin decide all three; Viewer can't decide. Each page has its own permissions to see and to decide; see Give your team access.

If it doesn't work

• A page is missing from the sidebar. Your access doesn't include it, or the plan leaves it out.
• Discord refuses a personal role. The row says so. The bot needs Manage Roles and a role above the personal roles.