diff --git a/rsts/deployment/deployment/sandbox.rst b/rsts/deployment/deployment/sandbox.rst
index 5c40eea5eb..46809ae4a3 100644
--- a/rsts/deployment/deployment/sandbox.rst
+++ b/rsts/deployment/deployment/sandbox.rst
@@ -78,5 +78,35 @@ who wish to dig deeper into the storage layer.
       🐋 Flyte sandbox ships with a Docker registry. Tag and push custom workflow images to localhost:30000
       📂 The Minio API is hosted on localhost:30002. Use http://localhost:30080/minio/login for Minio console
 
+Configuration
+______________
+
+The ``config-sandbox.yaml`` file contains configuration for **FlyteAdmin**,
+which is the Flyte cluster backend component that processes all client requests
+such as workflow executions. The default values are enough to let you connect and use Flyte:
+
+
+.. code-block:: yaml
+   
+   admin:
+     # For GRPC endpoints you might want to use dns:///flyte.myexample.com
+     endpoint: localhost:30080
+     authType: Pkce
+     insecure: true
+     console:
+       endpoint: http://localhost:30080
+   logger:
+     show-source: true
+   level: 0
+
+.. note:: 
+   
+   You can also create your own config file with `flytectl config init`, which
+   will create a config file at `~/.flyte/config.yaml`.
+
+   Learn more about the configuration settings in the
+   {ref}`Deployment Guide <flyte:flyteadmin-config-specification>`
+
+
 Now that you have the sandbox cluster running, you can now go to the :ref:`User Guide <cookbook:userguide>` or
 :ref:`Tutorials <cookbook:tutorials>` to run tasks and workflows written in ``flytekit``, the Python SDK for Flyte.
\ No newline at end of file