---
title: Computer-based Services
slug: computer-based-services
docTags: 
createdAt: 2026-01-29T01:03:55.784Z
---

Computer-based services are services that are ordered for a user but require an associated computer in order to be provisioned. The service represents access or capability requested by a user, while the selected computer defines where the service is deployed.

The associated computer is used as the deployment target for computer-based group membership, SCCM deployments, or other device-based provisioning mechanisms supported by Activate.

# Overview of computer-based services

Computer-based services differ from user-based services in that provisioning actions are performed against a computer object rather than directly against a user account, even though the service itself is still requested on behalf of a user.

A computer must be identified before provisioning can occur, ensuring that deployments are applied to the correct device.

# Computer selection requirement

A computer-based service is always associated with both:

- A user, who is requesting the service
- A computer, which is the target for deployment

A computer must be identified before provisioning can occur.

Depending on configuration and request method, computer selection may occur:

- During the initial service order
- After approval but before provisioning
- Automatically through entitlement-based deployment

Provisioning is deferred until a valid computer association is established.

# Decide later behaviour

The **Decide later** option controls when the computer must be selected.

When Decide later is enabled:

- The service can be ordered and approved without selecting a computer
- Provisioning is deferred
- The service remains pending until a computer is selected

When Decide later is disabled:

- A computer must be selected as part of the manual order process
- The service cannot proceed without an associated computer

The availability of the Decide later option is controlled by service configuration.

# Ordering paths and behaviour

Computer-based services may be requested through multiple paths:

- Manual ordering via Order Service
- Suggest Access
- Automatic deployment via entitlements

When services are added via Suggest Access or deployed automatically through entitlements, computer capture follows the same process as Decide later. Provisioning is deferred until a computer is identified.

# Provisioning mechanisms

Computer-based services can perform provisioning actions against both the user and the computer.

This allows a single service to:

- Grant the user access to an application or resource
- Deploy required software or configuration to the selected computer

Provisioning behaviour is controlled by service configuration.

## User-based provisioning

User-based provisioning actions are applied to the user who requested the service.

Common examples include:

- Adding the user to a security or application access group
- Granting entitlements required to access the application

These actions ensure the user has the appropriate permissions once the application is available.

## Computer-based provisioning

Computer-based provisioning actions are applied to the selected computer.

Common examples include:

- Adding the computer to a computer-based group
- Triggering SCCM or other device deployment mechanisms
- Applying device-specific configuration or automation

These actions ensure the application or service is deployed to the correct device.

# Service definition parameters

Computer-based service behaviour is controlled by parameters defined on the service definition.

Common parameters include:

- UserGroup – controls group membership or entitlements applied to the user
- ComputerGroup – controls group membership or deployment actions applied to the computer

By combining user and computer provisioning within a single service, Activate ensures that access and deployment remain aligned.

# Key considerations

When designing and configuring computer-based services:

- Ensure users understand when computer selection is required
- Validate behaviour across all ordering paths
- Confirm downstream systems can correctly process the selected computer

Consistent configuration helps provide predictable provisioning outcomes across manual and automated requests.