> ## Documentation Index > Fetch the complete documentation index at: https://assembly.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # App templates > Install a working app built by Assembly, then modify it — or add a Classic app as-is. A template is a working app, not a prompt. Installing one copies a finished app into your workspace, where you can use it immediately or hand it to the app builder to change. That makes it the fastest route when a template is close to what you need. Browse apps holds two different things, and it's worth knowing which you're looking at: * **Templates** — apps built by Assembly that you install and then modify like any app you built yourself. * **Classic apps** — Assembly's built-in apps. You install them as-is; the app builder can't change them. ## Where to find them From the sidebar, click **Add App**. * **Recommended for you** sits under the prompt box with a short, rotating set of suggestions. * **More ways to add → Browse all apps** opens the full catalog, where you can search or filter by category. * **More ways to add → Embed existing content** is a different path — it brings an outside tool into your portal rather than installing an app. See [Embeds and links](/docs/embeds-and-links/introduction). ## Prompt, template, or Classic app? Three ways to add an app, and the right one depends on how close the existing options are to what you need. | Start with | When | What you get | | ------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | A prompt | Nothing in the catalog matches, or your need is specific to how your firm works | A new app built from your description. See [Writing initial prompts](/docs/building-new-apps/writing-initial-prompts) | | A template | A template is close to what you want | A working app you can use now and change later | | A Classic app | You need core portal functionality — messaging, files, invoicing | A built-in app, configured but not modifiable | Some **Ideas** suggestions share a name with a template — Time tracker exists as both. The suggestion writes a fresh app from your words; the template installs one that already works. Start from the template when it's close, and from a prompt when you want something shaped to your process. ## Templates ### Onboarding * **Client onboarding wizard** — A five-step client onboarding flow that saves progress automatically while your team tracks who has finished, stalled, or not started. * **New client intake** — Collect scope, goals, stakeholders, budget, and timeline before kickoff, then review it all in one place. * **Document collector** — Request documents from clients with owners, due dates, and a status pipeline that replaces chasing them over email. * **Conditional forms** — Build forms with a drag-and-drop editor, send them by link or email, and track every submission through to a formatted PDF. ### Trackers * **Client project tracker** — Build milestone plans your team manages in detail and clients follow as a simple progress timeline. * **Deals Pipeline** — A pipeline board and table view for tracking deals, wired to your real Assembly CRM records rather than a separate copy. * **Time tracker** — Log billable hours against clients and export invoice-ready reports rolled up by client and date range. * **Case Status** — Move every case through one shared stage process and give clients a plain-language page showing where things stand and what happens next. * **Client calendar** — Month, week, and day calendar views with event scheduling, color-coded categories, and a dashboard of what's coming up. ### Knowledge base * **Client Resource Library** — A documentation-style library where clients browse and search the documents, guides, and recordings you publish. * **Data Room** — Share controlled files with named clients, revoke access instantly, and keep a full audit trail of every view and download. ### Internal * **Internal Communications** — Team chat with channels, DMs, threads, and reactions, built from your existing internal users. * **Internal Resource Library** — A searchable internal directory of policies, templates, and training materials, with an easy way to request what's missing. ### Approvals * **Design approvals** — Send clients a set of visual options to compare side by side, comment on, and pick a direction, across as many rounds as it takes. ### Requests * **Markup & comments** — Clients pin comments directly onto designs and PDFs while you ship revised versions until it's approved. ### Proposals * **Proposals** — Build branded, multi-page proposals with tiered packages and add-ons that clients accept and pay for in the portal. ### AI assistants * **Client AI assistant** — Give each client an AI assistant that answers from your knowledge base and their own data, and never anyone else's. ### Community * **Events & RSVPs** — Post upcoming events and let clients RSVP from their portal, with confirmations sent automatically and a full attendee list for your team. ### Support * **Client Support Requests** — A shared internal inbox where clients submit requests and your team replies openly or takes notes privately. A few templates appear under more than one category. Deals Pipeline is listed under both Trackers and Dashboards. ### Coming soon * **Content Approval** — Route drafts and deliverables to clients for sign-off, with comments, change requests, and a permanent decision history. * **Client Discussion Forum** — A shared community where clients and your team discuss topics in threaded conversations you moderate. * **Progress Tracker** — Define color-coded stages and move each contact or company through them, with a progress view clients can check anytime. ## Classic apps Classic apps are Assembly's own built-in apps, listed under the **Classic** category in Browse apps. They're configured in their own settings rather than rebuilt, and the app builder can't modify them — that's the difference from a template. The client's landing page in the portal One message thread per client Invoicing, subscriptions, and payment links Assign work to clients and your team eSignature with a full audit trail File sharing scoped per contact or company Client-facing forms with structured responses Ticket-based support for client requests Automated replies to incoming messages Let clients update their own details Bulk exports of your workspace data Sync Payments data with QuickBooks Online Sync Payments data with Xero ## After you install a template The app lands in your workspace as your app. From there it behaves like anything else the app builder made: * It starts hidden from clients until you make it visible. See [Controlling app visibility](/docs/building-new-apps/controlling-app-visibility). * You can change it in the build chat — rename fields, add a view, adjust the workflow. See [Iterating on apps](/docs/building-new-apps/iterating-on-apps). * It uses your workspace's branding, CRM, and contact list. There's no separate data to set up. Browse the catalog even when you plan to start from a prompt. Seeing how an existing template frames a workflow is a useful reference for describing your own.