Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Choose the company time zone. Use a location-based time zone so summer and winter times display correctly. Current availability: Implemented; verification required.

Before you start. An authorized administrator in the correct company or the TLS owner console, with mandatory verification completed. Use an approved synthetic account for acceptance. Keep credentials, personal data and recovery codes out of recordings.

Step 1. During Create company, search for the location’s IANA zone and confirm it with the company. Browser location is only a suggested starting point.

Step 2. Choose America/New_York for Eastern US locations, America/Chicago for Central, America/Denver for Mountain, America/Phoenix for Arizona where appropriate, or the location’s actual region. Fixed labels such as EST and CST are not accepted as company zones.

Step 3. After setup, open Portal settings and update Time zone. Save against the current settings revision to avoid overwriting another administrator’s changes.

Step 4. Review company helpdesk, passwords, knowledge, device jobs, license observations and security times. Stored event timestamps remain unchanged; the selected location controls their display.

Step 5. Test an event in summer and winter. Accounting dates and date-only fields are calendar dates; they are not shifted as if they were an event timestamp.

Now verify the result. America/New_York uses the correct daylight-saving offset. America/Phoenix and America/Denver can display different summer times.

If you get stuck. 

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.