# Follow the Setup Checklist A printable, time-boxed checklist of every step a Salesforce Administrator needs to complete to roll Folio out to their org. This is the master checklist for rolling out Folio in a new org. Work through the **Required setup** items in order; the **Optional / Advanced** items can be done later as your team's needs grow. **Total time to set up: 30โ€“45 minutes.** --- ## Required setup ### Install and provision - [ ] **Confirm your edition is supported and Lightning Web Security is enabled (2 min)** โ€” Folio runs on Enterprise, Unlimited, Performance, and Developer Editions, and will not work without LWS, which is enabled by default in most orgs. See [Check the Prerequisites](/docs/getting-started/prerequisites). - [ ] **Install the package (5 min)** โ€” Install the Folio managed package from the Salesforce AgentExchange and choose the right install scope. See [Install the Package](/docs/getting-started/installation). - [ ] **Assign permissions (5 min)** โ€” Assign the **Folio Docs License** permission set license to every Folio user, then one permission set each: **Folio Docs User** for end users, **Folio Docs Administrator** for anyone who will manage the package. See [Assign Permissions](/docs/getting-started/licenses-and-permissions). ### Configure Folio Docs - [ ] **Configure settings in the Admin Panel (15 min)** โ€” Open the Folio Admin page and walk through every section. See [Use the Admin Panel](/docs/admin/admin-panel) for full details. - [ ] Select your **Linkable Objects** (the Salesforce objects users can attach Documents to). - [ ] For each Linkable Object, select the **Linkable Fields** that should be available to Live Fields and the Salesforce components. - [ ] For each Linkable Field, toggle **Enable Write-Back** where applicable. - [ ] Set the org-wide **Linkable Field Write-Back** master toggle. - [ ] Configure **Auto-Share Level with Record Owner** for each Linkable Object. - [ ] **Decide how the User object is configured โ€” it behaves differently from every other object.** For User, Auto-Share Level doesn't govern record ownership; it governs **@-mentions of people**. If User isn't among your Selected Objects, users cannot be @-mentioned in Document bodies at all. If it is, the level you pick is the access a mentioned person receives on the Document. See [Special case: the User object](/docs/admin/admin-panel/settings#special-case-the-user-object). - [ ] Turn on **Background Jobs** under Asynchronous Processing. This single toggle schedules all nine of Folio's background jobs: search indexing, search-by-record-name sync, Team member sharing, the usage data behind the [Dashboard](/docs/admin/admin-panel/dashboard), version history consolidation, email digests, the archive purge, and log, export, and notification cleanup. Enable it once during setup and leave it on โ€” see [Asynchronous Processing](/docs/admin/admin-panel/settings#asynchronous-processing). **Enable it as an account that will stick around** โ€” a system automation or integration service account, or a long-standing admin. The jobs run as whoever turns the toggle on, and stop if that user is ever deactivated. - [ ] Decide whether to run **Notification Email Digest**, and pick the Organization-Wide Email Address they send from โ€” it must have **Allow All Profiles to Use this From Address** enabled. Off by default; users choose their own frequency once you enable it. See [Notification Email Digest](/docs/admin/admin-panel/settings#notification-email-digest). - [ ] Configure **Automatic Team Sharing** with Account / Opportunity / Case Teams. - [ ] Configure **Automatic Record Linking** (Opportunity โ†’ Account, Contact โ†’ Account). - [ ] Set **Delete permissions** for Documents (hard-delete enabled or disabled). - [ ] **Set up real-time updates for objects beyond the built-in four (5 min per object)** โ€” **Account**, **Contact**, **Opportunity**, and **Case** work automatically with no setup. For every other Linkable Object, add an after-save record-triggered Flow calling **Folio: Refresh Document from Record Changes**. This keeps Documents current with record data and re-applies owner-based sharing when a record changes hands. See [Set up Real-Time Updates](/docs/admin/real-time-updates). ### Surface Folio in the UI - [ ] **Add components to the right Lightning pages (5 min per page)** โ€” Place the Folio Document Editor on the main content area of high-traffic record pages (Account, Opportunity, Case, etc.). See [Add Components to Lightning Pages](/docs/admin/adding-editors-to-record-pages). - [ ] **Add Folio Docs to the navigation bar for end users (2 min per app)** โ€” In each Lightning app where your users live (Sales, Service, etc.), edit the navigation items to include the **Folio Docs** tab so users have a one-click destination to find and edit their Documents. See [Add Folio Docs to the Navigation Bar](/docs/admin/adding-folio-docs-home-to-navigation). - [ ] **Add Folio Admin to the navigation bar for admins (2 min)** โ€” In your administrative app(s), add the **Folio Admin** tab to the navigation bar so administrators have one-click access to the Admin Panel for ongoing configuration changes. Use the same App Manager โ†’ Navigation Items workflow described in [Add Folio Docs to the Navigation Bar](/docs/admin/adding-folio-docs-home-to-navigation), but select the **Folio Admin** tab instead. --- ## Optional / Advanced These are not required to use Folio, but unlock more value as your team's needs grow. - [ ] **Set up Document Templates (15โ€“30 min, varies by complexity)** โ€” Build reusable starter Documents (Account Plans, Close Plans, CS Handoffs, Case Summaries) with merge fields that resolve from a Source Record at instantiation time. See [Manage Templates](/docs/admin/admin-panel/templates). - [ ] **Set up automations with invocable Apex (15+ min for the first flow)** โ€” Use Folio's invocable Apex actions in Salesforce Flow to automate Document creation, sharing, tagging, linking, and ownership transfer based on real-time business events. See [Automate with Invocable Apex](/docs/admin/automation-invocable-apex) and [Review Invocable Apex Use Cases](/docs/admin/invocable-apex-use-cases) for worked examples. - [ ] **Curate your Tag vocabulary (ongoing)** โ€” Once users start tagging, use the Tags tab to set colors on the Tags that carry org-wide meaning and merge the duplicates that inevitably appear. See [Admin Panel Tags](/docs/admin/admin-panel/tags). - [ ] **Review data retention (5 min if needed)** โ€” The **Data Retention** section at the bottom of the Settings tab controls how long version snapshots, notifications, export files, and logs are kept. The defaults are sensible; adjust them if your org has specific retention requirements. See [Data Retention](/docs/admin/admin-panel/settings#data-retention). --- ## After you ship - [ ] **Train your end users.** Point them at [What is Folio Docs?](/docs/user-guide/what-is-folio) and [Browse the Folio Docs home page](/docs/user-guide/folio-docs-home) as their starting points. Flag [View and Edit at the Same Time](/docs/user-guide/concurrent-editing) explicitly โ€” the one-editor-at-a-time model is the thing users are most likely to be surprised by. - [ ] **Check the Dashboard after a few weeks.** The [Dashboard tab](/docs/admin/admin-panel/dashboard) shows which objects and Templates are being used, and which Linkable Objects are going unused. **Related:** [Check the Prerequisites](/docs/getting-started/prerequisites) ยท [Install the Package](/docs/getting-started/installation) ยท [Assign Permissions](/docs/getting-started/licenses-and-permissions) ยท [Use the Admin Panel](/docs/admin/admin-panel)