diff --git a/packages/clay-core/docs/table.mdx b/packages/clay-core/docs/table.mdx
index b22b676d8a..18fc5354c9 100644
--- a/packages/clay-core/docs/table.mdx
+++ b/packages/clay-core/docs/table.mdx
@@ -15,6 +15,7 @@ storybookPath: 'design-system-components-table--dynamic'
 -   [Content](#content)
     -   [Static](#static)
     -   [Dynamic](#dynamic)
+-   [Icons](#icons)
 -   [Sorting](#sorting)
     -   [Asynchronous](#asynchronous)
 -   [Nested row](#nested-row)
@@ -107,6 +108,55 @@ Unlike static content, dynamic content is when the options can change during the
 </Table>
 ```
 
+## Icons
+
+<div class="clay-site-alert alert alert-warning">
+	<strong class="lead">Warning</strong>
+	When implementing ClayTable from a React application, the icons may not render.
+	The <a href="https://clayui.com/docs/components/provider.html#application-provider">
+		Application Provider
+	</a> method will make the icons available for use.
+</div>
+
+```jsx
+import {Provider} from '@clayui/core';
+
+const spritemap = 'icons.svg';
+
+<Provider spritemap={spritemap}>
+	<Table>
+		<Head
+			items={[
+				{
+					id: '1',
+					name: 'Name',
+				},
+				{
+					id: '2',
+					name: 'Type',
+				},
+			]}
+		>
+			{(column) => <Cell key={column.id}>{column.name}</Cell>}
+		</Head>
+
+		<Body
+			defaultItems={[
+				{id: 1, name: 'Games', type: 'File folder'},
+				{id: 2, name: 'Program Files', type: 'File folder'},
+			]}
+		>
+			{(row) => (
+				<Row>
+					<Cell>{row.name}</Cell>
+					<Cell>{row.type}</Cell>
+				</Row>
+			)}
+		</Body>
+	</Table>
+</Provider>;
+```
+
 ## Sorting
 
 Column sorting is implemented OOTB so the developer doesn't need to worry about implementing the UI details but the developer still needs to add their filter layer since the component is data-agnostic and allows you to do this asynchronously, it is important, especially when your data is paged, that the filter must happen in the backend.
