Enter or upload CSV user data with header. For example:

name,email,affiliation,roles
John Adams,john@earbox.org,UC Berkeley,pc
"Adams, John Quincy",quincy@whitehouse.gov

Or just enter an email address per line.

Supported CSV fields include:
name    User name
first    First name
last    Last name
affiliation    Affiliation
roles    User roles: blank, "pc", "chair", or "sysadmin"
tags    PC tags (space-separated)
add_tags, remove_tags    PC tags to add or remove
collaborators    Collaborators
follow    Email notification: blank, "reviews", "allreviews"

Submitted by Elmer van Chastelet on 9 August 2018 at 11:56

On 28/01/2019 13:40, Elmer van Chastelet wrote:
> We don't have a hotCRP-specific output format for committees, but I'd
> like to know what format HotCRP expects here, so we can add support for
> this.

Here is what HotCRP says. It seems to expect a header line containing
standard field names, then N lines containing the actual data.

   Enter or upload CSV data with header, such as:

   name,email,affiliation,roles
   John Adams,john@earbox.org,UC Berkeley,pc
   "Adams, John Quincy",quincy@whitehouse.gov

   Or just enter an email address per line.

   Supported CSV fields include:

   email
       Email

   name
       User name

   first
       First name (given name)

   last
       Last name (family name)

   affiliation
       Affiliation

   roles
       User roles: blank, “pc”, “chair”, or “sysadmin”

   tags
       PC tags (space-separated)

   add_tags, remove_tags
       PC tags to add or remove

   collaborators
       Collaborators

   follow
       Email notification: blank, “reviews”, “allreviews”, “none”