Using the app

Lookout is organized around organizations (billing and membership), projects (where events land), and optional teams (who can see which projects). This guide follows the same navigation you see after signing in.

Account and profile

Register or accept an invitation, then verify your email when your environment requires it. Open Profile from the header menu to change your name, password, theme, and locale.

Under Profile you can create personal access tokens. Those tokens authenticate the REST API — they are separate from a project’s ingest API key.

Organizations

The Organizations page lists every org you belong to with your role (owner, admin, or member). Owners and admins can invite people, manage enterprise settings (allowed domains, SSO records), and export org data where billing allows.

Pick an organization from the switcher (or create one) to set your “current” org. Projects, teams, and billing are always scoped to that org unless noted.

Teams and access

Teams belong to an organization. A project with no linked teams is visible to all org members. When you attach one or more teams to a project, only members of those teams (plus owners and admins) see that project and its issues.

Use the Teams page to create teams and assign members. When creating a project via the REST API you can pass team IDs to apply the same rules.

Projects

Each project has its own ingest API key, slug, and settings. Open a project to see the issue list (grouped by fingerprint), search, filters, and links to Crons, Releases, Profiles, and Settings.

Project Settings covers the display name, API key (view prefix, rotate), Git repository hints for source links, third-party shortcuts (GitHub issues, Jira, GitLab, Linear), alert rules, outbound webhooks and delivery log, custom fingerprinting rules, and deletion.

Dashboard

The dashboard summarizes recent activity for your current organization. Use it as a home base before drilling into a specific project.

Issues list and search

Issues are groups of occurrences sharing a fingerprint (or a single event when no fingerprint exists). Use status and time range controls, then refine with the search box.

Search supports free text plus structured tokens such as level:error, env:production, release:, class:ExceptionName, and date or occurrence-count filters. The project UI shows a compact cheat sheet above the list.

The same search string is accepted by the grouped-errors REST endpoint’s search query parameter; see REST API.

Event detail

Opening an issue shows the latest occurrence by default; you can browse the timeline, stack trace, context, breadcrumbs, and tracing tabs when your SDK sends those fields.

Resolve, ignore, reopen, and snooze apply to the whole fingerprinted group when a fingerprint exists; otherwise they apply to that single event. Comments can attach to the issue thread or to a one-off event, depending on grouping.

Alerts and webhooks

Alert rules (email or Slack) live in project settings and evaluate on a schedule against error volume in a time window.

Outbound webhooks notify your HTTP endpoint when a new issue appears. Verify signatures with the signing secret documented in project settings and in the Ingest API.

Billing

Billing is per organization: the Billing page always reflects the organization currently selected in the header (plan, usage, Stripe checkout, and customer portal). Switch organizations there to work with another org’s subscription—each org is billed separately.

Organization owners manage plans in Billing when Stripe is configured. Organization settings (per organization) holds data export, ingest IP allowlist, and error digest email. Project limits and ingest quotas depend on your plan.

Sending data in

Point your applications at POST https://lookout.dply.io/api/ingest with the project API key. Field-level detail lives in the Ingest API and Protocol overview.