Using The App

The web app at app.buildnote.io is where you read your collected events. It shows pipeline timelines, test history and dashboards, and it has an assistant that answers questions about your data in plain English.

This section walks through the app one screen at a time. Start here to learn how navigation, teams and the time range work, then go to the page that matches what you want to do.

Signing in and choosing a team

You can sign in with GitHub, GitLab, Google, email and password, or your organisation's SAML provider. See User Management for the full authentication flow.

Everything in the app belongs to a team. When you create your account, you become the Billing Manager of a new team, and you can join as many other teams as you need. Each team has its own data, integrations, members and bill.

Use the account menu at the bottom of the left navigation to switch teams. It lists each team with the role you hold there, and Add team creates a new one. The team identifier is part of every URL, so any link you share opens in the right team.

The left navigation

The sidebar has five destinations. Which ones you see depends on your role and your team's plan. To make room for a wide table or a dashboard, use the panel icon next to the page title to collapse the navigation to a row of icons.

Builds is the default view and the starting point for exploring collected events, from organisations down to a single test case. Go here when something fails and you want to know why.

Dashboards holds the boards your team builds from saved queries, so the numbers you check regularly are always in one place.

AI Insights is the assistant. Ask a question in plain English and it answers with charts, dashboards, files or a build timeline shown in the conversation.

Query is a query editor for when you know exactly what you want and prefer to write the query yourself.

Settings holds team configuration: general, users, security, integrations, notifications and billing.

The time range

Most pages have a time-range control in the header. It applies to everything the page loads, including build lists, stability graphs, event tables, dashboard widgets and query results.

You can choose a preset (Today, This week, This month, This year, rolling windows from Past 8 hours to Past year, or Max) or pick your own start and end. The default is the past 7 days.

The selected range is stored in the URL, so when you paste a link into a pull request or a chat message, the other person sees exactly what you saw. The same applies to most filters, such as branch, status and event type, and to the file or tab you had open.

The assistant is the only page without a time filter. It works out the period from your question.

Breadcrumbs and bookmarks

Every detail page shows breadcrumbs at the top that trace the path from team to organisation, project, module, build and event. You can click any level to go back to it.

Organisations, projects and modules have a bookmark button. Bookmarking one adds it to a list in the left navigation, so the modules you check most often are one click away.

What your role and plan allow

There are three roles. User members can read builds and events, use dashboards and the query editor, and configure notifications. Admin members can also manage members, integrations and API keys, rename or delete the team, and see plan and usage details. Billing Manager members can also change the plan and manage payment methods, subscription details and invoices.

Your plan controls which features you can use as well as how much data you can collect. On the Free plan, events arrive only through a version control integration such as the GitHub app, events are kept for 14 days, and you can collect up to 25,000 events a day. The query editor, dashboards, API keys, notifications and AI features are not included. Pro and Enterprise plans include all of these, keep events for 400 days and raise the limit to one million events a day.

Where to next

• Exploring Builds covers the event explorer, from the list of organisations down to a single failing test and the files its build collected.
• AI Insights covers the assistant and the failure summaries shown on events.
• Dashboards explains how to build boards.
• Query explains the query editor.
• Guardrails covers the rules your pipeline runs and the results they record on a build.
• Team Settings covers members, integrations, notifications and keys.