How to Build Notion Database for Content Moderation With Status Pipeline

You need a system to track submitted content through review, approval, and publication stages. A Notion database with a status pipeline provides a single place to manage drafts, assign reviewers, and monitor progress. This article explains how to create a moderation database from scratch, set up a linked status pipeline, and configure views that show exactly what each team member needs. By the end you will have a working content moderation board that updates automatically as items move through each stage.

What a Content Moderation Status Pipeline Does in Notion

A status pipeline is a series of stages that content passes through from submission to final publication. In Notion you represent each stage as an option in a Select property called Status. When you move a database item from one status to another, the item changes its position in any grouped view that uses the Status property. This creates a visual pipeline similar to a Kanban board.

Before you build the pipeline you need a Notion workspace where you can create new pages and databases. You also need at least one team member who will act as a content moderator. The pipeline works with any content type, including blog posts, user comments, images, or support tickets. The database structure stays the same regardless of what you moderate.

Core Properties for a Moderation Database

Every moderation database needs a set of standard properties to track the content and its progress.

• Title: Name of the content piece, such as the article headline or the submitter’s description.
• Status (Select): The pipeline stage. Default options: Submitted, In Review, Approved, Published, Rejected.
• Submitter (Person or Text): Who submitted the content. Use the Person property if the submitter is a workspace member.
• Reviewer (Person): The team member currently reviewing the item.
• Date Submitted (Date): Timestamp for when the item entered the pipeline.
• Notes (Text): Free-text field for reviewer comments or rejection reasons.

You can add more properties later, such as a URL property for the source link or a Files property for attachments. The Status property is the only one required for the pipeline to function.

Steps to Create the Moderation Database and Configure the Status Pipeline

1. Create a new database page
   On any Notion page click the + button in the left margin. Select Database and choose Table. Name the database Content Moderation. A blank table appears with a default Title column.
2. Add the Status property
   Click the + button in the last column header. Select Property type Select. Name the property Status. Click inside the new Status column header and select Add an option. Type Submitted and press Enter. Repeat to add In Review, Approved, Published, and Rejected. Drag the options to arrange them in pipeline order. Submitted should be first, Rejected last.
3. Add the remaining properties
   Click + in the last column header again. Add a Person property named Submitter. Add another Person property named Reviewer. Add a Date property named Date Submitted. Add a Text property named Notes. Your database now has all the fields needed for moderation.
4. Switch to a grouped board view
   Click the view name at the top left of the database (it says Table by default). Select Add a view. Choose Board layout. Name the view Pipeline. In the board configuration panel that appears, select Group by Status. The board now shows columns for each status option. Items with no status appear in a No Status column.
5. Add a test item to verify the pipeline
   Click the + New button in the Submitted column. Type Test content in the title field. Press Escape to close the card. The item appears in the Submitted column. Click on the card to open it. Set the Submitter to yourself and the Date Submitted to today. Change the Status to In Review. The card moves to the In Review column automatically.
6. Create a linked database view for the team dashboard
   Go to the main page where your moderation team works. Type /linked and select Linked view of database. In the pop-up choose the Content Moderation database. Select the Pipeline board view. Resize the linked view to fit the page. Every change made in the original database reflects here instantly.
7. Assign a reviewer to an item
   Open a card in the In Review column. Click the Reviewer field and type a team member’s name. The item now shows who is responsible. You can also add a filter to the board view that hides items assigned to other people.
8. Add a filter to show only your items
   Click the … menu next to the view name. Select Filter. Add a filter: Reviewer contains Me. The board now shows only items assigned to you. Create a duplicate view named My Queue for personal use.

Common Mistakes and Limitations When Using a Status Pipeline

Items disappear from the board when the status changes

If you filter a board view by a specific status and then change the item’s status to something outside the filter, the item vanishes from that view. This is not a bug. The item still exists in the database. Switch to the full Pipeline view to see all items again. To avoid confusion, keep one unfiltered view that shows every status.

Team members cannot see the linked database view

Linked database views inherit the permissions of the original database. If a team member cannot see the linked view, check the database sharing settings. Click Share on the original database page. Ensure the person has at least Can Edit access. Linked views do not bypass page-level permissions.

Dragging a card does not change the status

In a board view you can drag a card from one column to another to change its status. If dragging does not work, the view might be in Table or Gallery mode. Switch to Board mode. Also confirm that the Group by setting is set to Status. If you group by a different property, dragging moves the item to a different group but does not change the Status property.

The pipeline shows too many columns

By default every status option becomes a column. If you have options like Archived or Spam, those columns also appear. To hide them, click the … menu on the board view, select Group by, and uncheck the statuses you want to hide. Hidden columns still exist in the database but do not appear on the board.

Notion Database Views for Content Moderation: Board vs Table vs Gallery

View Type	Best For	Pipeline Behavior
Board	Visual pipeline management and drag-to-move actions	Items move between columns when you drag or change Status
Table	Bulk editing properties and sorting by date or reviewer	Status appears as a column value; no visual grouping
Gallery	Previewing images or rich content before approval	Status is a property tag; no drag-to-move

Use the Board view as your primary pipeline. Use the Table view for quick property edits and sorting. Use the Gallery view only when the content includes images or cover photos that need visual inspection before approval.

With the Content Moderation database and its status pipeline set up, you can track every piece of content from submission to publication. The Board view gives your team a visual overview, while the linked database view keeps the dashboard centralized. To extend the pipeline, add a Formula property that calculates the number of days an item has been in In Review. This lets you spot stalled items without opening each card.