Trait requirements
Which ARCYProvider traits each dashboard insight needs to activate, and which prop to pass them through.
Each dashboard insight activates once the accounts or users in your app carry the traits it needs. This page is the full mapping: what's required, what's optional, and which ARCYProvider prop (userTraits or organizationTraits) it goes through.
ARCYProvider checks this same mapping at runtime and prints a console
warning in development whenever a required trait for an active insight is
missing, naming the exact prop path to add.
Supported insights
| Insight | Entity scope | Prop path | Required traits | Optional traits |
|---|---|---|---|---|
| Revenue at risk / Recoverable now | Either (hybrid apps resolve to organizationTraits only, see note below) | userTraits or organizationTraits | plan, planValue, planCurrency | — |
| At-Risk Users | User | userTraits | None (behavioral, activates with no traits) | planValue, signupDate, billingCycle, renewalDate |
| At-Risk Organizations | Organization | organizationTraits | None (behavioral, activates with no traits) | planValue, signupDate, billingCycle, contractEndDate |
For Revenue at risk / Recoverable now: planValue alone still activates that account's own figure, but omitting planCurrency excludes it from the portfolio-wide totals. See Revenue Tracking for the full currency behavior.
For appType="hybrid" apps, Revenue at risk / Recoverable now resolves to organizationTraits only, not both scopes independently like most either-scoped insights. Most hybrid products bill at the account level, not the individual level, so this avoids requiring traits that don't apply to how the product actually bills.
How entity scope resolves
Most insights are scoped to user, organization, or either. An either-scoped insight resolves which prop path applies from your declared appType:
appType="b2c"→ resolves touserTraitsappType="b2b"(the default) → resolves toorganizationTraitsappType="hybrid"→ both scopes apply as independent figures, except Revenue at risk / Recoverable now (see note above)
See Configuration for the full userTraits/organizationTraits shape and prop reference.