[MelvinBot]

Explanation of Change

Adds help-site content for company agents. Today every agent article assumes the agent is personal and owned by the person who created it. Company agents are owned by a workspace or domain instead, so several existing statements are wrong for them.

• New article: ai-agents/Create-and-Manage-Company-Agents.md. It covers creating an agent from Workspaces > [workspace] > Agents, choosing its workspace role, who owns it, who can manage it, and how it differs from a personal agent.
• Create-and-Use-Agents.md: links to the new article, adds a section about the new Owner column in Account > Agents, and limits the "owner = creator" and "added as a Copilot on your account" statements to personal agents.
• Understand-How-Agents-Work.md: adds company agents to the feature list and the comparison table.
• Manage-Copilot-Access.md: limits "agents are added as Copilots on your account" to personal agents, and explains that admins of the owning workspace or domain get Copilot access to company agents.
• Managing-Workspace-Members.md: notes that the invite list only shows agents you can manage.

The content is based on the merged App PRs for this feature: Create company agents, Group personal and company agents in Account Settings, and Exclude non-manageable agents from workspace invite list.

Please check before merging:

1. Company agents are still behind the companyAgents beta. Merge this when the feature launches.
2. The note above Create agent says "This agent will be added as a full copilot of your account…" for company agents too. That's not true for company agents, so the new article doesn't quote it. The App copy may need a follow-up fix.
3. The New agent button shows for Editors and People admins, but only workspace admins can create company agents. The docs say workspace admins only.
4. The new article has a screenshot placeholder for the workspace Agents page.

AI tests: This is a docs-only change. I checked that every new internal link points to an existing article and that the new anchor matches its heading. I couldn't run createDocsRoutes.sh or the spell check locally because node_modules isn't installed in my environment. CI will run them.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/681642
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If the PR adds or modifies the UI:
  • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
  • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
  • I verified all new/changed elements have meaningful accessible names and roles.
  • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[OSBotify]

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

Updated articles:

• articles/new-expensify/ai-agents/Create-and-Manage-Company-Agents
• articles/new-expensify/ai-agents/Create-and-Use-Agents
• articles/new-expensify/ai-agents/Understand-How-Agents-Work
• articles/new-expensify/settings/Manage-Copilot-Access
• articles/new-expensify/workspaces/Managing-Workspace-Members