diff --git a/content/en/docs/Document Management/adding-accounts/add-onedrive-account.md b/content/en/docs/Document Management/adding-accounts/add-onedrive-account.md
index febf997..7897abd 100644
--- a/content/en/docs/Document Management/adding-accounts/add-onedrive-account.md
+++ b/content/en/docs/Document Management/adding-accounts/add-onedrive-account.md
@@ -45,28 +45,37 @@ Both values are displayed on the application overview page immediately after reg
1. In the left sidebar, select **API permissions** under **Manage**.
2. Click **+ Add a permission**.
3. Select **Microsoft Graph**.
-4. Select **Delegated permissions** or **Application permissions** depending on your access model:
- - Use **Application permissions** for unattended/service access (most common for PlaidCloud Document)
-5. Search for and select the following permissions:
- - `Files.Read.All` — to read files and folders
- - `Files.ReadWrite.All` — if PlaidCloud Document needs to write files
- - `Sites.Read.All` — if accessing SharePoint-backed OneDrive for Business libraries
-6. Click **Add permissions**.
-7. Click **Grant admin consent for [your organization]** and confirm.
+4. Add the following permissions, selecting the type indicated for each:
+ - `Directory.ReadWrite.All` (Application) — Read and write directory data
+ - `Files.Read.All` (Application) — Read files in all site collections
+ - `Files.ReadWrite.All` (Application) — Read and write files in all site collections
+ - `Sites.ReadWrite.All` (Application) — Read and write items in all site collections
+ - `User.Read` (Delegated) — Sign in and read user profile
+ - `User.Read.All` (Application) — Read all users' full profiles
+5. Click **Add permissions**.
+6. Click **Grant admin consent for [your organization]** and confirm.
---
### Find the OneDrive Drive Path (Start Path)
-The **Start Path** in PlaidCloud Document controls which folder in OneDrive is used as the root for the account. To find the correct path:
+The **Start Path** in PlaidCloud Document controls which drive or folder in OneDrive is used as the root for the account.
-1. Open [OneDrive](https://onedrive.live.com) or your organization's SharePoint-based OneDrive for Business in a browser.
-2. Navigate to the folder you want to use as the root for this PlaidCloud Document account.
-3. The path shown in the browser's address bar or the folder breadcrumb reflects the folder hierarchy within OneDrive.
-4. Use the relative path from the root of the drive as the **Start Path** — for example, `/Documents/Finance` or `/Shared/Data`.
+In the most common scenario, the registered application has access to multiple drives or SharePoint sites. In this case the Start Path must begin with the name of the drive or site. For most OneDrive for Business accounts this is simply:
+
+```
+Documents
+```
+
+To target a specific subfolder within that drive, append the folder path:
+
+```
+Documents/Finance
+Documents/Shared/Data
+```
{{< note >}}
-To use the entire OneDrive as the root, leave the Start Path blank. To restrict PlaidCloud Document to a specific folder and its contents, enter the path to that folder.
+If the application only has access to a single drive, the Start Path can be left blank to use the root of that drive. When in doubt, start with `Documents` as the drive name.
{{< /note >}}
---
diff --git a/content/en/docs/markdown_example.md b/content/en/docs/markdown_example.md
deleted file mode 100644
index e15dc13..0000000
--- a/content/en/docs/markdown_example.md
+++ /dev/null
@@ -1,407 +0,0 @@
----
-title: Markdown Example Page
-main_menu: false
----
-
-PlaidCloud Documentation (this page) uses markdown in its construction. For those who would like to contribute to the development of PlaidCloud Documentation, please contact your representative or send an email to info@plaidcloud.com
-
-This page serves two purposes:
-
-- Demonstrate how the PlaidCloud documentation uses Markdown
-- Provide a "smoke test" document we can use to test HTML, CSS, and template
- changes that affect the overall documentation.
-
-## Heading levels
-
-The above heading is an H2. The page title renders as an H1. The following
-sections show H3-H6.
-
-### H3
-
-This is in an H3 section.
-
-#### H4
-
-This is in an H4 section.
-
-##### H5
-
-This is in an H5 section.
-
-###### H6
-
-This is in an H6 section.
-
-## Inline elements
-
-Inline elements show up within the text of paragraph, list item, admonition, or
-other block-level element.
-
-Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor
-incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis
-nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
-Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu
-fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
-culpa qui officia deserunt mollit anim id est laborum.
-
-### Inline text styles
-
-- **bold**
-- _italic_
-- ***bold italic***
-- ~~strikethrough~~
-- underline
-- _underline italic_
-- **underline bold**
-- ***underline bold italic***
-- `monospace text`
-- **`monospace bold`**
-
-## Lists
-
-Markdown doesn't have strict rules about how to process lists. When we moved
-from Jekyll to Hugo, we broke some lists. To fix them, keep the following in
-mind:
-
-- Make sure you indent sub-list items **2 spaces**.
-
-- To end a list and start another, you need a HTML comment block on a new line
- between the lists, flush with the left-hand border. The first list won't end
- otherwise, no matter how many blank lines you put between it and the second.
-
-### Bullet lists
-
-- This is a list item
-* This is another list item in the same list
-- You can mix `-` and `*`
- - To make a sub-item, indent two spaces.
- - This is a sub-sub-item. Indent two more spaces.
- - Another sub-item.
-
-
-
-- This is a new list. With Hugo, you need to use a HTML comment to separate two
- consecutive lists. **The HTML comment needs to be at the left margin.**
-- Bullet lists can have paragraphs or block elements within them.
-
- Indent the content to be the same as the first line of the bullet point.
- **This paragraph and the code block line up with the first `B` in `Bullet`
- above.**
-
- ```bash
- ls -l
- ```
-
- - And a sub-list after some block-level content
-
-- A bullet list item can contain a numbered list.
- 1. Numbered sub-list item 1
- 2. Numbered sub-list item 2
- 3. Numbered sub-list item 3
- 4. Numbered sub-list item 4
- 4. Numbered sub-list item 5
-
-### Numbered lists
-
-1. This is a list item
-2. This is another list item in the same list. The number you use in Markdown
- does not necessarily correlate to the number in the final output. By
- convention, we keep them in sync.
-3. {{}}
- For single-digit numbered lists, using two spaces after the period makes
- interior block-level content line up better along tab-stops.
- {{}}
-
-
-
-1. This is a new list. With Hugo, you need to use a HTML comment to separate
- two consecutive lists. **The HTML comment needs to be at the left margin.**
-2. Numbered lists can have paragraphs or block elements within them.
-
- Indent the content to be the same as the first line of the bullet
- point. **This paragraph and the code block line up with the `N` in
- `Numbered` above.**
-
- ```bash
- ls -l
- ```
-
- - And a sub-list after some block-level content. This is at the same
- "level" as the paragraph and code block above, despite being indented
- more.
-
-### Tab lists
-
-Tab lists can be used to conditionally display content, e.g., when multiple
-options must be documented that require distinct instructions or context.
-
-{{< tabs name="tab_lists_example" >}}
-{{% tab name="Choose one..." %}}
-Please select an option.
-{{% /tab %}}
-{{% tab name="Formatting tab lists" %}}
-
-Tabs may also nest formatting styles.
-
-1. Ordered
-1. (Or unordered)
-1. Lists
-
-```bash
-echo 'Tab lists may contain code blocks!'
-```
-
-{{% /tab %}}
-{{% tab name="Nested headers" %}}
-
-### Header within a tab list
-
-Nested header tags may also be included.
-
-{{< warning >}}
-Headers within tab lists will not appear in the Table of Contents.
-{{< /warning >}}
-
-{{% /tab %}}
-{{< /tabs >}}
-
-### Checklists
-
-Checklists are technically bullet lists, but the bullets are suppressed by CSS.
-
-- [ ] This is a checklist item
-- [x] This is a selected checklist item
-
-## Code blocks
-
-You can create code blocks two different ways by surrounding the code block with
-three back-tick characters on lines before and after the code block. **Only use
-back-ticks (code fences) for code blocks.** This allows you to specify the
-language of the enclosed code, which enables syntax highlighting. It is also more
-predictable than using indentation.
-
-```
-this is a code block created by back-ticks
-```
-
-The back-tick method has some advantages.
-
-- It works nearly every time
-- It is more compact when viewing the source code.
-- It allows you to specify what language the code block is in, for syntax
- highlighting.
-- It has a definite ending. Sometimes, the indentation method breaks with
- languages where spacing is significant, like Python or YAML.
-
-To specify the language for the code block, put it directly after the first
-grouping of back-ticks:
-
-```bash
-ls -l
-```
-
-Common languages used in PlaidCloud documentation code blocks include:
-
-- `bash` / `shell` (both work the same)
-- `go`
-- `json`
-- `yaml`
-- `xml`
-- `none` (disables syntax highlighting for the block)
-
-### Code blocks containing Hugo shortcodes
-
-To show raw Hugo shortcodes as in the above example and prevent Hugo
-from interpreting them, use C-style comments directly after the `<` and before
-the `>` characters. The following example illustrates this (view the Markdown
-source for this page).
-
-```none
-{{}}
-```
-
-## Links
-
-To format a link, put the link text inside square brackets, followed by the
-link target in parentheses. [Link to PlaidCloud.com](https://plaidcloud.com/) or
-[Relative link to docs.plaidCloud.com](/)
-
-You can also use HTML, but it is not preferred.
-Link to PlaidCloud.com
-
-## Images
-
-To format an image, use similar syntax to [links](#links), but add a leading `!`
-character. The square brackets contain the image's alt text. Try to always use
-alt text so that people using screen readers can get some benefit from the
-image.
-
-
-
-To specify extended attributes, such as width, title, caption, etc, use the
-figure shortcode,
-which is preferred to using a HTML `![]()
` tag. Also, if you need the image to
-also be a hyperlink, use the `link` attribute, rather than wrapping the whole
-figure in Markdown link syntax as shown below.
-
-{{< figure src="/images/pencil.png" title="Pencil icon" caption="Image used to illustrate the figure shortcode" width="200px" >}}
-
-Even if you choose not to use the figure shortcode, an image can also be a link. This
-time the pencil icon links to the PlaidCloud website. Outer square brackets enclose
-the entire image tag, and the link target is in the parentheses at the end.
-
-[](https://plaidcloud.com)
-
-You can also use HTML for images, but it is not preferred.
-
-
-
-
-## Tables
-
-Simple tables have one row per line, and columns are separated by `|`
-characters. The header is separated from the body by cells containing nothing
-but at least three `-` characters. For ease of maintenance, try to keep all the
-cell separators even, even if you heed to use extra space.
-
-| Heading cell 1 | Heading cell 2 |
-|----------------|----------------|
-| Body cell 1 | Body cell 2 |
-
-The header is optional. Any text separated by `|` will render as a table.
-
-Markdown tables have a hard time with block-level elements within cells, such as
-list items, code blocks, or multiple paragraphs. For complex or very wide
-tables, use HTML instead.
-
-
-
-
- | Heading cell 1 |
- Heading cell 2 |
-
-
-
-
- | Body cell 1 |
- Body cell 2 |
-
-
-
-
-## Visualizations with Mermaid
-
-You can use [Mermaid JS](https://mermaidjs.github.io) visualizations.
-The Mermaid JS version is specified in [/layouts/partials/head.html](https://github.com/PlaidCloud/website/blob/main/layouts/partials/head.html)
-
-```
-{{}}
-graph TD;
- A-->B;
- A-->C;
- B-->D;
- C-->D;
-{{}}
-```
-
-Produces:
-
-{{< mermaid >}}
-graph TD;
- A-->B;
- A-->C;
- B-->D;
- C-->D;
-{{}}
-
-```
-{{}}
-sequenceDiagram
- Alice ->> Bob: Hello Bob, how are you?
- Bob-->>John: How about you John?
- Bob--x Alice: I am good thanks!
- Bob-x John: I am good thanks!
- Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row.
-
- Bob-->Alice: Checking with John...
- Alice->John: Yes... John, how are you?
-{{}}
-```
-
-Produces:
-
-{{< mermaid >}}
-sequenceDiagram
- Alice ->> Bob: Hello Bob, how are you?
- Bob-->>John: How about you John?
- Bob--x Alice: I am good thanks!
- Bob-x John: I am good thanks!
- Note right of John: Bob thinks a long
long time, so long
that the text does
not fit on a row.
-
- Bob-->Alice: Checking with John...
- Alice->John: Yes... John, how are you?
-{{}}
-
-
More [examples](https://mermaid-js.github.io/mermaid/#/examples) from the official docs.
-
-## Sidebars and Admonitions
-
-Sidebars and admonitions provide ways to add visual importance to text. Use
-them sparingly.
-
-### Sidebars
-
-A sidebar offsets text visually, but without the visual prominence of
-[admonitions](#admonitions).
-
-> This is a sidebar.
->
-> You can have paragraphs and block-level elements within a sidebar.
->
-> You can even have code blocks.
->
-> ```bash
-> sudo dmesg
-> ```
->
-
-### Admonitions
-
-Admonitions (notes, warnings, etc) use Hugo shortcodes.
-
-{{< note >}}
-Notes catch the reader's attention without a sense of urgency.
-
-You can have multiple paragraphs and block-level elements inside an admonition.
-
-| Or | a | table |
-{{< /note >}}
-
-{{< caution >}}
-The reader should proceed with caution.
-{{< /caution >}}
-
-
-{{< warning >}}
-Warnings point out something that could cause harm if ignored.
-{{< /warning >}}
-
-
-
-## Includes
-
-To add shortcodes to includes.
-
-{{< note >}}
-{{< include "task-tutorial-prereqs.md" >}}
-{{< /note >}}
-
-## Katacoda Embedded Live Environment
-
-{{< kat-button >}}
-
----
-
-## Embed a custom markdown shortcode section
-
-{{< include "i-am-a-test.md" >}}