The roles and role hierarchy feature will not be applicable for the integration forms. This implies that anyone who has access to the integration form's report will have access to all the data irrespective of their role.
This behavior is consistent across Zoho Creator and manifests during form submissions, execution of insert record tasks, and when handling data through API, including Date-Time values manipulated in scripts. The following table below shows the start and end dates of daylight saving period in the Pacific Time zone for each year.
Year | DST Start Date | DST End Date |
2024 | March 10 | November 3 |
2025 | March 9 | November 2 |
2026 | March 8 | November 1 |
2027 | March 14 | November 7 |
2028 | March 12 | November 5 |
2029 | March 11 | November 4 |
2030 | March 10 | November 3 |
Notably, the system faces constraints in capturing Date-Time values falling between 2 am - 3 am on the start date of the Daylight Saving period in the Pacific Time zone. This restriction persists regardless of the application and account time zone settings.
For instance, attempting to input Date-Time values like "13-Mar-2011 2:30:00", "11-Mar-2012 2:33:00", "10-Mar-2013 2:40:00", etc., is not feasible due to their occurrence within the changeover period. Moreover, any Date-Time value equivalent to Pacific Time falling between 1 am - 2 am PDT on the end date of the Daylight Saving period will be automatically adjusted by 1 hour. As an illustration, the Date-Time "04-Nov-2012 08:30:00 Etc/UTC" will shift to "04-Nov-2012 09:30:00 Etc/UTC" since the equivalent PDT value at that time is "04-Nov-2012 01:30:00 PDT."