ActivityLog

ActivityLog — User Guide

Everything you need to sign up, mint a token, wire your first system into ActivityLog, and bring in Microsoft 365, Azure DevOps, Claude Code, or your own services.

This guide is written for the developer or operator at a customer who has signed up (or is evaluating) ActivityLog. For the marketing pitch see ../Executive-Overview.md; for the formal API contract see ../API-Reference.md; for internal architecture see ../Architecture.md.

Where to start

If you want to... Read this
Send your first message in under five minutes 00-quickstart.md
Understand the account / tenant / system / user model 10-setup-account-tenant.md
Mint, rotate, or revoke a system token 20-setup-system-tokens.md
Invite teammates and assign roles 30-invites-and-team.md
Set up two-factor authentication (TOTP) 40-totp-setup.md

Sending data into ActivityLog

Path When to use it Doc
Native HTTPS — POST /messages Your own application code 50-ingest-native.md
OpenTelemetry (OTLP/HTTP) You already have OTel instrumentation 51-ingest-otlp.md
Langfuse-compatible You use the Langfuse SDK for LLM tracing 52-ingest-langfuse.md
Webhook receivers (ADO / Event Grid / GitHub) You can configure your source to POST 53-ingest-webhooks.md

Not sure which? Start with 50-ingest-native.md — it has the decision tree.

Querying and exporting

Doc Topic
60-query-api.md POST /activity/search (faceted, cross-source), GET /messages, filters, aggregates, timelines, detail, exports

Pre-built integrations

Source Doc
Microsoft 365 (Teams + Outlook + Entra ID + SharePoint) 70-integrations-m365.md
Azure DevOps 71-integrations-azure-devops.md
Claude Code (OpenTelemetry) 72-integrations-claude-code.md
Umbraco 73-integrations-umbraco.md

Reports

Doc Topic
90-reports.md The portal report pages (My week, Timesheet, Change control, AI usage, Compliance, Microsoft 365, Knowledge base, SIEM, Activity), how they find your systems, and the facets behind them

Administration

Doc Topic
80-admin-portal.md Admin-portal capabilities for operators (Fyin staff)

Conventions used in this guide

  • Public base URL: https://api.activitylog.com for the API; https://activitylog.com/portal/ for the customer portal; https://activitylog.com/portal/staff/ for the staff (operator) pages. Staging is https://activitylog-api.betawebserver.com / https://activitylog.betawebserver.com/portal/.
  • Tokens in examples are placeholders like al_REPLACE_WITH_YOUR_TOKEN. Never copy these literally — mint your own in the portal.
  • Tier numbers quoted in tables come directly from ../Pricing.md. If you spot a drift, that doc is the source of truth.
  • Status labels — features marked Live ship today; Coming soon is on the active roadmap; Deferred is acknowledged but not scheduled.

Conventions and tone

  • One concept per heading. If a paragraph is long, it's wrong.
  • Every command appears in a code block, even one-liners — so you can copy-paste safely.
  • Cross-links use relative paths so this folder is portable.

Found a problem?

  • API reference drift: file an issue against ../API-Reference.md.
  • Pricing-page drift: same, against ../Pricing.md.
  • Anything in this guide: open a ticket referencing the file by name.