> For the complete documentation index, see [llms.txt](https://2600hz.gitbook.io/sds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2600hz.gitbook.io/sds/sds-3.0/sds-components/components/table.md).

# Table

### Use Cases for Table Component: 

✅ Displaying Structured Data: Tables are excellent for presenting structured data in a clear and organized manner, such as lists of items, financial data, or schedules. 

✅ Sorting and Filtering: Allow users to easily sort and filter data within the table, enhancing usability and enabling quick access to relevant information. 

✅ Editing Data: Enable users to edit data directly within the table, providing a convenient interface for making changes without needing to navigate to a separate form. 

✅ Responsive Design: Ensure the table component is responsive to different screen sizes, allowing for optimal viewing and interaction across devices.

### Not-to-Use Cases for Table Component: 

❌ Complex Data Manipulation: Avoid using tables for complex data manipulation tasks that require advanced interactions beyond sorting, filtering, and basic editing. In such cases, consider using dedicated data visualization tools or custom interfaces. 

❌ Excessive Data Display: Refrain from displaying large amounts of data within a single table, as it can overwhelm users and degrade performance. Instead, implement pagination or lazy loading to manage large datasets effectively.

 ❌ Non-Tabular Data Presentation: Tables are not suitable for presenting non-tabular data, such as multimedia content or hierarchical data structures. Use appropriate UI components tailored to the specific data format for better clarity and usability.