Bulk User Import File Definition | ||||||
|---|---|---|---|---|---|---|
Server Usage | ||||||
PFM | Pro | Req'd | Profile Manager Usage | Workcloud Communication PTT Pro Usage | Comments | |
samaccountname |  | | | This is the User Name field in Profile Manager and is required. Field accepts from 1 to 255 alphanumeric and special characters. | The User Login field in Zebra PTT Pro and is required. Field accepts from 1 to 24 alphanumeric characters, dash, and period | The column heading for this element must be samaccount name. Create user names that meet the requirements in both systems. |
password | <Not used> | <Not used> | Not used but column is required. | |||
firstname | | | | Field accepts from 1 to 255 alpha numeric characters and special characters. | Field accepts from 1 to 30 alpha numeric characters and special characters. | The first name must meet the requirements in both systems. |
lastname | | | | Field accepts from 1 to 255 alpha numeric characters and special characters. | Field accepts from 1 to 30 alpha numeric characters and special characters. | The last name must meet the requirements in both systems. |
userRoleLevel | | | Specify role level used in hierarchical role selection based on the attribute "memberof". | <Not used> | If both userRoleLevel and userroles columns are populated, userRoleLevel is used and the useroles column is ignored. Separate multiple role levels with commas. The role level is case sensitive. When the level is created, the same case must be used in the user import file. Roles must exist in Profile Manager before the import is executed. | |
userroles | | | Specify the user role. User roles must be created prior to import. | <Not used> | If userRoleLevel is not specified, then this column is a comma separated list of roles. One or more roles must be defined. Roles must exist before the import is executed. | |
organization | | Field describing the users organization. Field accepts from 1 to 255 alpha numeric characters and special Characters. | <Not used> | Descriptive field. | ||
site | | | | Field describing the department. Field accepts from 1 to 255 alpha numeric characters and special Characters. | <Not used> | For PFM this is a description field. In PTT Pro this field must exactly match any existing department for the customer. If the department does not exist, it is created. |
forceLogout | | When enabled if the user logs in on another device without logging off of the first device, the system automatically logs off the user from the first device. | <Not used> | Value is either 'true' or 'false' | ||
authenticationMethod | | | The supported option is OAUTH2. | <Not used> | The PTT Pro server does support Oauth to provide a shared device model, but there is no actual Authentication Method switch per user. | |
phone | | <Not used> | Phone number if SMS activation is planned. | This is not a required field. | ||
email | | <Not used> | Email address of the user. | This is not a required field. | ||
oauthName | | | <Not used> | Populated in the PTT Pro server to support a shared device model. | Format can be either: "domain\username" or "username@domain" | |
GroupUserTemplate | | | <Not used> | Defines the talk group template to use. Four possible entries are: associate, SME, associate, or standard. | Used in the PTT Pro server to determine talk group behavior. | |
featureKeysTemplate | <Not used> | Assigns a pre-configured template to the user. The template must exist in the PTT Pro server for this to be assigned. | Must match an existing PTT Pro Feature Keys template. | |||
clientSettingsTemplate | | <Not used> | Assigns a pre-configured Template to this user. The Template must exist in the PTT Pro server for this to be assigned. | Must match an existing PTT Pro Client Setting Template. | ||
PBX Extension | <Not used> | <Not used> | Optional pseudonym for the PBX extension. Used in conjunction with Extension Manager Hidden Department to reserve and extension for the identified user. | |||
