# Policy Types

Approve Delete
:   Sets an approval requirement for deleting Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow. On delete request, Instances will be shut down and only deleted if approved.

Approve Provision
:   Sets an approval requirement for provisioning Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.

Approve Reconfigure
:   Sets an approval requirement for reconfiguring Instances and servers within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.

Approve Workflow Execute
:   If enabled, when Workflows are executed on workloads within the Policy scope, an Approval is generated. This could apply when a Workflow is executed from the Workflows list page or from the detail page for an Instance or server. Approvals can be targeted to HPE Morpheus Enterprise internal Approvals or targeted to a third-party integration (such as ServiceNow). The Workflow will not begin to execute until after the approval is granted.

Backup Creation
:   Disable or enable the ability to create a backup when provisioning an instance.

Backup Targets
:   A master account can determine storage provider options for backups with Backup Targets policies.

Budget
:   Sets a maximum total combined price for all instances in the Group, Cloud, Tenant or owned by the User this policy is applied to.

Cluster Resource Name
:   The name of Cluster hosts (master and workers) when creating Kubernetes, Docker and KVM Clusters. Pre-populates a fixed or editable Resource Name value for the cluster using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings

Cypher Access
:   Granularly set LIST, READ, WRITE, and DELETE access to arbitrary Cypher secret paths scoped globally or to specific Roles and Users. See the section below for a guide to establishing a Cypher access policy.

Delayed Delete
:   Delayed Delete Policies allow for soft deletion of Instances and Apps. Instead of deleting immediately, Instances and Apps with a Delayed Delete policy applied will be shutdown upon deletion request and hidden by default from the UI. The Instance/App will then be in `Pending Removal` status. In order to see Instances pending deletion on the Instances list page (Provisioning > Instances), you must filter for “Pending Removal” status. These Instances will not show when filtered for “All Statuses”

Expiration
:   Sets an expiration timeframe in days after which the Instance will be deleted. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration. See HPE Morpheus Enterprise [Knowledge Base](https://support.morpheusdata.com/s/article/How-to-create-an-extensions) for more information about Expiration policies

File Share Storage Quota
:   Sets a Storage Quota for File Share usage (in GB) to scoped User, Role, Tenant or Global.

Hostname
:   The `hostname` or `computer name` which is set in the OS and DNS. On some platforms, hostnames are restricted by length, spaces, and/or special characters. Pre-populates a fixed or editable name for hostnames/machine names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings

Instance Name
:   Pre-populates a fixed or editable name for Instance Names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings. Note that it’s not recommended administrators include “>”, “<”, “%”, “$”, or “=” in naming policies

Instance Networks
:   When an Instance is provisioned within the scope of the Policy (Group or Cloud scoping is supported), the network selected on the Policy is automatically set and locked in the provisioning wizard to force provisioning onto the selected network.

Max Containers
:   Sets the max number of Containers for the Group or Cloud the Policy is added to.

Max Cores
:   Sets the max number of total of Cores combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.

Max Hosts
:   Sets the max number of total Hosts in the Group or Cloud the Policy is added to.

Max Load Balancer Pools
:   Sets the max number of load balancer pools within the policy scope

Max Memory
:   Sets the max number of total of RAM combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.

Max Pool Members
:   Sets the maximum number of members in a load balancer pool

Max Snapshots
:   Set the maximum number of Snapshots that may be stored for each Instance or VM within the scope. Once the limit is met, HPE Morpheus Enterprise will warn the user when attempting to create more snapshots until the number is reduced

Max Storage
:   Sets the max number of total of Storage combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.

Max Virtual Servers
:   Sets the maximum number of virtual servers within the policy scope

Max VMs
:   Sets the max number of Virtual Machines for the Group or Cloud the Policy is added to.

Message of the Day (MOTD)
:   Message of the Day”” Policy for displaying Alerts in HPE Morpheus Enterprise. Configurable as a pop-up or full-page notification with Info, Warning and Critical message types.

    NOTE

    Requires role permission: `Admin: Message Of the Day` set to “Full” to create and manage MOTD Policies.

Network Quota
:   Limits the number of networks that can be created within the policy’s scope

Object Storage Quota
:   Sets a Storage Quota for Object Storage usage (in GB) to scoped User, Role, Tenant or Global.

Power Scheduling
:   Adds a Power Schedule for the Instances in a Group or Cloud. Power Schedules can be created in Library > Automation > Power Scheduling

Router Quota
:   Limits the number of routers that can be created within the policy’s scope

Shutdown
:   Sets a shutdown timeframe in days upon provision after which the Instance will be stopped. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration.

Storage Server Storage Quota
:   Sets a Storage Quota for selected Storage Server (in GB), applied Globally or per specified Tenants.

Tags
:   Requires the user to add compliant Tags at provision time, this can be enforced on a strict or passive basis

    NOTE

    Tag scanning and enforcement is currently only available for Azure, Amazon, Google, and VMware clouds. For a more comprehensive guide on implementing Tag Policies, see the associated article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-work-with-cloud-tagging-policies?language=en_US).

User Creation
:   Controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.

User Group Creation
:   Forces User Creation of members in the selected User Group during Provisioning.

Workflow
:   Workloads provisioned within the scope of the Policy will have the indicated Workflow applied and the Tasks executed within the proper phase of the Instance lifecycle
