List
Common Use Cases
- Trackers: tasks, issues, risks, and requests in one place
- Inventories: assets, equipment, and contracts with their details
- Registers: logs of events, decisions, or approvals
- Lightweight apps: forms and views that act like a simple application
- Reference data: lookups that other lists draw from
- Project data: structured information a team works together
Benefits
- Structured columns: typed fields instead of free-form cells
- Filter and group: views organize items any way you need
- Validation: rules keep the data clean at entry
- Permissions: access is controlled like any SharePoint content
- Versioning: item history is tracked when enabled
- Integration: Power Automate, Power Apps, and Teams plug right in
How It Works
- Items and columns: each row is an item described by columns
- Column types: choice, date, person, number, lookup, and more
- Views: saved arrangements of filters, sorts, and grouping
- Forms: the new and edit experience for each item
- Stored in a site: a list lives inside a SharePoint site
- Microsoft Lists: the same lists surface in the Lists app
Limits and Nuances
- List view threshold: large lists need indexes to filter past 5,000 items
- Not for files: documents belong in a library, not a list
- Lookup limits: cross-list lookups have practical limits
- Capacity: lists scale large but are not a database replacement
- Column type choices: picking the right type matters for reporting
- Permissions complexity: item-level permissions add management overhead
Common Questions About the List
What is a SharePoint list?
A SharePoint list is a structured table of information made up of items (rows) and columns (typed fields) you define. It is designed to track data such as tasks, assets, requests, or issues, much like a spreadsheet but with typed columns, validation, views, permissions, and integration. Lists are the foundation under most trackers and lightweight business apps built in SharePoint.
How is a list different from a document library?
A list stores data in rows and columns, while a document library stores files with metadata attached. Both share the same column, view, and permission features, but a library centers on documents and a list centers on records. If your main content is files, use a library; if it is structured information, use a list.
What makes lists more powerful than a spreadsheet?
Lists use typed columns – choice, date, person, number, lookup – so the data is consistent and can be filtered, grouped, validated, and reported on. They also bring permissions, version history, and tight integration with Power Automate, Power Apps, and Teams. That combination turns a flat table into something closer to a small application that several people can use at once.
Are SharePoint lists and Microsoft Lists the same thing?
They are the same underlying lists, surfaced through different experiences. The Microsoft Lists app gives a friendlier home for creating and tracking lists, while the lists themselves still live in SharePoint sites and behave the same way. A list you create in either place can be opened and managed from the other.
How large can a SharePoint list get?
Lists can hold very large numbers of items, but the list view threshold means operations that touch more than 5,000 items at once need indexed columns to stay fast. With sensible indexing and views, a list can grow into the tens of thousands of items. It is still not a full database, so extremely large or highly relational data may call for another tool.
When should I build a list?
Reach for a list whenever you are tracking structured information that several people need to share. Greg Zelfond, the consultant behind LookBook 365, builds most of his trackers and team tools on lists, because the right columns and views turn a simple table into a self-service app without any code. When the content is files rather than data, a library is the better starting point.