Skip Navigation

Format a user import CSV file

The following table describes the required import CSV formatting standards.
Field Name
Description
Is Mandatory?
Username
The Username is a value that identifies a user in the
BlackBerry AtHoc
system and the user repository (for example, LDAP or Microsoft Active Directory) within your organization. The Common Name field must contain a unique value, such as an Employee ID or a Windows user name. After the Common Name is registered with the
BlackBerry AtHoc
system, the user is linked to the user profile within your organization.
The username cannot contain spaces or any of the following characters: [ ] : ; | = + * ? < >. Leading or trailing spaces are trimmed during the import process. After the leading or trailing spaces are trimmed, the username is accepted and the user is imported.
Yes
Status
Use the Status column to enable, disable, or delete a user. The following attribute values can be used:
  • Enabled: Enable the user
  • Disabled: Disable the user
  • Deleted: Delete the user
The import file must contain a Status column, but the column can be empty. If the Status column is empty but the database contains Status information, the current Status information is overwritten and replaced by the empty values in the import file on import.
Yes
Hierarchy Common Name
Use the hierarchy common name to specify the location in your User Base Hierarchy where the user is a member. Click
Users
>
Users
> The Groups icon to view your organizational hierarchy.
No
Static Distribution List Common Name
Use the static distribution list common name to specify a static distribution list to add users to. Click
Users
>
Users
> The Groups icon to view your distribution list hierarchy.
There can be multiple Static Distribution List Common Name columns. If the user does not already exist, this option can only be used to add the user to a static distribution list. A valid value is "Yes" (the user will be added to this static list.) If the user already exists, use this option to add or remove the user from a static distribution list. Valid values are "Yes" (the user will be added to this static list) or "No" (the user will be removed from this list.)
No
User Attribute Name
Specify a user attribute name as column heading to update user attribute values.
No
Device Common Name
Use the device common name to specify a device name in the import file. For pager addresses, specify the pager carrier ID followed by a colon (:) before the pager number. For example, to import pager number, "5551222" with pager carrier ID 3, use "3:5551222" as the pager address in the CSV file. To view the list of pager carrier IDs and names, see "Pager carrier IDs and names" in the
BlackBerry AtHoc
Create and Publish Alerts
guide.
No
Password
Passwords must conform to the password rules set in
Settings
>
Security Policy
>
Password Update Rules
.
No
Organization
Only available for super enterprise or enterprise organizations with user uniqueness enabled. Specify the display name for each organization. New users are created in the specified organization and existing users are moved to the specified organization.
If the following error occurs while importing users in a super enterprise or enterprise organization: "[Organization]: Column was not recognized as an attribute or device", it is because user uniqueness is not enabled. You can enable user uniqueness in
Settings
>
General settings
.
No
Subscribed Organizations
Only available when the organization subscription feature is enabled and organizations are available for subscription. Specify organizations to subscribe users to. You can subscribe a user to a maximum of ten organizations. Separate organization names with a comma. You can also specify start and end dates for the subscription. Use the date format of your organization. Separate the start and end dates with a pipe (|) character. For example: Sub-Org1: 4/5/2021|8/8/2021, Sub-Org3: 5/5/2021|, Sub-Org4: |7/7/2021.
No