Public statuses
| Status | Meaning |
|---|
| clear | Currently included in the ranking. This can change after later cheating or missed evidence. |
| under review | Application is open. |
| not eligible | A prerequisite failed before review or after a report case closed as clear. |
| uncertain | Review ended without clearance and without closing as cheater. |
| cheater | Project cheating finding or external cheater database match. |
| no status | The project has a local user record but no decision for that user. |
| not found | No local user record was found for the looked-up handle. |
Decision source
Decision source is public and appears in Lookup.
| Source | Meaning |
|---|
| review | Status came from submitted review votes. |
| admin decision | Admins set the final status. |
| external match | External cheater database from another source matched the user. This does not open a reviewer report case. |
Available roles
| Role | Who can have it |
|---|
| non-member | User without member, reviewer, or admin rights. This can apply to clear and non-clear users. |
| member | Clear user with member rights, but without reviewer or admin rights. |
| reviewer | Clear user with reviewer rights granted by an admin. |
| admin | Clear user with admin rights. |
Role changes
| Change | Rule |
|---|
| self-owned Apply clearance | If reviewers or admins clear a self-owned Apply review, the user gets member role. |
| nomination or direct clearance | Member nomination and admin direct clearance grant non-member role unless an admin explicitly grants member. |
| non-member authentication | Clear non-members become members after they authenticate their clear Codeforces handle. |
| loss of clearance | Review, report cases, admin decisions, or external matches can remove clear status. Clear-only roles then return to non-member. |
Admins can override roles.