---
title: Clear Task-Based Title Using the Feature Name (title case)
description: A short description of the page's content. This is used for SEO purposes.
keywords: [how to primary task, feature name, related task phrases]
internalScope: Audience is [who this doc is for]. Covers [single clearly defined workflow], does not cover [closely related workflows intentionally excluded].
---
<!--
This template follows the HelpDot governance standards.
Full guidelines: docs/HELP_AUTHORING_GUIDELINES.md
Naming, navigation, and capitalization: docs/HELPSITE_NAMING_CONVENTIONS.md

CORE AUTHORING RULES

- One primary workflow per article
- Use only # and ## headings (never ###)
- Headings must be full, searchable task-based phrases
- Do not use generic headings (e.g., Overview, Details, Setup, Options, Notes)
- Include the exact Feature Name in instructional headings
- Include web and mobile navigation instructions when applicable
- Use exact UI terminology and correct button casing
- Use title case for the article title and sentence case for every ## heading
- Use "select" for UI interactions (never click or tap) and "choose" only for decisions between options
- Lowercase roles and generic terms (workspace admin, workspace, expense report) unless quoting a UI label
- Do not use Liquid includes or collapsible FAQ sections
- If multiple distinct workflows are required, split into separate articles

ADDITIONAL HEADING GUIDANCE

Section headings beyond the primary workflow may vary depending on the feature.

Examples of acceptable headings:
- What the [Exact Feature Name] shows
- How [Exact Feature Name nuance] works
- How to manage [specific task] in [Exact Feature Name]
- How [Exact Feature Name] affects reimbursements
- How [Exact Feature Name] works with [integration] 
- How to troubleshoot [Exact Feature Name] errors

All headings must remain specific, searchable, and include the Feature Name when relevant.
-->

# [This must match the article title exactly]

Briefly explain:
- What this feature does
- Why someone would use it
- The outcome they can expect
- Any important limitations

Keep this concise and benefit-focused.

---

## Who can use [exact feature name]

Clearly state:

- Required role (workspace admin, member, domain admin, etc.)
- Plan limitations (Free, Collect, Control, Track, or Submit plan; annual or pay-per-use subscription)
- Any permission or workspace setting prerequisites

If this feature depends on another setting:
If [the required setting] is not enabled, [learn how to enable <Dependency Feature>](/relative-link).
If [the required setting] is not enabled, [learn how to enable [Dependency Feature]](/relative-link).
State explicitly if the feature is limited to one platform:
This feature is only available on web. It isn't available on mobile.

---

## How to [complete primary task using exact feature name]

<!--
NAVIGATION STRUCTURE GUIDANCE

If web and mobile navigation differ:
- Provide separate labeled sections:
  On web:
  On mobile:
- Do not merge instructions into one sentence.

If web and mobile navigation are structurally the same:
- Use a unified instruction.
- Example:
  In the navigation tabs (on the left on web, on the bottom on mobile), select **Workspaces > [workspace name] > Members**.
- Do not duplicate identical steps unnecessarily.

Follow the navigation rules in docs/HELPSITE_NAMING_CONVENTIONS.md (navigation tabs, navigation paths, navigation menu, More (⋮), fields, and the selection bar).
-->

1. In the navigation tabs (on the left on web, on the bottom on mobile), select **Workspaces > [workspace name] > [Section name]**.
2. Select **[Exact button name, matching the UI]**.
3. Configure the required settings.
4. Select **Save** or the final action button (for example, **Submit**, **Confirm**).

**ADD A SCREENSHOT HERE.**  
Suggestion: Show the full page with the relevant section highlighted.


## What happens after you [complete primary task using exact feature name]

Explain:
- System behavior
- Notifications triggered
- Approval or reimbursement impact
- Sync behavior (if applicable)
- Billing impact (if applicable)

Be explicit. Avoid vague phrasing.

---

# FAQ

## Can members [Common Task Variation Using Feature Name]?

Clear direct answer.

## Why can’t I see [Feature Name]?

Explain possible causes:
- You’re not a workspace admin or workspace owner
- The feature is not included in your plan
- The workspace setting is disabled
- Domain-level restrictions apply

## Does [Feature Name] work with [Integration or Related Feature]?

Provide a precise compatibility explanation.

## How do I troubleshoot issues with [Feature Name]?

Include only lightweight troubleshooting.
If complex troubleshooting is required, link to a separate dedicated article.