Manage Users Managing Users
Polycom, Inc. 351
• All fields for a single user must be on a single line and end with a new line
or end of file character. The line after a new line is assumed to be for
another user.
• All fields for a single user must be on a single line and end with a new line
or end of file character. The line after a new line is assumed to be for
another user.
• Commas (‘,’) are used as field separators and cannot be embedded in a
field. All commas must be included, even before fields that are optional.
Each field’s leading and trailing white space (blanks and tabs) is ignored
(does not become part of the field value).
• Unicode characters are allowed in the file as long as they are valid for the
field type.
• Blank lines are allowed and are ignored.
• A header line is not allowed in the CSV file. All lines must either represent
a user or be blank.
• The following fields are required:
Username, First Name or Last
Name
, and Email.
• Other fields can be left blank, but not skipped.
Field Usage Notes
Username The username must be unique across the entire
RealPresence Resource Manager system. (The
recommended naming convention to ensure uniqueness
is specified in section
If a specified username already exists in the selected area
(or in the system, if Areas is disabled), then the system
assumes you wish to update the existing user’s
information.
If a specified username already exists in a different area,
then the user is neither added nor updated and an error is
issued.
Role(s) Role names are case sensitive.
To specify multiple roles for a user, separate the roles with
a pipe (‘|’).
If the Role(s) field contains only area-specific roles, then
the user will automatically be set to manage the selected
area.
