# Choose a Deployment Method

> Choose between a reviewed one-client Admin Push and a saved-version Workspace Deployment.

Glow provides two ways to copy a workflow into client workspaces. Choose based on the source you want to deploy, the number of clients and when you want to review the copy.

  
    
      
    
    Admin Push
    
      Review one client copy before creating it.
    
    
      Source: current active workflow
    
  
  
    
      
    
    Workspace Deployment
    
      Roll out a selected saved version to one or more clients.
    
    
      Source: saved workflow version
    
  

## Compare the two paths

| Decision          | Admin Push                                          | Workspace Deployment                                           |
| ----------------- | --------------------------------------------------- | -------------------------------------------------------------- |
| **Source**        | The workflow's current active version               | A saved version you select                                     |
| **Destination**   | One client workspace                                | One or more selected client workspaces                         |
| **Review timing** | A detailed preflight appears before the copy starts | You choose the approved version and destinations in Deployment |
| **Best fit**      | A reviewed, one-client handoff                      | A controlled rollout from a known version                      |
| **Result**        | A new inactive client copy                          | A new independent Draft copy in each selected workspace        |

Neither path updates an existing client workflow. Treat every delivered copy as independent, and finish its client-owned connections, variables and test data before making it Live.

## Use Admin Push

Choose Admin Push when you want to inspect one target in detail before the copy is created. The preflight reports the client resources that need attention, including connections and workspace values.

👉 **[Follow Pushing Workflows to Clients →](/msp/cross-workspace-pushing)**

## Use Workspace Deployment

Choose Workspace Deployment when you have saved the exact version you approved and want to select the client destinations for that version. The Deployment page is also where a workflow can be prepared for other reuse routes.

👉 **[Follow the Deployment Page →](/getting-started/templates/deployment)**

## Before either deployment

- Confirm that your grant permits writing to the client workspace.
- Save and test the source you intend to deliver.
- Keep client-specific values in workspace variables or secrets rather than embedding them in Step fields.
- Plan to connect client-owned accounts and collect fresh test data in the receiving workspace.

For an end-to-end handoff, follow [Your First Client Workflow](/msp/first-client-workflow).

## What's Next?

- 👉 **[Deploy and Test Your First Client Workflow →](/msp/first-client-workflow)**
- Review what may cross workspace boundaries in [How Multi-Tenancy Works](/msp/how-multi-tenancy-works).
- Monitor delivered workflows from [Your Console](/msp/dashboard-analytics).