Optional setup

Group your parks into portfolios.

If you have logical groupings of parks — by region, by owner, by manager — define them once and ask portfolio-shaped questions forever after.

Why bother

Without portfolios, you ask things like:

"What's the NOI of WG-MTN, WG-OAK, WG-RVR, WG-CRK, WG-PAS, WG-HRZ,
 WG-DCK, and WG-FRN last month?"

With portfolios, you ask:

"What's the NOI of the Western portfolio last month?"

Same answer, half the typing, less chance of forgetting a park. Once portfolios exist, AskRentAI auto-detects them in every question.

The portfolios JSON shape

Portfolios are stored as a JSON object on your tenant. Each key is the portfolio name; each value is an array of park codes (the short codes shown in Rent Manager — e.g. WG-MTN).

{
  "Western": ["WG-MTN", "WG-OAK", "WG-RVR", "WG-CRK"],
  "Southeast": ["SE-PIN", "SE-OAK", "SE-CYP"],
  "RV": ["RV-LAK", "RV-COA"]
}

Park codes must match Rent Manager exactly. Including dashes, capitalization, and any prefixes. If RM stores it as WG-MTN, write WG-MTN — not wgmtn or WG MTN.

How to set portfolios

Option A · at signup

Paste the JSON into the Portfolios field on the signup page. Done in one shot.

Option B · update after signup (API)

You can update portfolios any time by calling PATCH /admin/tenants/me with your AskRentAI bearer token. Example using curl:

curl -X PATCH https://api.askrentai.com/admin/tenants/me \
  -H "Authorization: Bearer rmk_YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "portfolios": {
      "Western":   ["WG-MTN", "WG-OAK", "WG-RVR", "WG-CRK"],
      "Southeast": ["SE-PIN", "SE-OAK", "SE-CYP"]
    }
  }'

Option C · email it to me

If you'd rather not deal with curl, email your portfolios JSON to brian@askrentai.com and I'll patch it for you. Acceptable for v1 — not a forever workflow.

Common patterns

By region

{
  "Western":   ["WG-MTN", "WG-OAK"],
  "Central":   ["CN-RDR", "CN-PRA"],
  "Southeast": ["SE-PIN", "SE-OAK"]
}

By owner / entity

{
  "Fund I":  ["WG-MTN", "SE-PIN", "CN-RDR"],
  "Fund II": ["WG-OAK", "SE-OAK", "CN-PRA"],
  "Personal": ["RV-COA"]
}

By manager / zone leader

{
  "Jamie's zone":  ["WG-MTN", "WG-OAK", "WG-CRK"],
  "Pat's zone":    ["SE-PIN", "SE-OAK"],
  "House parks":   ["RV-LAK", "RV-COA"]
}

By type / asset class

{
  "MHP":      ["WG-MTN", "WG-OAK", "SE-PIN", "SE-OAK"],
  "RV":       ["RV-LAK", "RV-COA"],
  "Mixed":    ["CN-RDR"]
}

Parks can belong to multiple portfolios. A park can be in both "Western" and "Fund I" — useful when you slice the portfolio different ways for different questions.

Asking portfolio questions

Once portfolios exist, plain English works. Any of these will resolve correctly:

"What's the NOI of the Western portfolio last month?"
"Run a P&L trend on Fund I for the last 12 months."
"Which parks in Jamie's zone are below budget this quarter?"
"Compare Western vs Southeast on water reconciliation."

Updating portfolios as the portfolio changes

Acquired a new park? Sold one? Just PATCH the full portfolios object again — it replaces the previous version. There's no per-park "add" or "remove"; sending the whole object is the simpler contract.

Order doesn't matter. Whitespace doesn't matter. The JSON shape is the only thing that matters.