User Management

Buildnote's authentication gives you secure access to your CI/CD pipeline monitoring. This page covers creating an account, signing in and managing users.

Authentication

Buildnote supports five authentication methods for creating and accessing your account, so you can use whichever fits your organisation's existing setup.

Authentication Options

You can sign in to Buildnote with GitHub, GitLab or Google (using OAuth), with an email address and password, or with SSO through your SAML identity provider.

GitHub, GitLab and Google sign-up uses a secure OAuth connection. Choose your provider, authorise the Buildnote application, and your account is created automatically. You then receive a confirmation email at your registered address.

To register with email and password, enter your email address and choose a password. Buildnote sends a verification link to your email address. Click the link to verify your email. Your account is then created and you receive a confirmation email.

SSO works with your organisation's existing SAML identity provider. A team administrator sets up the integration by entering the SSO URL, Entity ID, IdP Certificate, and the SAML attributes that hold user names and email addresses. Team members then sign in by entering their team name on the SSO login page, which sends them to your organisation's identity provider to authenticate.

Logging In

Sign in with the same method you used when you registered.

If you use GitHub, GitLab or Google, choose your provider and sign in on the provider's page. You are then sent back to Buildnote. If you use email, enter your registered email address and password. If you use SSO, enter your team name on the SSO login page, and you are sent to your organisation's identity provider to sign in.

If you forget your password for email sign-in, you can reset it. Enter your registered email address to receive a reset link, which is valid for 15 minutes. Click the link, choose a new password, and you can sign in again.

SSO Configuration

To set up SAML single sign-on, a team administrator enters the following:

• SSO URL: the endpoint your identity provider sends SAML responses to.
• Entity ID: a unique identifier for the service provider, such as urn:your-entity-id.
• IdP Certificate (PEM): the X.509 certificate from your identity provider, in PEM format, used to verify SAML responses.
• User Name SAML Attribute: the attribute that holds the user's display name, such as displayName.
• User Email SAML Attribute: the attribute that holds the user's email address, such as email.

Once this is set up, team members sign in through the SSO login page by entering their team name, which starts the SAML authentication flow.

User Management

Buildnote manages users through teams, with roles that control what each member can do.

Team Structure

When you sign up, you automatically become the Billing Manager of a new team with a generated name. You can start using Buildnote straight away and invite other people to your team.

You can belong to several teams, with a different role in each. This suits people who work across different projects or departments, and organisations with cross-functional teams or matrix management.

Each team is billed separately, which keeps costs apart between projects or departments. You can see exactly what each team costs, and each team can grow based on its own usage and needs.

Roles and Permissions

Buildnote has three roles that decide what a team member can do.

User Role can view the team's builds and events, see basic integration information and configure their own notifications. This role gives people the visibility they need without administrative access.

Admin Role has all User permissions and can also manage the team. Admins can invite and remove team members, install and configure integrations, add and remove API keys, rename and delete the team, and see basic plan information and usage statistics, including events ingested and submitters for the billing period.

Billing Manager Role has all Admin permissions and full control over billing. Billing Managers can upgrade or downgrade the plan, manage payment methods, view subscription information and access invoices.

Team Administration

Teams are central to how Buildnote works. Admins and Billing Managers control who belongs to a team, inviting colleagues by email and removing members when needed. They also manage team settings, including the integrations that connect Buildnote to your development workflows.

Buildnote works for small development teams and large organisations with complex requirements alike, and its user management keeps access secure and appropriate as you grow.

If your organisation needs an on-premises deployment or enterprise features beyond standard SSO, Buildnote offers an Enterprise plan tailored to your organisation's needs.