3 Notion Features I Actually Use: Tabs, Dashboard Views, and Custom AI Agents

Listen on Spotify // Listen on Apple podcasts

The three Notion features I actually use right now are Tabs, Dashboard views, and Custom Agents. Notion has launched 25+ features in the last year, and these are the ones that stayed in my system, because each one removed a specific kind of friction between the information I need and the decision I need to make with it. Tabs fixed what I see when I open my home base page. Dashboard views fixed how fast I can read the state of my work. Custom Agents took over the gathering I kept procrastinating on. You probably don't need all three. The useful question is whether one of them would make the setup you already have easier to use, and if you can't name the problem a feature solves, leave it alone.

Key takeaways

• Tabs let you keep the content on a page without showing all of it at once. Move the sections you already have instead of recreating them.

• Before you add a chart to a Notion dashboard, name the question it's supposed to answer.

• A Dashboard view can only show what's recorded in the database underneath it. Dashboard views are available on Business and Enterprise plans.

• Give a Custom Agent one specific gathering job, and keep the decisions with a human.

• If you can't name the repeated problem a new feature would remove, leave the feature alone.

Seven Notion pages, one starting point

I used to run my week from seven separate Notion pages. A page for Monday, a page for Tuesday, a page for Wednesday, each one set up for that day's theme: priorities, follow-ups, stats, habits. All useful. But every morning I was opening another dashboard, scrolling past things I didn't need, and finding my starting point all over again. On top of that, I live in pinned browser tabs, and clicking from one daily page to the next opened it in a new, unpinned tab. Small thing. It drove me nuts.

When Tabs launched, I moved those daily layouts into tabs on one home base page. Same information, one place to start. What surprised me was how much I got to keep. The whole fix was to stop opening a different page every damn day.

If you've never used them, picture one page with labeled tabs across the top of a section. The labels stay put, and the content underneath changes when you click a different tab. My Monday layout is a tab. My warmup (habits and daily journal) is a tab. Tuesday, my client day, shows client connections and leads. That home base page is now the first page in my favorites, and it's where every workday starts.

A Notion dashboard can be organized and still be overwhelming

Visual clutter is what happens when everything on your Notion page has a home and all of it is visible at the same time. A lot of people tell me they love their Notion system and still freeze when they open it. That's usually visual clutter, or too many clicks between them and the thing they came for.

I felt the tension myself. I have ADHD, so out of sight really is out of mind for me, and I wanted my information close. But seeing every part of my week at once gives me analysis paralysis. Scrolling is one of my red flags: if I have to scroll to find what I need, there's too much on the page. I love being able to find my information. But at 7:00 in the morning, I do not need to make eye contact with my entire business.

So ask what you need to see when you first open the page. Keep that visible, and give the rest a clear place to go when you need it.

One limit: Tabs won't decide what belongs on the page. Twenty tabs with vague names is another place to search. Start with the sections you already use. And watch yourself if you enjoy building in Notion like I do, because I can turn a small layout change into a much bigger project if I let myself. Keeping what already worked was the useful part.

Dashboard views: give every chart a job

A Dashboard view is a database view that turns one database into an at-a-glance control center, with the useful pieces arranged together in one layout. These are different from the handmade dashboard pages full of linked databases and widgets that show up when you search for Notion setups. Instead of clicking between a table, a board, and a calendar to understand the same body of work, you see it together.

Check your plan before you get attached: Dashboard views are available on Business and Enterprise plans [CHECK].

My rule: before you add another chart to a dashboard, name the question it's supposed to answer. For a content database, that might be what's scheduled this week, what's stalled at a particular stage, or what's performing. A chart earns its place when it makes one of those answers easier to see. If it's only there because it looks cool, it's one more thing to interpret every time you open the page.

I'm the cautionary tale here. I love a graph. I love numbers. I'm a former scientist, and I'm very easily persuaded to add something because it has interesting data in it. So I check my impulses with one question: will this let me operate differently when I look at it? And a second one, because it gets me if I'm not careful: am I checking the work, or am I rearranging the way I work?

My command center: the depth of the database without reading all of it

My main Dashboard view is what I call my command center. Across the top, it counts how many meetings I have today, how many open tasks, how many things are waiting on other people, and how many open decisions I have. Together those tell me my level of commitment for the day (or over-commitment, depending on the day). Below that sit my top priorities sorted by priority, my meetings, what's waiting on others, and the decisions I need to make. Active projects live at the bottom because I don't access them much.

Every one of those numbers comes from my task database. Meetings are tasks labeled as events. Open tasks are filtered to things due today with certain statuses. Waiting-on items are filtered to that status. Which means the view depends completely on what I've recorded. If I haven't updated a status or added a date, the view can't show me the reality I forgot to record. Before you make a layout more elaborate, check that the information you're asking it to summarize is actually there.

What I love about it: it gives me the depth of the database without forcing me to read the whole database every time I check it. It's the same lesson Tabs taught me. I still want all of my information. I want less of it demanding my attention at the same time. I've had this command center for under a month, and I haven't felt any compulsion to rebuild it. The only thing I adjust is the filtering, and if I'm honest, I'd tighten it to show only my next four tasks.

Custom Agents: let the agent gather, you decide

Tabs and Dashboard views still require me to open Notion and look. Custom Agents are where Notion starts doing some of the looking for me.

Human-first AI is an agent built to do the gathering so a person can do the deciding. Here's the version of that I watched work for a client. They were checking four tools every morning to figure out what needed attention: Slack, email, their calendar, and Notion. We built them a morning brief Custom Agent that gathers that information into one place, so they open one brief and see their meetings, priorities, anything they missed, and tasks waiting on a response.

It needed the right permissions and connected sources, and it needed clear instructions. We gave it a very specific gathering job. The client still made the decisions, which is exactly how I want it. A Custom Agent can only use the Notion pages, databases, and connected tools you've actually set up and allowed it to access.

I held off on agents for a long time because I was afraid of the cost, and meanwhile I was doing manual work I frankly shouldn't have been doing. When I finally asked myself whether I'd pay 30 bucks a month [CHECK] to make sure a specific thing got done, the answer kept coming back yes.

What a useful agent needs before you trust it

I built three agents recently, each one for a problem I could name. Evie [CHECK] is my email manager: she triages, archives, clears the noise, and flags urgent mail. Her instructions say in plain language that she does not write or send email. I respond, and I handle the relationship. My community scout reviews community notification emails I filter into one label and curates a prioritized brief of relevant opportunities and potential clients, then I choose where, when, and with whom I participate. My weekly follow-up co-pilot reviews due and overdue follow-ups in my client CRM, prepares drafts in the CRM records, and creates a linked review task, so I check the context, edit the message, and decide whether and when to send it.

Before you build one, decide what counts as a priority. A due date? A direct request? Something explicitly marked for review? Those are very different instructions. Tell the agent to make uncertainty visible: if a source wasn't accessible, say so, and if a date is missing, say so. Then test the first output against the sources. Did it miss something important, include something irrelevant, or treat an old item as current? If the source page is wrong, AI will deliver the wrong answer with incredible efficiency. Wrong is still wrong.

If you can't name the problem, leave the feature alone

Here's where I've landed, and I'll stand by it: "How can I use this?" is the wrong question to ask when Notion ships something new. It can talk me into almost anything. I can always find a use, because I like building things. Then I have to remember it, update it, check it, and figure out whether I still need it.

So now I ask, "Which repeated problem would this remove?" Tabs removed constant page switching. A morning brief agent removed gathering from four places. A follow-up agent removed digging up context before I followed up with a prospective client. If I can't name the problem a feature will solve, I leave the feature alone. I can like a feature without adding it.

Your one move: open one Notion page you use regularly and notice the first place you stop, search, or scroll past something you don't need. Finish the sentence "When I open this page, I'm trying to find ___." Change one thing that makes that answer easier to get, then use the page again before changing anything else. Don't rebuild the whole workspace. (I almost added "yet," but honestly, there are very few situations where you need to.) Visual overload? Test Tabs and drag your existing sections in. Can't read the state of one database? Test one Dashboard view around one operational question. Repeated information gathering? Map what you collect, where it lives, and what the brief needs to contain before you build an agent.

One problem, one feature, one honest test.