GITBOOK-35: No subject

SUMMARY.md

@@ -12,7 +12,7 @@
 * [Automatic Instrumentation in the IDE](instrumentation/automatic-instrumentation-in-the-ide/README.md)
   * [Spring, Spring Boot, Dropwizard and default](instrumentation/automatic-instrumentation-in-the-ide/spring-spring-boot-dropwizard-and-default.md)
   * [Quarkus, Micronaut](instrumentation/automatic-instrumentation-in-the-ide/quarkus-micronaut.md)
-* [Instrumenting your code in CI/Staging or the terminal](instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md)
+* [Instrumenting your code in CI/Staging or the terminal](instrumentation/instrumenting-your-code-from-terminal.md)
 
 ## Digma Core Concepts
 

digma-core-concepts/environments.md

@@ -13,7 +13,23 @@ Digma excels in analyzing observability data, detecting changes, and measuring b
 
 To bring some order into this chaos, Digma uses environments as an abstraction to measure data from different deployment stages and use cases separately.
 
+### The default environment
+
+By default, all observability data received by the Digma Analytics Engine is lumped in the `LOCAL`or `LOCAL_TESTS` environments if you've installed Digma locally on your machine. The latter environment will automatically ingest any observability from your local test runs in the IDE.
+
+Once you've installed Digma centrally all untagged traces will immediately be lumped under the `UNSET` environment. However, this should be a temporary state and we strongly recommend to create named environments for each of your observability sources.
+
+### Private vs. Shared Environments
+
+Private environments are environments only you have access to. If you're running Digma locally this is also the only environment you can create - seeing as you're also the only user!
+
+Once you've installed Digma centrally you can create shared environments that are accessible to multiple users. A good example would be setting up a Digma environment for your CI or Staging.
+
 ### How to create environments
 
-Private environments are easy to create in your local deployment.
+Beyond the default environments, creating additional private or shared environments requires registering for a Digma Account (which is free and available at this [link](https://digma.ai/sign-up)). 
+
+Private environments are easy to create in your local deployment from the Observability Panel and through the `Add Environment` button. 
+
+<figure><img src="../.gitbook/assets/image (13).png" alt=""><figcaption></figcaption></figure>