Administration
Audit log
Read who did what in your organization, and when, filtered by event and date.
Costfluent records identity and administrative actions for every organization, on every plan, and every plan reads the record back in the product and can export it.
Before you start
- Reading the audit log needs the Owner organization role.
Read the audit log
- Open Settings, then Audit logs. Entries are newest first, each with its Event, Object, Changes, Actor, IP and Time. Event names each event in words, with the name it is recorded under, such as
user.invited, below; Changes names roles, states and categories in words too. - Narrow them by Event, searching the list by an event's words or its recorded name, by Actor and Object, and by From (UTC) and To (UTC) dates. A recorded name the list does not hold can still be typed exactly and chosen. When no entry matches, Clear filters removes them all.
- Select Load more to read further back.

Export the log
- Open Settings, then Audit logs, and set Event, From (UTC) and To (UTC) to the entries you want.
- Select Export CSV. The file holds every entry those filters select.
What is recorded
Besides sign-ins and changes to members, teams and settings, the log records:
- notification channels:
app.created,app.updated,app.deletedand, when a webhook's signing secret is rotated,app.signing_secret_rotated, with the channel's kind, the host a webhook posts to and how many addresses an email channel mails, never its secret, its full address or its recipients; - issue trackers:
app.created,app.updatedandapp.deleted, with the tracker's kind and name, never its token, key or secret;issue_link.createdeach time a member asks a tracker for an issue, naming the tracker and the finding or anomaly; andsavings_item.updatedwith System as the actor when a completed issue moves its finding to Implemented. See Issue trackers; - annotations on cost reports:
annotation.created,annotation.updated,annotation.resolved,annotation.reopenedandannotation.deleted, with the note's day, text and reports. The markers budgets and cost alerts leave as they fire are not recorded here; the firing is. See Annotations; - report subscriptions:
cost_report_subscription.created,cost_report_subscription.updated,cost_report_subscription.activated,cost_report_subscription.deactivatedandcost_report_subscription.deleted; - segments and allocation rules:
segment.created,segment.updatedandsegment.deleted, andallocation_rule.created,allocation_rule.updatedandallocation_rule.deleted, a reorder recordingallocation_rule.updatedfor each rule it moves. See Segments and allocation rules; - the organization itself:
org.createdandorg.exported, besideorg.updated; - members leaving on their own,
membership.left, and invitations withdrawn before anyone accepted them,user.invite_revoked; - single sign-on being required or no longer required,
auth.sso.enforcement_changed, and Owners marked or unmarked as break-glass,auth.sso.break_glass_changed; - changes Costfluent's staff make to your organization:
org.updated,entitlement.limit_override_changed,entitlement.feature_grant_changed,entitlement.ingestion_halt_changed,billing.plan.changed,billing.subscription.resync_requestedwhen Costfluent asks its billing to read your subscription again from the payment processor,provider.sync_triggered,provider.replay_triggeredwhen Costfluent rebuilds your costs from the billing data already collected,provider.quarantine_retry_triggeredwhen it sends rows that could not be processed through again,provider.reconciliation_triggeredwhen it compares a month against your provider's invoice,provider_invoice.importedwhen it imports one of your provider's invoices for you,user.disabledanduser.enabledwhen Costfluent suspends or reinstates the account of one of your members, andorg.named_engineer_assignedandorg.named_engineer_clearedwhen a Costfluent engineer names themself your organization's named engineer or the name is removed; - the end of a partner's management:
org.management_endedin the organization's log, naming the partner, withbilling.subscription.cancel_scheduledwhen a paid subscription is set to end, andpartner.management_endedin the partner's log, naming the organization. See Organizations; - objections to an announced sub-processor change:
subprocessor_change.objected, with the version. See Organization and workspaces; - support requests:
support_ticket.createdwhen a member opens one,support_ticket.message_addedfor each message in its thread andsupport_ticket.resolvedwhen a member resolves it, naming the request by its number, category and status, never by its subject, messages or files.
Who acted
The Actor column says who took each action:
- the person's name, or their email address when they gave no name, for something a member of the organization did; "Former member" when that account no longer exists;
- System, for an action Costfluent took on its own;
- "Costfluent" and the staff member's name, for a change Costfluent's staff made to your organization. Such entries show no IP address, in the log or in the export;
- "Manager" and the partner's name, for an action taken by the partner that manages the organization. Such entries name the partner, not the person who acted for it, and show no IP address. See Organizations.
- in a partner's own log, the staff member's name with "in" and the customer organization's name under it, for an action they took in an organization the partner manages. Every such action is recorded in both logs; the export carries the organization's name in its last column,
managed_organization.
How it behaves
- Recording, reading and exporting do not depend on the plan.
- Exports of cost data are recorded here too; see Explore cost data.
- The log belongs to the organization, not to one workspace, so it uses UTC whatever time zone your workspaces keep: Time shows each entry in UTC, and From and To are UTC days. To includes the day you choose.
- If the log cannot be loaded, nothing is shown rather than a partial history.
- In a partner's own log, the Public API's
targetUserIdfilter matches only the partner's own members, so it does not find an entry about a customer's user that was recorded there from an organization the partner manages. - Costfluent support sessions, and the exports and invoice downloads made in them that Costfluent support sessions lists, are recorded in Costfluent's own audit log and not shown here, in the export or in the Public API.