A policy defines the amount of time end-users will have access to an environment and what will happen to the environment once this access period has expired. The policy also defines what happens to the environment once it has been idle for a certain amount of time. Policies must be made public in order for other admin users to see and use them.
You can define as many policies as you need and apply them to Courses and Environments. For Events, end-user access to environments is defined by event schedules, see: Creating an event.
The amount of time a user has access to an environment. The duration starts from when the environment is first launched.
The amount of time after first launch that the environment is destroyed.
Users can be allowed to extend their access duration by the setting defined here. The quantity of extensions combined with the extension duration determine the additional user access.
Should Heropa detect an idle user session in the Workspace, the auto-suspend setting determines if the VMs in the environment will be automatically shutdown. As an example, an auto-suspend after 1 hour setting will shutdown the VMs exactly 1 hour after an idle session has been detected.
Note: An idle session is triggered after 15 minutes of no user activity in the browser tab.
Adding a policy
- In the Heropa Portal, from the Left Navigation menu choose Policies, then select Add from the main action menu.
- In the Create new policy window, complete the following information:
- Company: Select the company that will own the policy.
- Users with a global role type can create a policy for any company. Users with a company role type can create a policy for their own company only.
- Select 'Share with all companies' if the policy is to be available to all companies. For more information, see: Sharing resources across Companies.
- Name: Enter a name for the policy. Often a name that describes the policy settings can be helpful.
Once the above information has been completed, click Create.
Updating a policy
If a policy is updated, for example a change is made to its duration, auto-suspend or destruction rules, any associated courses or non-provisioned environments will have these changes automatically reflected in them. Note: Already launched environments using the policy will not be affected.
Overriding a policy
The longest you can specify a VM to run in a policy is 12 hours. If you require a VM to run continuously, or longer than what is specified in a policy, this can be handled on a per VM basis. Use the 'Disable auto-suspend' action against the VM. See: Managing an environment's VMs.