> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/welcome-to-notionapps.md). # Welcome to NotionApps ## Welcome to NotionApps ### Overview NotionApps helps you turn Notion databases into secure, shareable applications for the people who need to view, create, update, and act on your data. At its simplest, NotionApps gives your Notion data a focused app experience: screens, forms, login, permissions, mobile-friendly layouts, branding, and a published link your users can open without entering your Notion workspace. The newer NotionApps goes beyond a CRUD app layer. With Automation, you can route work, notify the right people, manage approvals, start conversations, update records, and show users what is happening as work moves forward. ### What You Can Build Use NotionApps when you want to create real apps from the databases you already manage in Notion. Common app patterns include: * Client portals * Internal tools * Field team apps * Approval systems * Inventory and asset trackers * Timecard and operations apps * Project, task, and request portals * Private member or customer apps * Lightweight CRMs and service desks Your Notion workspace remains the source of truth. NotionApps gives each role a clean, focused interface for the work they need to do. ### App Builder The app builder is the foundation of NotionApps. With it, you can: * Connect Notion databases to an app. * Create list, detail, form, calendar, and data-entry screens. * Let users create and update Notion database items from the app. * Control which screens appear in navigation. * Protect private apps with login. * Restrict data so users only see records meant for them. * Add file uploads, images, signatures, maps, buttons, page content, and other interactive components. * Publish the app to a NotionApps URL or custom domain. * Give users a mobile-friendly app experience without sharing the underlying Notion workspace. ### Automation Automation turns your apps into operational systems. Instead of stopping after a form submission or database update, an app can decide what should happen next. A builder can start with a business outcome, and NotionApps can help assemble the workflow, messaging route, approval path, and testing steps behind it. Use Automation to: * Send notifications after a form is submitted. * Route requests to the right person or queue. * Create follow-up records or tasks. * Update Notion records after an action or decision. * Wait for a period of time, then escalate. * Branch based on status, priority, role, or form values. * Ask for approval and continue after a decision. * Start a private conversation around a request or record. * Broadcast announcements to app users. * Send structured events to another app or external webhook. * Accept external events and turn them into app records or workflows. * Test and inspect automation activity before relying on it in production. Automation is powered by Workflow, Messaging, and Approval Management. ### Workflow Workflow is the process engine. It runs the ordered steps that happen after a form submission, screen action, button click, record event, webhook, or other app event. Workflow can create and update records, send notifications, call webhooks, wait, branch, escalate, pause for decisions, and keep run history so builders and support teams can inspect what happened. ### Messaging Messaging is the communication and routing layer. It moves events between people, app screens, workflows, announcements, linked apps, and external systems. Use Messaging for routed notifications, app-wide announcements, contextual conversations, app-to-app events, webhook delivery, and delivery-status tracking. ### Approval Management Approval Management gives apps dedicated approval surfaces and approval-specific actions. Use it when users need to claim work, review requests, approve or reject items, hold decisions, manage queues, or keep requesters informed through status screens, messages, and notifications. ### Operational Screens Automation is most useful when users can see and act on the work inside the app. NotionApps can include native operational screens such as: * Notification Center * Conversation screens * Work Queue * Decision screens * Workflow Status * Exception Resolution * Operator Console * Linked App Exchange * Automation Launcher These screens let users participate in the process instead of leaving automation hidden in the background. ### Quick Links * [Connect Notion](https://docs.notionapps.com/basics/connect-notion) * [Create an app](https://docs.notionapps.com/basics/create-an-app) * [Share App](https://docs.notionapps.com/basics/share-app) * [Manage Workspaces](https://docs.notionapps.com/basics/manage-workspaces) * [Create Users Database](https://docs.notionapps.com/users/create-users-database) ### Get Started Start with your Notion database, choose the app experience your users need, then add automation where work needs to move forward. Good first projects include: * A client request portal that notifies the owner and tracks status. * An employee approval app that routes requests to a manager. * A field operations app that captures photos, signatures, and reports. * An inventory exception workflow that alerts the right team when counts are off. ### Community Use the NotionApps community to ask questions, share app ideas, and get help while building. [NotionApps Community](https://community.notionapps.com) ### Video Tutorials Video tutorials walk through common setup and customization workflows. {% embed url="" %} [Video Tutorials](https://docs.notionapps.com/video-tutorials) ### Use Cases Explore common NotionApps patterns and examples. [Use Cases](https://docs.notionapps.com/use-cases) ### In Short Notion stores the data. NotionApps gives that data an app experience. Automation helps the app move work forward. That is the new NotionApps: apps from Notion databases, plus the workflow, messaging, approvals, and operational screens needed to run real processes.