How to Create a ‘My Documents’ View in SharePoint
A ‘My Documents’ view filters the library to just the current user’s content. One filter, infinite personalisation.
What it is
A ‘My Documents’ view uses the [Me] token in a filter — typically ‘where Created By is equal to [Me]’ or ‘where Owner is equal to [Me]’ — to show only files relevant to the current user. The clever thing is that [Me] resolves dynamically. The same view shows different content for every user; everyone sees their own files automatically.
This single technique transforms how users experience a library. Instead of a library being a shared space full of everyone’s content, it becomes a personalised workspace. Users land on the page and see immediately what’s theirs, what needs attention, what’s overdue. No clicking, no filtering manually, no searching.
You can build many [Me] views: ‘My drafts’ (where Owner = Me and Status = Draft), ‘My approvals waiting’ (where Approver = Me and Status = Pending), ‘My documents due soon’ (where Owner = Me and Due Date is within the next 30 days). Each one becomes a personal task list inside the library, no extra tools required.
When to use this
- On any library where individual users have specific responsibilities for their own files.
- When the library is shared but users want personalised entry points.
- For project management, document management, content authoring, approval queues.
- Whenever a Person column captures ownership or assignment.
How to do it
- Edit the view or create a new one.
- In the Filter section, set Created By (or Owner, or Assigned To) is equal to [Me].
- Save the view as ‘My Documents’ (or ‘My Tasks’, ‘My Drafts’).
- Make it Public so all users get the same experience.
- Optionally combine with status: ‘My drafts’, ‘My approved’, ‘My overdue’.
- Build similar views for other Person columns (Approver, Reviewer, Project Lead).
Best practices
- Use [Me] in views, never typed names. [Me] adapts; typed names don’t.
- Build multiple [Me] views. Different filters serve different needs.
- Make [Me] views Public. Every user sees their own content automatically.
- Combine with sort by Modified. Most recent at the top — natural to scan.
Common mistakes
- Using typed names instead of [Me]. Hard-codes the view to one person; not reusable.
- Not promoting [Me] views to Public. Each user has to recreate the same view themselves.
- No corresponding Person column. [Me] only works against Person columns. Adding it on a text field doesn’t work.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
How do I create a ‘My Documents’ view in SharePoint?
Create a new view, add a filter on a Person column (e.g. Owner or Assigned To) where the value equals [Me] (with the square brackets). Save the view as a public view. Each user who opens this view now sees only items where they are the named person — automatic personalisation, no per-user setup.
What does [Me] mean in a SharePoint filter?
[Me] is a dynamic placeholder that resolves to the currently logged-in user. SharePoint evaluates it per session, so the same view shows different content to different users. It only works on Person and Created By / Modified By columns. Use it for ‘My Files’, ‘My Tasks’, ‘My Reviews’ — anywhere personalisation matters.
Why doesn’t my [Me] filter work in SharePoint?
Three common causes: the column you’re filtering on isn’t a Person column (it’s stored as text); the square brackets are missing — it must be exactly [Me] not Me; or the view is filtered by ‘is equal to’ the literal text ‘Me’ instead of the keyword. Make sure all three are right and the filter should resolve correctly.
Can I combine ‘My Documents’ with other filters in SharePoint?
Yes — that’s where it gets useful. ‘My documents that are in Draft status’, ‘My documents due this week’, ‘My documents missing metadata’. Combine the [Me] filter with other column filters and you get personalised, task-focused views that serve each user differently while staying in a single shared view definition.