Contents
Required Columns
Optional Columns
Required Columns
Emails
The person's email addresses.
emails email address emailaddress email-address email_address email addresses emailaddresses email-addresses email_addresses employee email employeeemail employee-email employee_email employee emails employeeemails employee-emails employee_emails employee email address employeeemailaddress employee-email-address employee_email_address employee email addresses employeeemailaddresses employee-email-addresses employee_email_addresses |
Channel IDs
Unique codes for the Share911 Communication Channels that the user should have access to.
Every channel in Share911 has its own unique code which you can see in the URL for that channel or in Manage Channel > Channel Info. If you would like to use your organization's own location IDs you can do that as well, just first add the appropriate Work Place or Location ID to the corresponding Share911 channel in Manage Channel > Registration.
channel ids channel id channelid channel-id channel_id channelids channel-ids channel_ids channel code channelcode channel-code channel_code channel codes channelcodes channel-codes channel_codes location locations location id locationid location-id location_id location ids locationids location-ids location_ids |
Optional Columns
Employee ID
Unique employee identification number.
employee id employeeid employee-id employee_id employee id number employeeidnumber employee-id-number employee_id_number employee number employeenumber employee-number employee_number |
First Name
Given name.
first name first fname f-name firstname first-name first_name given name givenname given-name given_name |
Last Name
Surname/family name.
last name surname last lname l-name lastname last-name last_name family name familyname family-name family_name |
Mobile
Mobile phone number. Used when sending text messages.
mobile phone phone number phonenumber phone_number phone-number mobile number mobilenumber mobile-number mobile_number mobile phone mobilephone mobile-phone mobile_phone mobile phone number mobilephonenumber mobile-phone-number mobile_phone_number |
Title
Job title.
title job title jobtitle job-title job_title |
Shifts
Assigned work shifts.
shifts shift workshift work_shift work-shift work shift work shifts |
Manager IDs
Manager's employee identification numbers.
manager ids manager id managerid manager-id manager_id manager-ids manager_ids manager employee number manageremployeenumber manager_employee_number manager-employee-number manager employee numbers manageremployeenumbers manager_employee_numbers manager-employee-numbers manager employee id manageremployeeid manager-employee-id manager_employee_id manager employee ids manageremployeeids manager-employee-ids manager_employee_ids |
Emergency Contact Name
Emergency contact's name.
emergency contact name emergencycontactname emergency-contact-name emergency_contact_name emergency contact emergencycontact emergency-contact emergency_contact contactname contact name contact-name contact_name |
Emergency Contact Phone
Emergency contact's phone number.
emergency contact phone emergencycontactphone emergency-contact-phone emergency_contact_phone contactphone contact phone contact-phone contact_phone |
Emergency Contact Email
Emergency contact's email address.
emergency contact email emergencycontactemail emergency-contact-email emergency_contact_email contactemail contact email contact-email contact_email |
Permissions
Granted channel permissions.
permissions |
An optional Permissions column can be included if you wish to set users' permissions during the upload. The Permissions column can have one of the following values per row:
Empty / Blank
Leaving the Permissions column empty, or not including the column at all, will leave the user with their current permissions unchanged. Newly created users will receive the default permissions for each channel.
For instructions on how to set default permissions, please watch the "How to Set Default Permissions" video.
List of Permissions
Permissions that should be applied to every channel the user has access to.
For a description of the permissions available in Share911, please see the What are User Permissions help page.
Example
Action | Emails | Channel IDs | Permissions |
---|---|---|---|
save | sally.brown@example.com | acme/a, acme/b, acme/c | Liveview, Check-in |
In this example, Sally would end up having Liveview and Check-in permission in each of her 3 channels.
Granting Permissions on Specific Channels
For more fine-grained control, use JSON format to specify permissions for specific channels.
Example
Action | Emails | Channel IDs | Permissions |
---|---|---|---|
save | sally.brown@example.com | acme/a, acme/b, acme/c | {“acme/a”: [“Liveview”, “Check-in”, “Manage Users”], “acme/b”: [“Liveview”, “Check-in”, “Broadcast Alert”]} |
In this example, Sally would end up having different permissions for each of her channels:
- acme/a - Liveview, Check-in, and Manage Users
- acme/b - Liveview, Check-in, and Broadcast Alert
- acme/c - Channel's default permissions.
User Groups
user groups usergroups user-groups user_groups user group usergroup user-group user_group department code departmentcode department-code department_code department id departmentid department-id department_id dept code deptcode dept-code dept_code dept id deptid dept-id dept_id |
An optional User Groups column can be included if you wish to set users' groups during the upload. The User Groups column can have one of the following values per row:
Empty / Blank
Leaving the User Groups column empty, or not including the column at all, will leave the user with their current User Groups unchanged.
DELETE
A value of "DELETE" in the User Groups column will remove the user from all user groups across all of their channels.
Example
Action | Emails | Channel IDs | User Groups |
---|---|---|---|
save | sally.brown@example.com | acme/a, acme/b, acme/c | DELETE |
In this example, Sally would no longer be in any User Groups.
List of User Groups
The set of User Groups that the user should be a member of across all channels that the user has access to.
Example
Action | Emails | Channel IDs | User Groups |
---|---|---|---|
save | sally.brown@example.com | acme/a, acme/b, acme/c | SECURITY, MEDICAL |
In this example, Sally would end up being a member of the SECURITY and MEDICAL user groups in each of her 3 channels.
Setting User Groups on Specific Channels
For more fine-grained control, use JSON format to specify User Groups for specific channels.
Example
Action | Emails | Channel IDs | User Groups |
---|---|---|---|
save | sally.brown@example.com | acme/a, acme/b, acme/c | {"acme/a": ["ADMINISTRATION", "FACILITIES"], "acme/b": ["MEDICAL"], "acme/c": ["SECURITY"]} |
In this example, Sally would end up having different user groups for each of her channels:
- acme/a - ADMINISTRATION and FACILITIES
- acme/b - MEDICAL
- acme/c - SECURITY
Manually Managed Channels
DEPRECATED - This column is no longer used.