---
title: Service Flags
slug: service-flags
createdAt: 2025-06-11T20:26:21.329Z
---



This section outlines the available Service Flags in Activate and how they influence ordering, provisioning and lifecycle behaviour.

## OrderOnly

The service is treated as order-only and is not stored as a persistent service instance. It does not appear in user or computer services.

This flag is suitable when lifecycle management (create, update, delete) is not required.

**Examples:** Print toner, consumables.

## AllowDuplicates

By default, users can hold only one instance of a service. For computer-based services, they can hold one instance per computer.

This flag allows users to have multiple instances as required.

## SupportsResetPassword

Indicates the service supports password reset and can appear in the **Reset Service Password** task.

Services must implement a ResetPassword function in the service script.

**Example:** SAP accounts using independent passwords.

## SupportsUpdate

Indicates the service supports the **Update Service** task.

**Example:** SAP roles that vary by user function.

## SupportsUpdateUser

Enables automatic updates to the service when user details change.

Services must implement an UpdateUser function.

**Example:** SAP storing first/last names in its own database.

## DisableExpiry

Prevents the service from being ordered for a defined period.

Disables the **How long does the user need this service?** control.

**Example:** Order-only services where lifecycle management is not required.

## DisableEffective

Prevents deferred start dates for orders.

Disables the **When does the user need this service?** control.

**Example:** Internet Access Policy, where changes must apply immediately.

## DisableDecideLater

Forces selection of a computer when one is required.

Disables the **Decide Later** option.

**Example:** Services requiring a device to be provisioned.

## DisableQuickAdd (8.1.4+)

Prevents the service from being added through **Quick Add**. Other Quick Add rules still apply (e.g., use of Web.Forms, expiry options, computer requirements).

**Example:** Services with important additional details users must review before ordering.

## AutoExpire

Automatically expires the service instead of initiating renewal.

If expiry is set, the background renewal script will delete the service instance immediately.

**Example:** Time-limited services that must be re-ordered each time.

## ValidLicenseOnly

Requires a valid licence to be available before the service can be provisioned.

Prevents service instance creation until a suitable licence asset is allocated.

**Example:** AutoCAD or other high-cost licensed software.

## ViewOnly

Makes the service visible but not orderable via the web portal.

**Example:** Informational items where ordering occurs outside Activate.

## Hidden

Hides the service from the web portal.

**Example:** Automatically deployed items such as printer drivers.

## Grouped

Indicates that the service is part of a grouped collection of related sub-services.

**Example:** Financial systems with multiple requestable components.

## Category

The service is displayed as a category with a specialised form and a list of sub-items.

Useful when providing additional context or multiple related choices.

**Example:** Remote Access options.

## Bundle

Defines the service as a bundle of multiple services.

Allows users to order a predefined set of services quickly.

**Example:** A new‑starter bundle containing all required initial services.