The from: and from:me Filters
Finding documents by person
You'll be able to
- Use from: to find documents associated with a person
- Use from:me to re-find your own work
Read first
Day 7 Lab
- Think of a doc you remember by its author, not its title.
- Search with
from:<that person>. - Now find one of your own docs with
from:me. - Note how "who" can be a faster handle than "what".
Working Example: from: in Action
The from: filter finds documents associated with a person across tools; from:me scopes to your own. Verified against search_filters.
design review → everyone's design-review docs
from:maya design review → the ones Maya authored or shared
from:me design review → your own design-review docs
"Who" is often a sharper handle than "what" — people are entities in the graph.Week 1 Capstone
You can now frame intent, choose a query mode, read results, and cut a result set by type, app, and person. That everyday fluency is the foundation every later week builds on — and it is what sits behind outcomes like Confluent's (70%+ adoption, 15,000+ hours saved monthly).
Check for understanding
What's the difference between from:me and my:history for re-finding a doc?
Check yourself
1. What does Glean's Enterprise Graph primarily connect?
2. When is a natural-language question better than keywords?
3. Your top result is the wrong TYPE of thing entirely. That is a...
4. What does a result's snippet tell you?
5. What does `type:document onboarding` do?
6. `app:slack quarterly roadmap` returns...
7. In one sentence, what does `from:me` do?
In 10 seconds
“Remember the person, not the title? Use from:. from:maya surfaces what Maya authored or shared; from:me re-finds your own work. People are an index into the graph too.”
The updated: Time Filter