Codex
62220186af
- New ExternalImportSource and ExternalWorkHistoryEntry models, controller and migrations - Screening fields on external profile imports - Admin and provider profile views, routes and workflow tests updated - Phase 1 validation, route inventory, gap report template and roadmap docs - Add the Google Sheets work-order parser tool (tools/google-sheets-wo-parser)
29 lines
2.0 KiB
Markdown
29 lines
2.0 KiB
Markdown
# Setup and giveaway guide
|
|
|
|
## User setup
|
|
|
|
1. Make a copy of the published Google Sheet template into your own Google Drive.
|
|
2. Open the copy on a desktop browser.
|
|
3. Select **WO Parser > Set up / repair workbook**.
|
|
4. Review and approve the Google authorization screen.
|
|
5. The parser automatically finds recent Inbox messages from Field Nation and WorkMarket. No Gmail label or filter is needed.
|
|
6. Return to the Sheet and select **WO Parser > Check Gmail now** to verify it works immediately.
|
|
7. Open **New WOs** on the Google Sheets mobile app when you want the optional spreadsheet view.
|
|
|
|
The installer creates the labels `WO Parser/Processed` and `WO Parser/Needs Review`, plus a five-minute trigger. It scans only recent Inbox messages from Field Nation and WorkMarket senders; it does not delete or mark source mail read.
|
|
|
|
## Template owner setup
|
|
|
|
1. Create a clean Google Sheet under the project account.
|
|
2. Open **Extensions > Apps Script** and replace the default file with `src/Config.gs`, `src/Parsers.gs`, and `src/Code.gs` from this repository. Set the manifest from `appsscript.json`.
|
|
3. Reload the Sheet, run **WO Parser > Set up / repair workbook**, and use fabricated/redacted test messages from Field Nation or WorkMarket sender patterns in a test Inbox.
|
|
4. Share the finished sheet as **Anyone with the link > Viewer**. Do not give strangers edit access to the template itself.
|
|
5. Share a make-a-copy URL by replacing the final `/edit` portion of the sheet URL with `/copy`.
|
|
6. Publish this repository beside the template link so recipients can inspect the code.
|
|
|
|
Each recipient must run Setup in their own copy. Triggers belong to the Google account that creates them and do not make the template owner a reader of anyone else's Gmail.
|
|
|
|
## Updating a released template
|
|
|
|
Do not silently download or execute remote code in a user's Sheet. Publish a version number and release notes. For a breaking update, publish a new template and provide an import/export migration path for the old archive.
|