diff --git a/docs/deploy-viya.md b/docs/deploy-viya.md
index b792ee7..b3293da 100644
--- a/docs/deploy-viya.md
+++ b/docs/deploy-viya.md
@@ -80,7 +80,7 @@ To avoid giving users the ability to run code on that context (and shared system
 
 Services are deployed by running a SAS program.
 
-**Streaming Deploy:**
+**Streaming Deploy (BACKEND + FRONTEND):**
 
 Run the following in SAS Studio:
 
@@ -90,7 +90,7 @@ filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/vi
 %inc dc;
 ```
 
-**Separated Deploy:**
+**Separated Deploy (BACKEND ONLY):**
 
 Run the following in SAS Studio:
 
@@ -119,6 +119,7 @@ The following attributes may be updated in the index.html file.  For streaming d
 - `servertype` - should be SASVIYA
 - `debug` - can stay as `false` for performance, but could be switched to `true` for debugging startup issues
 - `useComputeApi` - Setting `true` will give the best performance due to the use of [hot sessions](https://github.com/sasjs/adapter#using-the-compute-api) created client-side by the SASjs adapter.  This is great for demo purposes, or when running a single user DC instance, however for typical enterprise use we recommend `false` or `null` so that the compute context usage can be restricted as described [above](/deploy-viya/#create-shared-compute-context)
+- `runAsTask` - setting `true` will trigger jobs as Viya Compute Tasks.  Be sure to increase the default expiry to 30 seconds (it is 5 by default) and set `useComputeApi` to `null`.
 
 
 ### First Launch