-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[No QA] [HOLD on image] Update docs to reflect GL Code column in Categories and Tags tables #81468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
3150d77
dd6de46
e037600
ac78ff4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,6 +9,8 @@ In Expensify, categories represent your **chart of accounts, GL accounts, expens | |
|
|
||
| Admins can manually create categories for a workspace, or they can be imported automatically when connected to an accounting platform like QuickBooks, Xero, NetSuite, or Intacct. Once imported, categories can be enabled or disabled as needed. Over time, Expensify also learns how you apply categories to specific merchants and suggests them automatically. | ||
|
|
||
| The Categories table displays the category **Name**, **GL Code** (if assigned), and whether it's **Enabled** for workspace members to use. | ||
|
|
||
| {:width="100%"} | ||
|
|
||
| --- | ||
|
|
@@ -136,5 +138,5 @@ It will be removed from the workspace’s category list. However, it will remain | |
|
|
||
| ## How Can My Employees See the GL Codes? | ||
|
|
||
| GL codes are not visible to employees by default. If visibility is required, consider including the GL code in the category name itself. | ||
| GL codes are visible to Workspace Admins in the Categories table but are not visible to workspace members. If you need members to see GL codes, consider including the GL code in the category name itself. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Terminology violation: Use "workspace members" instead of "employees" to match Expensify standards. The updated line 141 correctly uses "workspace members," but this FAQ question heading still uses the outdated term "Employees." |
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,8 @@ In Expensify, **tags** represent attributes like classes, projects, cost centers | |
|
|
||
| Admins can manually create one level of tags or multiple levels of tags for a workspace, or they can be imported automatically if your workspace is connected to an accounting system like QuickBooks Online, Intacct, Xero, or NetSuite. Once added, tags can be enabled or disabled. Expensify also learns your tag preferences for merchants and applies them automatically. | ||
|
|
||
| The Tags table displays the tag **Name**, **GL Code** (if assigned), and whether it's **Required** for expenses. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AI Readiness violation: Missing breadcrumb path below the H1 heading. According to HelpDot standards, articles should include a breadcrumb path (like "Settings > Workspaces > Tags") immediately after the H1 heading to help with AI navigation and context. |
||
|
|
||
| {:width="100%"} | ||
|
|
||
| --- | ||
|
|
@@ -39,7 +41,7 @@ Before you can manage tags, you need to enable the **Tags** feature for your wor | |
| 2. Click **More > Import spreadsheet** (or if you haven't added any tags yet, just click **Import** from the main Tags settings page). | ||
| 3. Click **Single level of tags**. | ||
| 4. Click **Choose File** and select the file to import. | ||
| 5. Toggle the "File contains column headers" on or off accordingly, then select which spreadsheet column should be mapped to which tag field. We require columns Name and Enabled, and you can optionally include a column for Tag GL Code. | ||
| 5. Toggle the "File contains column headers" on or off accordingly, then select which spreadsheet column should be mapped to which tag field. We require columns Name and Enabled, and you can optionally include a column for Tag GL Code. GL codes will be visible to Workspace Admins in the Tags table. | ||
| 6. Click **Import** to finish importing the tags. | ||
|
|
||
|
|
||
|
|
@@ -110,13 +112,13 @@ To manage tags in bulk: | |
|
|
||
| # Add or Edit a GL Code | ||
|
|
||
| If you're on the **Control** plan, you can assign a GL code to each tag for exporting purposes. These GL codes are not visible to workspace members. | ||
| If you're on the **Control** plan, you can assign a GL code to each tag for exporting purposes. GL codes are visible to Workspace Admins in the Tags table but are not visible to workspace members. | ||
|
|
||
| To add or edit a GL code: | ||
|
|
||
| 1. Go to **Workspaces > [Workspace Name] > Tags**. | ||
| 2. Click a tag to open its detail panel. | ||
| 3. Click the **GL Code** field, enter or update the code, then click **Save**. | ||
| 3. Click the **GL Code** field, enter or update the code, then click **Save**. The GL code will appear in the Tags table alongside the tag name. | ||
|
|
||
| --- | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -99,7 +99,7 @@ Available options: | |
|
|
||
| # Configure Tag Rules | ||
|
|
||
| Tag Rules allow tagging-based workflows and approvals. | ||
| Tag Rules allow tagging-based workflows and approvals. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Formatting violation: Trailing whitespace detected at the end of this line. Please remove the trailing space after "approvals." to maintain clean formatting. |
||
|
|
||
| To manage them: | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AI Readiness violation: This new line was added before the H1 heading and image reference, but there's no breadcrumb path below the H1. According to HelpDot standards, articles should include a breadcrumb path (like "Settings > Workspaces > Categories") immediately after the H1 heading to help with AI navigation and context.