← Documentation

Administrator guide

The admin surface is Microsoft Lists — no separate admin app to deploy.

Fastest setup — entirely inside the add-in, no IDs to find:

1. Settings → search for your SharePoint site by name and pick it (or paste a URL).
2. Create missing lists — all three lists are created with the correct columns.
3. Add a division route — team, channel, and tag are dropdowns populated from your own Teams memberships; the add-in writes the routing rule for you.

Repeat step 3 per division. Requires edit rights on the site.

4. Test my setup — Settings → "✅ Test my setup" → Run all checks. Verifies sign-in, the site and all three lists, every routing rule (live check that each channel and tag actually exists in its team), the bill feed, the parser, and tracker write access — without posting anything. Two opt-in live tests send a clearly-labeled test post to a channel of your choice and a test email to yourself. "Copy results" produces a report you can email if something fails.
5. Import the contact list — Settings → "Import contact list": paste Name/Email/Division rows straight from the coordinator's spreadsheet or contacts export (divisions like "MVD/TDD" assign both). Preview shows exactly what merges where; emails are added to each division's rule and never removed. Unknown divisions become new rules flagged to receive a Teams channel. The sections below

document the schemas for admins who prefer to create or audit everything manually
in Microsoft Lists (both paths produce identical lists).

1. Create the routing list

On your chosen SharePoint site, create a list named LegislativeRoutingMatrix
with these columns (all "Single line of text" unless noted):

Rule semantics: a division token from the report matches a rule when it
equals the DivisionCode, DivisionName, or any alias (case-insensitive). Among
matches that are active and within their effective dates, the highest
Priority wins. Session handoffs = add the new rule with a later
EffectiveStartDate and end-date the old one; history stays intact.

2. Create the audit list

Same site, list named LegislativeAudit, columns (Single line of text):

Title (bill number)   ReportKey   IdempotencyKey   TeamId   ChannelId
TeamsMessageId   Status   Error   Divisions   EmailRecipients
PublishedBy   SourceSubject

The add-in appends one row per publish attempt. Do not delete rows for
reports that may be re-run — the IdempotencyKey rows are what prevent
duplicate posts.

2b. Create the bill tracker list (recommended)

Same site, list named BillTracker — this is the shared "who's waiting on
who" board and replaces individual completeness spreadsheets. Columns:

The add-in writes one Pending review row per bill × division at publish
time; division staff update Status themselves.

Pin it in Teams: in the legislative channel, **+ Add a tab → Lists →
existing list → BillTracker**. Create these views:

• *My division* — filter Division = yours (the "filter tagged bills" ask)
• *Still waiting* — Status = Pending review, grouped by Division, sorted by DueDate (the cross-divisional "who's waiting on who" board)
• *Overdue* — Pending review AND DueDate < today

2c. Templates

Fill-in files showing exactly what each list expects:

• Contacts template — Name / Email / Division rows for the add-in's paste-import (step 4 of setup).
• Routing matrix template — the full column set with sample rows, for bulk-building rules in Excel and importing via Microsoft Lists. Leave the Teams ID columns blank — the add-in's pickers fill those; everything else imports as-is.

3. Import the existing Excel routing matrix

Microsoft Lists imports Excel directly: List → ⋯ → "Export/Import" or create
the list *from* the Excel file, then rename columns to match the table
above. For tag IDs, use the add-in's tag lookup (Settings → paste the Team
ID → Fetch tags) and copy each TeamsTagId into the matching row.

4. Permissions to grant

• Coordinators: edit on both lists (audit rows are written as them).
• Division reviewers: no list access needed — they just receive posts/emails.
• The Entra app needs one-time admin consent (docs/permissions.md).

5. Validating a route

In the add-in: Settings → connect the site → parse a test report → the
Review screen shows exactly which rule each division resolved to and flags
rules missing tag IDs. Preview shows the rendered post before anything is
published.

6. Using a different state (or Congress)

The add-in is state-configurable:

1. Settings → State / legislature — pick your state. This presets the bill identifier prefixes the parser recognizes (editable — e.g. add "LB" for Nebraska's unicameral if needed).
2. New-filings feed: Iowa uses the Legislature's own RSS. Every other state uses the Open States API via the deployment's feed mirror (verified live: Iowa 1,917 and Texas 1,185 bills in a 1-year window). Congress: the parser preset works for federal bill reports, but Open States carries state data only - a congress.gov API adapter is a planned addition for the federal new-filings feed. Mirror setup: add the state's name to states.json in the repository and set the OPENSTATES_API_KEY repository secret (free key from openstates.org). The scheduled mirror then publishes feeds/openstates-<state>.json automatically.
3. Everything else (routing matrix, tracker, audit) is already org-specific — each organization points at its own SharePoint site.
4. Org profile: after configuring, use Settings → Org profile → Copy profile, and send the code to your team; they paste + Apply and are fully configured.

7. Code chapter tracking

Bill briefs reference the Iowa Code ("Amends Code Chapter 9", "Code
chapters 6A and 6B"). The add-in extracts these references and:

• shows them as chips on each bill in Review (checkmarked when they hit the agency's tracked list),
• flags newly filed bills in the Filings tab whose descriptions touch tracked chapters (even when no watch term matches),
• suggests divisions for unrouted bills when routing rules claim chapters via the optional CodeChapters column.

The tracked list ships seeded from the DOT's 2015 tracking list
(Settings → "Tracked Code chapters") and is FULLY EDITABLE — the 2015
list predates several Code changes, so review it with your legislative
coordinator and paste the updated set. It travels with org profiles.

8. Generating the Daily Bill Report (feed → report → everywhere)

The Router can compose the daily report itself:

1. Setup → Daily Bill Report generation: paste the report's To: line (addresses extract automatically) and set the session name.
2. Each morning: Filings tab → Check new filings. Bills already included in past reports are hidden; new ones show with watch-term and tracked-chapter matches. Select → Route selected bills.
3. Divisions are auto-suggested from each rule's CodeChapters column — verify on Review (auto-suggested items carry a warning until you look).
4. Publish with "Draft the Daily Bill Report email" ticked (pre-ticked for feed-originated bills): one Teams post per bill with mentions, consolidated division emails, tracker rows, audit — and the formatted Daily Bill Report lands in YOUR DRAFTS addressed to the distribution list. Review it, send it. Nothing ever sends by itself.

The generated report's text round-trips through the Router's own parser,
so recipient agencies running their own Router can parse it directly.