Access, privacy, and support
Protect sensitive records and give support useful context.
Give people access to the sites and records they need for their work. Review roles and assignments when someone changes crews or leaves the organization.
Sensitive records
Timecards, location evidence, certifications, documents, and incident information can contain personal details. Review the intended recipient before exporting or sharing a record.
Incident medical information has separate access from the narrative and investigation. Use the dedicated medical-details workflow instead of placing that information in general notes or messages. Opening protected incident detail is recorded in its history.
Use audit history to understand changes. It records supported actions; it does not make every action reversible or replace your organization's record-review process.
Account and device settings
Do not share accounts, passwords, or one-time codes. An Owner can manage roles and worker access. Mobile users can review permissions and the optional analytics setting in device setup.
For Site Secure's published terms and data practices, see Privacy and Terms.
Contacting support
Include the support reference if one appears, such as SS-XXXX-XXXX-XXXX. Also provide the page, approximate time, organization, role, site, expected result, and what actually happened.
Leave passwords, one-time codes, payment details, private keys, and tokens out of the request. Share sensitive record contents only through the support process arranged for that purpose.