list_users gives (name, email, role, currencies, status), plus your
own language and timezone — preferences that say how to answer you
and appear here and nowhere else. The company is deliberately minimal: id, name
and the fiscal calendar. Pass your own role id to get_role to read the
permissions behind your limits.
Read the fiscal calendar before interpreting any period. Every YYYY,
YYYY-SX and YYYY-QX label another tool returns is numbered on it, and
the company’s own fiscal year need not start in January. A response of
FY2027, 2026-02 → 2027-01 says the current fiscal year is FY2027 and
spans February 2026 through January 2027.
For the rest of the configuration — statement periods, currencies, the AI
agents your company runs, which optional modules are switched on — call
get_company_settings. For
the connected integrations, call
list_integrations.
access carries one key per resource you can actually reach
(statement, request, quota, data_table, report,
dashboard): how broadly you see it (scope plus a plain-language
description) and, for statements and requests, the saved views you may
pass to the matching list tool. Each view also carries access — the roles
and users who can read it — when you are allowed to share that resource. A
resource you have no access to carries no key at all — if a key is
missing, do not try to query that resource. Reports and dashboards report
all or shared only, like quotas: each is its own view, so a share
names the resource itself. A caller who reaches a report only through a
shared dashboard carries no report key — the values its tiles display are
named in that dashboard’s description instead of inventing a fifth
scope.
shared_resources names the resources shared with you individually — the
grants that reach past your role, already counted in access above. Pass
your own role id to get_role for
the other channel: what is shared with everyone holding your role. The rows
follow the same shape get_role returns. Sharing is a live-environment
concept, so those are the live ones.
Takes no arguments: the identity is read from the authenticated session, not
passed in. For the full profile (managers, groups, plan attributions, custom
attributes), call get_user with your own id or email.
Response
Body
Body
object
Same compact fields as each item in
list_users’s
response (id, resource_url, name, email, status, role,
payment_currency, calculation_currency, licensed, license_missing,
integrations, last_synced_at), plus two fields unique to this tool:object
object
One key per resource you can actually reach (
statement, request,
quota, data_table, report, dashboard): how broadly you see it
(scope plus a plain-language description) and, for statements and
requests, the saved views you may pass to the matching list tool. A
resource you have no access to carries no key at all. Full per-resource
schema: Access object reference.Resources shared with you individually, on top of whatever your role
grants — call
get_role with your own
role id for the other channel, which covers everyone holding it. This is
what lets you reach a view your role alone would deny, so access above
already accounts for it. Empty when nothing is shared with you
individually. Full field reference (resource, resource_type,
parent_name, access): get_role’s
shared_resources — same shape. Live environment only.