Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I'm currently setting up a layout for a website that's going to be a sort of "bracket" website, where users can sign up and they can be approved/denied by an administrator. I'm currently at a roadblock in my design process, because I can't figure out an appropriate way to handle mass user authentication.

For example, there will be bracket that any person who has registered on the website will be able to sign up for. When they sign up, they're put into a "waiting pool", where they're sorted by a system that puts them into four or five different skill groups (as to not match the best players against the worst). After everything is sorted, the people in the pool need to be "approved" for the tournament, which is where I'm having trouble.

If I have 100 people in this pool, what would be the most efficient way to display them for approval (this would only be done by an administrator on the back-end of the website)? I was thinking of listing them and having check boxes next to each person's username, but it seems like that would be tedious and time consuming. Is there any other way to handle this issue?

share|improve this question
    
What does the administrator need to know about each person when approving them? I'm wondering what information needs to be displayed in the approval interface. –  Matt Obee Oct 12 '12 at 15:01
    
From what I can tell right now, it would probably display something like: Username | SkillGroup | T.Entered, where the username would be a link to the respective profile, and T.Entered would be the tournaments entered so far. edit: I misunderstood. The administrators will be approving/denying users based on their preferences, some tournaments might not be appropriate for some users, but there's a good possibility they might sign up for it anyways. –  John Oct 12 '12 at 15:05
add comment

1 Answer

up vote 0 down vote accepted

There are two parts to the solution I would suggest for this.

I would firstly want to filter the list of people based on my criteria. So if I only want to approve people in the "intermediate" skill group (I don't know what the real groups are) who have also entered between 5 and 10 tournaments, I could filter the list to show only those people. Equally, if I know I want to reject beginners, I could filter the list to show only those people and then easily reject them.

Listing the people with checkboxes, as you mentioned, does seem sensible to me. That means I can select multiple people and then approve or reject them in a single action. I would include a single checkbox at the top that allows me to easily select all.

mockup

download bmml source – Wireframes created with Balsamiq Mockups

share|improve this answer
    
This is an awesome idea! I shared this with my administrators and they really liked the layout of this, so I guess this is what we're going to do. Thank you a lot! –  John Oct 13 '12 at 1:18
    
Good stuff. Happy to help. –  Matt Obee Oct 13 '12 at 10:16
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.