diff --git a/docs/.vitepress/config.mts b/docs/.vitepress/config.mts
index cea7155..5826934 100644
--- a/docs/.vitepress/config.mts
+++ b/docs/.vitepress/config.mts
@@ -36,6 +36,7 @@ export default defineConfig({
           { text: 'Links and Images', link: '/links-and-images' },
           { text: 'CSV Viewer', link: '/csv-viewer' },
           { text: 'Query Configuration', link: '/query-configuration' },
+          { text: 'Define Column Types', link: '/define-column-types' },
           { text: 'Troubleshooting', link: '/troubleshooting' },
           { text: 'Future Plans', link: '/future-plans' },
           { text: 'Changelog', link: '/changelog' }
diff --git a/docs/define-column-types.md b/docs/define-column-types.md
new file mode 100644
index 0000000..6421582
--- /dev/null
+++ b/docs/define-column-types.md
@@ -0,0 +1,4 @@
+# Define Column Types
+
+SQLSeal sets types of your data automatically. This is the mechanism which for most of the cases works perfectly, but for more advanced use-cases, you might want to force specific type of the column (for example you might have ids which you want to treat like text, even if they consist of just the numbers). To enforce the specific type, you can set individual types inside the CSV Viewer:
+![Setting Column Type](./setting-column-type.png)
\ No newline at end of file
diff --git a/docs/setting-column-type.png b/docs/setting-column-type.png
new file mode 100644
index 0000000..5d67870
Binary files /dev/null and b/docs/setting-column-type.png differ