Manage time zones

In , every organization and every user has a definable time zone parameter. However, uses organization time zones and user time zones differently:

As a result, organization members in a time zone different from the organization's time zone may see different times displayed. See the example below for more details.

Your profile page lets you view and edit time zone settings from the Time Zone Options tab.

 uses an organization's time zone to define when a scheduled executes. The organization time zone defines execution and functions such as formatDate and parseDate. Unless otherwise specified, uses the organization time zone as the default time for time and date-related functions and execution. You can view and edit your organization time zones on the Time Zone Options tab of the profile page. afsa

The selected time zone now appears on the Time Zone Options page.

Any scheduled execute at the scheduled time in the time zone you assigned in step 4.

 uses your user time zone to display time and date information. For example, execution logs display the time in your user time zone. The user time zone only impacts how Make displays information, such as the date and time displayed in module output, bundles, or a log. Changing the user time zone does not impact execution. You can view and edit your user time zone anytime on the Time Zone Options tab of the profile page.

The selected time zone now appears on the Time Zone Options page.

A organization based in New York City has members in New York City, Los Angeles, and London. When members view execution histories, they see that information relative to their local time zone. Members in London see the time executed in London time, Los Angeles members see those execution times in LA time, and so on. However, when they schedule , uses New York City time regardless of the user's location.