diff --git a/docs/access/guide-to-requesting-databricks-access.md b/docs/access/guide-to-requesting-databricks-access.md
new file mode 100644
index 0000000..7210c79
--- /dev/null
+++ b/docs/access/guide-to-requesting-databricks-access.md
@@ -0,0 +1,54 @@
+# Guide to Requesting Databricks Access
+
+Created by Eric Yu (originally shared via Slack)
+
+## Overview
+
+This guide explains the current process for requesting access to Databricks, including who to contact and important context about recent team changes.
+
+## Prerequisites
+
+- You must require Databricks access for your role or project.
+- You should be able to contact members of Tower’s data team via the company’s standard communication channels (e.g., Slack, email).
+
+## How to Request Databricks Access
+
+1. **Identify the correct point of contact**
+   - The primary contact for Databricks access is **Kaushik**, who is on **Tower’s data team**.
+   - Do **not** contact **Ron Bailey** for Databricks access. He is no longer with the company.
+
+2. **Reach out to Kaushik**
+   - Send a message to Kaushik (via Slack or email, per your team’s norms) requesting Databricks access.
+   - Include:
+     - Your name and role
+     - The project or team that requires Databricks
+     - Any deadlines or time sensitivity, if applicable
+
+3. **Follow any additional instructions from Tower’s data team**
+   - Kaushik or another member of Tower’s data team may provide:
+     - Additional forms or approvals required
+     - Environment or workspace details
+     - Onboarding or security steps specific to Databricks
+
+## Important Notes
+
+- **Contact change:** The previous point of contact, **Ron Bailey**, was laid off and should no longer be contacted for Databricks-related requests.
+- **Tower’s data team ownership:** Access to Databricks is now clearly owned and managed through **Tower’s data team**, with Kaushik as the key contact.
+
+## Troubleshooting
+
+- **No response from Kaushik**
+  - If you do not receive a response within a reasonable timeframe (e.g., 2–3 business days), escalate by:
+    - Contacting another member of **Tower’s data team**, or
+    - Asking your manager to help route the request.
+
+- **Unclear requirements**
+  - If you are unsure what information to provide, start with:
+    - Your use case for Databricks
+    - Any data sources you expect to use
+    - Whether you need read-only or write access  
+  - Kaushik or Tower’s data team can then clarify any additional requirements.
+
+---
+*Originally shared by: Eric Yu*
+*Source: [Original Slack thread](https://distylai.slack.com/archives/C0A2YGPRRA8/p1765505104943429)*