User Management
Buildnote authentication system provides secure access to your CI/CD pipeline monitoring tools. This documentation covers account creation, login procedures, and user management capabilities.
Authentication
Buildnote supports five authentication methods for creating and accessing your account, giving you flexibility based on your organization's existing workflows.
Authentication Options
You can authenticate with Buildnote using GitHub, GitLab, or Google OAuth integration, traditional email and password credentials, or SSO via SAML integration with your Identity Provider.
GitHub, GitLab, and Google authentication work through secure OAuth connections. Select your provider, authorize the Buildnote application, and the system creates your account automatically. You'll receive a confirmation email at your registered address.
Email and password registration requires entering your email and creating a password. Buildnote sends a verification link to your email address. Click the link to verify your email, create your account, and receive confirmation.
SSO authentication integrates with your organization's existing SAML-based Identity Provider. Team administrators configure the integration by providing the SSO URL, Entity ID, IdP Certificate, and SAML attribute mappings for usernames and email addresses. Team members access Buildnote by entering their team name on the SSO login page, which redirects to your organization's Identity Provider for authentication.
Logging In
Use the same authentication method you chose during registration to access Buildnote.
GitHub, GitLab, and Google users select their provider and authenticate on the provider's page before redirecting back to Buildnote. Email users enter their registered email and password directly. SSO users enter their team name on the SSO login page, which redirects them to their organization's Identity Provider for authentication.
If you forget your email authentication password, Buildnote provides password recovery. Enter your registered email to receive a recovery link valid for 15 minutes. Click the link to create a new password and regain account access.
SSO Configuration
Team administrators configure SAML Single Sign-On integration by providing the SSO URL (endpoint where your Identity Provider sends SAML responses), Entity ID (unique service provider identifier like urn:your-entity-id), IdP Certificate in PEM format (X.509 certificate from your Identity Provider to verify SAML responses), User Name SAML Attribute (attribute containing user display names such as displayName), and User Email SAML Attribute (attribute containing user email addresses such as email).
After configuration, team members access the service through the SSO login interface by entering their team name, which initiates the SAML authentication flow.
User Management
Buildnote uses team-based user management with role-based permissions to control access across your engineering organization.
Team Structure
New Buildnote users automatically become Billing Manager of a newly created team with a system-generated name. This setup provides immediate access to Buildnote features while allowing you to invite additional team members.
The platform supports membership in multiple teams, enabling individuals to contribute to different projects or departments with appropriate access levels for each context. This works particularly well for organizations with cross-functional teams or matrix management structures.
Each team has separate billing, providing financial isolation between projects or departments. This structure allows precise cost allocation and independent scaling based on each team's usage patterns and requirements.
Roles and Permissions
Buildnote provides three roles that determine team member capabilities.
User Role grants basic access to view builds and events for their team, access basic integration information, and configure personal notifications. This role provides necessary visibility without administrative capabilities.
Admin Role includes all User permissions plus team management capabilities. Admins can invite and remove team members, install and configure integrations, add and remove API keys, rename teams, delete teams, and view basic plan information and usage statistics including events ingested and submitters for the billing period.
Billing Manager Role includes all Admin permissions plus complete financial control. Billing Managers can upgrade or downgrade plans, manage payment methods, view subscription information, and access invoices.
Team Administration
Team management is central to Buildnote's functionality. Admins and Billing Managers control team membership by inviting colleagues via email and removing members when necessary. You maintain oversight of team settings including integration configurations that connect Buildnote to your development workflows.
Buildnote scales from small development teams to enterprise organizations with complex requirements. The platform's user management capabilities maintain security and appropriate access control throughout your organization.
For organizations requiring on-premises deployment or additional enterprise features beyond standard SSO integration, Buildnote offers Enterprise plans that provide exceptional value and closer alignment with your specific organizational needs.