Info
Info is what your org already knows about the situation behind an agent’s question: your fiscal calendar, your currencies, who reports to whom. You don’t write one — ContextWorks computes each. Decide which domains carry which on Build → Info.
How it works
Every Info answers Get Info in full, with parameters, so an agent can ask for last quarter by name instead of guessing dates.
Some also put one short line on every payload the domain serves, and on the catalog. Which ones do is a live answer: ContextWorks works it out per call. No setting controls it.
Currencies stays quiet in a single-currency org. Fiscal Periods says nothing: the standing context line already carries today’s date and quarter. Record Links always speaks: payloads already carry record IDs, and its one line tells the agent to link any record it names, with the address to use. It comes after the data rather than before, next to where the agent starts writing its answer.
The On every payload column shows the line each one would add. That’s the line you would get; another user sees theirs, with their name and currency.
What ships
| Info | What it answers |
|---|---|
| Fiscal Periods | Your fiscal periods by name and boundary, this year and the years around it |
| Currencies | Which currencies the org uses, which one is corporate, and the rates between them |
| Team | Who you are, and who reports to whom in the role hierarchy |
| Record Links | Where your records live, so an answer can link to them |
Team walks the role hierarchy, not the forecast hierarchy. In an org that forecasts, those are different answers, and the Team description says so.
Turn one on
Check the box where an Info meets a domain. Each box saves as you check it. The same choices sit on each domain’s own Info tab.
The grid lists everything the package ships, on or off. There’s nothing else to configure.
See what an agent would get
Open Catalog Explorer from a domain. Info appears in the tree beside Entities, Briefs and Skills. Click one to run the real Get Info call. You get the answer verbatim, in Formatted, Markdown or JSON, with its token cost.
Best practices
- Turn Team off on a customer-facing domain. An external agent shouldn’t receive your reporting lines. Customer-facing columns carry a warning marker, so read down one to see what that audience receives.
- Leave Currencies on. It stays quiet in a single-currency org and speaks where amounts cross currencies.
- Turn Record Links off on a customer-facing domain too. A Lightning URL is no use outside your org, and a link an outsider can’t open is worse than none.
Limitations
You can’t write your own Info. The package ships the set, and each answer comes from code rather than a text box. That is the difference between an Info and a brief.
Notes
- A column you don’t manage shows read-only instead of hidden, so a domain manager sees the whole grid and edits their own part.
- The standing context line has its own org-wide switch on the Behavior settings page. Turning it off silences Info too. → Settings