You can define time intervals for use in policies. For example, if you want to block users from accessing shopping sites from 8 AM to 5 PM on weekdays, you can create a time interval called Weekdays that includes Monday through Friday from 8 AM to 5 PM.
When an organization creates time bound policies, policy behavior might differ between users. If the user is coming from a known location, the policy will be applied based on the time zone configured for their location. If the user is a remote user (including users using the Z-App), the policy will be applied according to the time at the Zscaler Enforcement Node (ZEN) they are connected to.
Consider the following example, an organization has a URL filtering policy using a time interval. This policy set to block the Social Networking URL category Monday through Friday from 9 a.m. - 5 p.m.
A user tries to access facebook.com through a ZEN in the Paris data center. They come from a known location with the time zone configured as Europe/London on Tuesday at 5:30 p.m. London time. See image. This user is blocked from going to the site even though the time in Paris at that point in time is 6:30 p.m. The reason for this behavior is because the ZEN uses the time zone of the configured location for policy execution.
Consider another user, who is also in London and generates traffic through the Paris data center. This user is not from a known location, they are a remote user. They also try to go to Facebook at the same time.
This remote user is allowed to access Facebook. The reason for this behavior is that, though the user is located in London and the time in London is 5:30 p.m., there is no location configured for remote users. Therefore, the ZEN’s time zone is used for policy execution. Because the ZEN used is in Paris and the time there is 6:30 p.m., the policy would not be triggered.
On the Time Intervals page, you can do the following: