[No QA] Update and rename Create-expense-tags.md to Create-and-manage-expense-tags.md by stephanieelliott · Pull Request #84478 · Expensify/App

stephanieelliott · 2026-03-07T02:56:38Z

Resource update request: https://github.com/Expensify/Expensify/issues/606928

…-tags.md

update redirects file

melvin-bot · 2026-03-07T02:58:45Z

melvin-bot · 2026-03-07T02:58:47Z

@Valforte @bfitzexpensify One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

github-actions · 2026-03-07T02:58:53Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+## How to create a tag manually
+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**


Formatting inconsistency: "navigation tabs" is not bold here, but it is bold in other sections (lines 28, 155, 164, 172). For consistency, wrap it in bold: **navigation tabs**. Also, this step is missing a period at the end.

Suggested change

1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**

1. In the **navigation tabs** (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**.

github-actions · 2026-03-07T02:58:55Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**
+2. Select **Tags**.
+3. Choose **Add tag**


Formatting inconsistency: This step is missing a period at the end. Also, "Choose" is used here but "Select" is used in parallel steps elsewhere in the article. Pick one verb and use it consistently throughout.

Suggested change

3. Choose **Add tag**

3. Select **Add tag**.

github-actions · 2026-03-07T02:58:57Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+## How to create a tag manually
+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**
+2. Select **Tags**.


Formatting inconsistency: Missing period at end of step.

Suggested change

2. Select **Tags**.

2. Select **Tags**.

github-actions · 2026-03-07T02:58:59Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+## How to import single-level Tags using a spreadsheet
+
+Use this option when you want one flat list of tags (for example: Marketing, Sales, IT).


Formatting inconsistency: "navigation tabs" is not bold here but is bold in other sections. Also missing a period at the end of this step.

Suggested change

Use this option when you want one flat list of tags (for example: Marketing, Sales, IT).

1. In the **navigation tabs** (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**.

github-actions · 2026-03-07T02:59:00Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+## How to import single-level Tags using a spreadsheet
+
+Use this option when you want one flat list of tags (for example: Marketing, Sales, IT).
+


Formatting inconsistency: Missing period at end of step.

Suggested change

2. Select **Tags**.

github-actions · 2026-03-07T02:59:01Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+Use this option when you want one flat list of tags (for example: Marketing, Sales, IT).
+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**


Formatting inconsistency: Missing period at end of step.

Suggested change

1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**

3. Select **More** > **Import spreadsheet**.

github-actions · 2026-03-07T02:59:11Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+---
+
+## How to import multi-level Tags using a spreadsheet
+


Formatting inconsistency: "navigation tabs" is not bold here but is bold in other sections (e.g., lines 28, 155, 164). For consistency, use **navigation tabs**.

Suggested change

1. In the **navigation tabs** (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**.

github-actions · 2026-03-07T02:59:14Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+---
+
+## How to create a tag manually


Heading capitalization inconsistency: "tag" is lowercase here, but other headings capitalize "Tags" (e.g., "How to enable Tags on a workspace", "How to import single-level Tags"). Choose one convention and apply it to all headings throughout the article.

Suggested change

## How to create a tag manually

## How to create a Tag manually

github-actions · 2026-03-07T02:59:15Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+3. Select one or more tags. 
+4. Choose **Selected** in the top right. 
+5. Select **Delete tag**.
+


Heading capitalization inconsistency: "tags" is lowercase here, but other section headings capitalize "Tags" (e.g., "How to enable Tags on a workspace", "How to import single-level Tags"). For consistency:

Suggested change

## How to delete expense Tags

github-actions · 2026-03-07T02:59:17Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+Workspaces on the Control plan can assign a GL code to each tag for exporting purposes. Tag GL codes are not visible to members.
+
+1. In the **navigation tabs** (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**.
+2. Select **Tags**.


Heading capitalization inconsistency: "tag" is lowercase here but capitalized ("Tags") in most other headings. For consistency:

Suggested change

2. Select **Tags**.

## How to add or edit a Tag GL code

github-actions · 2026-03-07T02:59:19Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+- [Dependent tags with GL codes](https://help.expensify.com/assets/Files/Dependent+with+GL+codes+format.csv)
+- [Dependent tags without GL codes](https://help.expensify.com/assets/Files/Dependent+without+GL+codes+format.csv)
+- [Independent tags with GL codes](https://help.expensify.com/assets/Files/Independent+with+GL+codes+format.csv)
+- [Independent tags without GL codes](https://help.expensify.com/assets/Files/Independent+without+GL+codes+format.csv)


Formatting inconsistency: "Notes:" (plural) is used here but only one bullet point follows. The rest of the article uses "Note:" (singular) for single-item notes. Use the singular form for consistency.

Suggested change

- [Independent tags without GL codes](https://help.expensify.com/assets/Files/Independent+without+GL+codes+format.csv)

**Note:**

github-actions · 2026-03-07T02:59:21Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**
+2. Select **Tags**.
+3. Select **More** > **Import spreadsheet**


Verb inconsistency: "Choose" is used here, but most other steps in the article use "Select". For consistency, use "Select" throughout.

Suggested change

3. Select **More** > **Import spreadsheet**

4. Select **Single level of tags**.

github-actions · 2026-03-07T02:59:28Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**.
+2. Select **Tags**.
+3. Select **More** > **Import spreadsheet**.


Verb inconsistency: "Choose" is used here, but most other steps in the article use "Select". For consistency, use "Select" throughout.

Suggested change

3. Select **More** > **Import spreadsheet**.

4. Select **Multi-level tags**.

github-actions · 2026-03-07T02:59:30Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+---
+
+## How to add or edit a tag GL code


Verb inconsistency: "Choose" is used here, but most other steps in the article use "Select". For consistency, use "Select" throughout.

Suggested change

## How to add or edit a tag GL code

4. Select **Selected** in the top right.

github-actions · 2026-03-07T02:59:32Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+**Notes:**
+ - Only CSV and TSV files are supported for multi-level tag imports. A single file can include up to 50,000 tags.
+


Readability / AI Readiness: This heading is long and hard to scan. Consider shortening it while keeping the full feature name. For example:

Suggested change

## How single-level and multi-level Tags affect expenses

github-actions · 2026-03-07T02:59:36Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+1. In the navigation tabs (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**
+2. Select **Tags**.
+3. Choose **Add tag**
+4. Enter a tag name and select **Save**.


Style compliance: Per Expensify HelpDot standards, end-of-flow confirmation buttons should use "Confirm" rather than "Save." If the UI button literally reads "Save," please disregard this comment -- but if the button text is actually "Confirm," this should be updated.

Same concern applies to line 175.

github-actions · 2026-03-07T02:59:40Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+ - Only CSV and TSV files are supported for multi-level tag imports. A single file can include up to 50,000 tags.
+
+---
+


Readability: The phrase "how many 'layers' of coding members must complete" is awkward and could be misread (it is unclear whether "coding members" is a noun phrase or "coding" modifies "layers"). Consider rephrasing for clarity:

Suggested change

Single-level Tags and multi-level Tags determine how many tag fields appear on each expense. This controls how many layers of coding a member must complete when submitting expenses.

github-actions · 2026-03-07T02:59:41Z

HelpDot Documentation Review

Overall Assessment

This PR renames and rewrites the expense tags documentation from Create-expense-tags.md to Create-and-manage-expense-tags.md. The rewrite is a substantial improvement over the original. It eliminates duplicate instructions that existed in the old file (the old version had the "add a single tag" steps listed twice), fixes the heading hierarchy (the old file incorrectly used multiple H1 headings for subsections), standardizes interaction verbs from "click" to "select"/"choose" for cross-platform consistency, and adds two valuable new explanatory sections covering single-level vs. multi-level tags and dependent vs. independent tags. The redirect in redirects.csv is properly handled. Overall, this is a strong rewrite with a few minor consistency issues worth addressing.

Scores Summary

Readability: 8/10 - Clear, well-organized prose at an appropriate reading level. Step-by-step instructions are easy to follow, and the new explanatory sections with concrete examples (State/City for dependent tags, Department/Location for independent tags) are especially helpful. Minor deductions for inconsistent punctuation in numbered steps (some end with periods, some do not) and for the removal of the "enable or disable tags" section from the old file, which leaves a small gap in coverage.
AI Readiness: 9/10 - Excellent improvements. Headings are descriptive and task-oriented (e.g., "How to import single-level Tags using a spreadsheet"), giving AI systems strong semantic signals. The YAML metadata is well-structured with a clear internalScope following the prescribed format. The heading hierarchy is correct: a single H1 for the title, H2 for all sections, and H1 for FAQ. One minor issue: the heading "How single-level Tags and multi-level Tags affect tag fields on expenses" is quite long and could be slightly condensed for readability without losing descriptiveness.
Style Compliance: 7/10 - Good adherence to Expensify voice and tone overall, but there are several consistency issues. The verb standardization from "click" to "select" is a welcome fix; however, capitalization of "Tags" is inconsistent throughout the document (sometimes capitalized mid-sentence as a feature name, sometimes lowercase), bold formatting of "navigation tabs" is applied in some sections but omitted in others, and punctuation at the end of numbered steps is not uniform. These are small issues but they accumulate across the document.

Key Findings

Positive aspects:

Eliminates the duplicate "add a single tag" instructions that existed in the old file (old lines 28-30 duplicated at lines 50-55).
Fixes the heading hierarchy: the old file used multiple H1 (#) headings for subsections, which violated the "H1 and H2 only" structure. The new file correctly uses H1 only for the page title and FAQ.
Replaces "click" with "select"/"choose" consistently, which is correct for documentation that covers both web and mobile platforms.
Adds two entirely new explanatory sections ("How single-level Tags and multi-level Tags affect tag fields on expenses" and "How dependent and independent multi-level Tags work") with clear, concrete examples.
Consolidates the navigation path from two steps (click Workspaces then Select your workspace name) into one (select Workspaces > [workspace name]), reducing friction.
Properly adds a redirect entry in redirects.csv so existing links will not break.
FAQ questions are rewritten in clearer, more member-centric language (e.g., "How can my Employees see the GL Codes?" becomes "Can members see Tag GL codes?").

Issues to address:

Inconsistent capitalization of "Tags": The document alternates between capitalizing "Tags" mid-sentence (treating it as a feature name, e.g., "single-level Tags") and using lowercase "tags" (e.g., "expense tags," "delete expense tags"). A consistent convention should be adopted. If "Tags" is a proper feature name when referring to the workspace feature, it should always be capitalized in that context; if referring generically to tag values, it should be lowercase.
Inconsistent punctuation in numbered steps: Some steps end with a period and some do not. For example, in "How to create a tag manually," steps 1 and 3 lack terminal periods while step 4 has one. This inconsistency appears across multiple sections.
Inconsistent bold formatting of navigation instructions: The "How to enable Tags on a workspace" section bolds navigation tabs, but the "How to create a tag manually" and both import sections do not bold it. Either all instances should be bolded or none.
Removed content -- enable/disable tags section: The old file included a "How to enable or disable expense tags" section explaining how to toggle individual tags on or off, and noted that tags imported from accounting systems are inactive by default. This information does not appear in the new file. Consider whether this section should be retained, as it covers a distinct use case from the "delete" workflow.
Long heading: "How single-level Tags and multi-level Tags affect tag fields on expenses" is lengthy. Consider condensing it, for example: "How tag levels affect expense fields."

Recommendations

Standardize "Tags" capitalization: Decide on a convention (capitalize when referring to the workspace feature, lowercase when referring to individual tag values) and apply it uniformly.
Normalize punctuation: Ensure all numbered steps either consistently end with periods or consistently omit them. Ending with periods is the more standard approach.
Normalize bold formatting: Apply the same bold treatment to "navigation tabs" and the navigation path across all step-by-step sections.
Consider restoring the enable/disable section: The ability to toggle tags on or off (and the note about accounting-imported tags being inactive by default) is useful information that was present in the old file. Consider adding it back, even as a brief subsection.
Condense the long heading: Shorten "How single-level Tags and multi-level Tags affect tag fields on expenses" to improve scannability.

Files Reviewed

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md (198 additions) -- New file. Substantially improved rewrite with better structure, expanded explanatory content, and corrected heading hierarchy. Has minor consistency issues with capitalization, punctuation, and formatting.
docs/articles/new-expensify/workspaces/Create-expense-tags.md (170 deletions) -- Deleted. Old file had duplicate instructions, incorrect heading hierarchy (multiple H1s), and inconsistent use of "click."
docs/redirects.csv (1 addition) -- Redirect from old URL to new URL properly added.

Note: Detailed line-by-line feedback has been provided as inline comments.

github-actions · 2026-03-07T02:59:42Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

+
+## What happens if a tag is disabled in my accounting system?
+
+It will be removed from the workspace’s tag list. However, it will still appear on expenses or reports where it was previously applied.


AI Readiness: "It" at the start of this answer is a vague reference. For better clarity and AI retrieval, restate the subject.

Suggested change

It will be removed from the workspace’s tag list. However, it will still appear on expenses or reports where it was previously applied.

The disabled tag will be removed from the workspace's tag list. However, it will still appear on expenses or reports where it was previously applied.

OSBotify · 2026-03-07T03:03:11Z

A preview of your ExpensifyHelp changes have been deployed to https://73ce6947.helpdot.pages.dev ⚡️

Updated articles:

articles/new-expensify/workspaces/Create-and-manage-expense-tags

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d71287b255

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-07T03:03:43Z

docs/articles/new-expensify/workspaces/Create-and-manage-expense-tags.md

@@ -0,0 +1,198 @@
+---


Add redirect for renamed tags article URL

Renaming this markdown file changes the published article path because our docs route generator derives href directly from the filename (.github/scripts/createDocsRoutes.ts), but this commit does not add a redirect from .../Create-expense-tags to the new slug. We still have multiple links pointing at the old URL (for example in src/CONST/index.ts and src/components/SidePanel/HelpContent/helpContentMap.tsx), so those links will start returning 404 after this deploy unless docs/redirects.csv is updated.

Useful? React with 👍 / 👎.

OSBotify · 2026-03-09T21:28:10Z

🚀 Deployed to staging by https://github.com/bfitzexpensify in version: 9.3.34-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-03-10T18:50:16Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.34-2 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Update and rename Create-expense-tags.md to Create-and-manage-expense…

d71287b

…-tags.md

stephanieelliott self-assigned this Mar 7, 2026

Update redirects.csv

ebccaff

update redirects file

stephanieelliott requested a review from a team as a code owner March 7, 2026 02:58

melvin-bot bot requested review from Valforte and bfitzexpensify and removed request for a team March 7, 2026 02:58

github-actions bot reviewed Mar 7, 2026

View reviewed changes

github-actions bot changed the title ~~Update and rename Create-expense-tags.md to Create-and-manage-expense-tags.md~~ [No QA] Update and rename Create-expense-tags.md to Create-and-manage-expense-tags.md Mar 7, 2026

chatgpt-codex-connector bot reviewed Mar 7, 2026

View reviewed changes

stephanieelliott removed the request for review from Valforte March 9, 2026 06:29

bfitzexpensify approved these changes Mar 9, 2026

View reviewed changes

bfitzexpensify merged commit c627215 into main Mar 9, 2026
14 checks passed

bfitzexpensify deleted the helpsite-fix-tags-page branch March 9, 2026 11:47

OSBotify mentioned this pull request Mar 9, 2026

Deploy Checklist: New Expensify 2026-03-09 #84634

Closed

75 tasks


		## How to create a tag manually

		1. In the navigation tabs (on the left on web, and at the bottom on mobile), select Workspaces > [workspace name]

	1. In the navigation tabs (on the left on web, and at the bottom on mobile), select Workspaces > [workspace name]
	1. In the navigation tabs (on the left on web, and at the bottom on mobile), select Workspaces > [workspace name].


		## How to import single-level Tags using a spreadsheet

		Use this option when you want one flat list of tags (for example: Marketing, Sales, IT).

	1. In the navigation tabs (on the left on web, and at the bottom on mobile), select Workspaces > [workspace name]
	3. Select More > Import spreadsheet.

	- [Independent tags without GL codes](https://help.expensify.com/assets/Files/Independent+without+GL+codes+format.csv)
	Note:

	3. Select More > Import spreadsheet
	4. Select Single level of tags.

	3. Select More > Import spreadsheet.
	4. Select Multi-level tags.

	## How to add or edit a tag GL code
	4. Select Selected in the top right.


		Notes:
		- Only CSV and TSV files are supported for multi-level tag imports. A single file can include up to 50,000 tags.


	Single-level Tags and multi-level Tags determine how many tag fields appear on each expense. This controls how many layers of coding a member must complete when submitting expenses.


		## What happens if a tag is disabled in my accounting system?

		It will be removed from the workspace’s tag list. However, it will still appear on expenses or reports where it was previously applied.

	It will be removed from the workspace’s tag list. However, it will still appear on expenses or reports where it was previously applied.
	The disabled tag will be removed from the workspace's tag list. However, it will still appear on expenses or reports where it was previously applied.

Conversation

stephanieelliott commented Mar 7, 2026

Uh oh!

melvin-bot bot commented Mar 7, 2026 • edited by bfitzexpensify Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Concierge reviewer checklist:

Uh oh!

melvin-bot bot commented Mar 7, 2026

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Mar 7, 2026

HelpDot Documentation Review

Overall Assessment

Scores Summary

Key Findings

Recommendations

Files Reviewed

Uh oh!

github-actions bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Mar 7, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 7, 2026

Choose a reason for hiding this comment

Uh oh!

melvin-bot bot commented Mar 7, 2026 •

edited by bfitzexpensify

Loading