What is a one sentence summary of your feature request?
Allow administrators to change the time zone of an existing organization in 1Secure after it has been created.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, once an organization is created in 1Secure, its time zone setting is locked and cannot be modified. This creates challenges if the wrong time zone was selected during setup or if organizational requirements change. Allowing the time zone to be adjusted from the organization’s configuration page would enable administrators to easily correct mistakes and adapt to evolving needs without disrupting operations. This feature would improve user experience, reduce administrative burden, and ensure that reporting reflects the correct time zone.
How do you currently solve the challenges you have by not having this feature?
At present, if an incorrect time zone is set, we have to delete and re-create the organization with the correct time zone, which involves re-adding sources and waiting up to 24 hours for data collection to complete. If correct time zone is required for reporting, then all the data that was collected for the previous organization will also be gone. This process is time-consuming, can cause data gaps, and introduces unnecessary operational overhead.