Authentication & Team Management

LogPulse supports multiple authentication methods to fit your organization's security requirements. Users can sign in with email and password, a work or school Microsoft account, Google or GitHub, or use API keys for programmatic access.

Access control is managed through a role-based system with four levels: Owner, Admin, Member, and Viewer. Organizations provide multi-tenant isolation for companies managing multiple teams or products.

Auth MethodUse CaseMFA Support
Email & PasswordIndividual accounts and small teamsAuthenticator app (TOTP) with backup codes, or a passkey
OAuth (Google)Teams using Google Workspace for identityDelegated to Google
OAuth (GitHub)Developer teams using GitHub for identityDelegated to GitHub
Microsoft (Entra ID)Organizations using Microsoft 365 / Entra ID for identityDelegated to your Entra tenant
SSO (SAML 2.0 / OIDC)Enterprise organizations with their own identity providerDelegated to your identity provider
API KeysProgrammatic access, CI/CD pipelines, agent configurationN/A (key-based)

Email & Password

Standard email and password authentication is available for all LogPulse accounts. New users create an account with an email address and password, then verify their email address via a confirmation link.

Password Requirements

Passwords must meet the following requirements:

RequirementDetails
Minimum length12 characters
Maximum length128 characters
Character classesAt least three of: lowercase letter, uppercase letter, number, special character (a space counts)
Password historyCannot reuse any of your last 5 passwords
ExpirationNone by default. An organization can set a maximum password age

Password Reset

To reset a forgotten password, click "Forgot password" on the login page. A password reset link is sent to the registered email address. The link expires after 1 hour and can only be used once.

Note
If you signed up with Microsoft, Google or GitHub, password reset is managed by your identity provider. Use the LogPulse password reset flow only for email/password accounts.

Social Login (OAuth)

LogPulse supports social login with Microsoft, Google and GitHub. Users can sign in with their existing work or school Microsoft account, or their Google or GitHub account, without needing to create a separate LogPulse password.

Google OAuth

Choose Continue with Google on the sign-in page. Personal Google accounts and Google Workspace accounts both work. Two-factor authentication is handled by Google.

GitHub OAuth

Choose Continue with GitHub on the sign-in page. This is convenient for developer teams that already use GitHub. Two-factor authentication is handled by GitHub.

Microsoft (Entra ID)

Sign in with Microsoft works for work and school accounts from any Microsoft Entra organization. Personal Microsoft accounts (outlook.com, hotmail.com, live.com) are not accepted. Multi-factor authentication and conditional access are applied by your own Microsoft environment, and disabling a user there stops their next sign-in to LogPulse.

An email address only counts when your organization has verified its domain in Entra. Without a verified domain, Microsoft sign-in cannot create an account or connect to an existing one. This protects against someone in another Microsoft environment putting your address on their own account.

Already have a LogPulse account with a password? Sign in as usual and connect Microsoft under Profile, Security. Only a Microsoft account with the same email address can be connected.

LogPulse only asks for the openid, profile and email permissions: signing you in and reading your name and email address. It does not read mail, files or your directory. On a dedicated environment, LogPulse can limit Microsoft sign-in to your own Entra tenant.

Many organizations do not let users approve apps themselves. A user then sees "Need admin approval" from Microsoft. An Entra administrator approves LogPulse once for the whole organization, in either of two ways:

  1. Sign in to LogPulse with Microsoft yourself and tick "Consent on behalf of your organization" on the permissions screen.
  2. Or in the Microsoft Entra admin center: Enterprise applications, LogPulse, Permissions, Grant admin consent. LogPulse appears there after the first sign-in attempt from your organization.

Sign-in errors

When Microsoft sign-in is refused, the sign-in page explains why. The code is in the address bar after error=.

CodeMeaningWhat to do
microsoft_email_unverifiedYour Microsoft account has no verified email address.An Entra administrator verifies the email domain in your Microsoft environment. Until then, sign in another way.
microsoft_tenant_not_allowedThis LogPulse environment does not accept your Microsoft organization.Ask your LogPulse administrator, or sign in another way.
microsoft_tenant_mismatchThe Microsoft account is not the one connected to your LogPulse account.Sign in with the Microsoft account you connected, or with your password.
microsoft_token_invalidThe sign-in from Microsoft could not be accepted.Try again. If it keeps happening, contact support.
account_not_linkedThis email address already has a LogPulse account that is not connected to Microsoft.Sign in the way you did before, then connect Microsoft under Profile, Security.

Single Sign-On (SSO)

Organizations on the Enterprise plan can connect their own identity provider over OIDC or SAML 2.0, verify their email domains, require single sign-on and create members on first sign-in.

Note
Single sign-on is part of the Enterprise plan and is being rolled out. Contact us to enable it for your organization.

Set up single sign-on →

API Keys

An API key is for sending logs. Agents, collectors and your own applications use it to call the ingest endpoints. An API key cannot search or change anything: for that you use a personal access token, which works with the permissions of your own account.

API key or personal access token

API keyPersonal access token
ForSending logsCalling the API as yourself: search, alerts, dashboards, configuration
Belongs toThe organizationYour account, in one organization
Can doIngest onlyWhat your role may do, limited to the scopes you pick

Creating and Managing Keys

Go to Configure → Sources → HTTP API and click New Key. Give the key a name. The key is shown once, right after you create it, and cannot be retrieved later. A key starts with lp_; the list only shows its first characters. Creating a key needs apiKeys:create, which owners and admins have.

To rotate a key, create a new one, switch your senders to it, and then delete the old one. Use a separate key per source or environment, so you can replace one without touching the others.

Revoking Keys

Delete a key on the same page. From that moment every request with the key is refused. A deleted key cannot be restored.

Warning
Deleting a key stops every sender that still uses it. Switch them to a new key first.

Team Management

Inviting Members

To invite a new team member, go to Tenant → Users, enter the email address and pick a role. The user receives an email invitation with a link to join the organization.

Invitations expire after 48 hours. If the user has not accepted the invitation, you can resend it from the pending invitations list.

Roles

Every member has one of four built-in roles. On top of that, Owners and Admins can create custom roles on the Roles page: a set of permissions plus the namespaces and indexes the role may see, assigned to members.

RoleDescription
OwnerFull access to all features including billing, organization settings, and member management. Each organization must have at least one Owner.
AdminCan manage alert rules, notification channels, dashboards, saved searches, and team members. Cannot access billing or delete the organization.
MemberCan search logs, write logs, create and update alerts, create and update dashboards, and manage pipelines. Cannot manage team settings, API keys, or delete alerts.
ViewerRead-only access to logs, dashboards, roles, and pipelines. Cannot create or modify any resources.

Role Permissions

The following table shows the complete permissions matrix for each role.

PermissionOwnerAdminMemberViewer
Read logsYesYesYesYes
Write logsYesYesYesNo
Delete / export logsYesYesNoNo
Read dashboardsYesYesYesYes
Create / update dashboardsYesYesYesNo
Delete dashboardsYesYesNoNo
Create / update alertsYesYesYesNo
Delete alertsYesYesNoNo
Create API keysYesYesNoNo
See API keysYesYesYesNo
Revoke API keysYesYesNoNo
Read rolesYesYesYesYes
Manage rolesYesYesNoNo
Manage pipelinesYesYesYesRead only
Invite / remove usersYesYesNoNo
Change member rolesYesYesNoNo
Manage organization settingsYesYesNoNo
Manage billingYesNoNoNo

Organizations

Creating Organizations

An organization is the top-level container for all LogPulse resources including logs, dashboards, alerts, and team members. When you sign up, a default organization is created automatically. You can create additional organizations from the organization switcher in the top navigation bar.

Each organization has its own billing, data storage, API keys, and team roster. Data is fully isolated between organizations -- there is no cross-organization log access. Each user can create up to 5 organizations. How many members an organization can have depends on the plan: 2 on Free, 3 on Starter, 10 on Pro and unlimited on Business.

Switching Organizations

If you belong to multiple organizations, use the organization switcher in the top-left corner of the dashboard to move between them. Your role may differ across organizations (for example, Owner in one and Member in another).

Organization-Level Settings

Organization settings are accessible to Owners and include:

SettingDescription
Organization nameDisplay name shown in the dashboard and notifications
Default timezoneTimezone used for dashboard displays and scheduled reports
Two-factor requirementRequire every member to set up two-factor authentication, and optionally a passkey for owners and admins
Idle timeoutSign members out after a period of inactivity
Maximum password ageAsk members to change their password after a number of days
Single Sign-OnSAML 2.0 or OIDC with verified email domains (Enterprise)
Billing planCurrent plan, usage, and payment method

Audit Log

The audit log records who did what in your organization. It is stored as logs in the index _audit, so you search it like any other data: index=_audit. It is kept for 180 days on every plan, regardless of your data retention.

SourcetypeWhat it holds
authenticationSecurity events: failed sign-ins, lockouts, sign-outs, SSO sign-ins and rejections, API keys created, deleted or refused
applicationChanges and actions: members, roles, API keys, alert rules, dashboards, pipelines, settings, AI use, raw log replays
web_accessEvery API request: method, path, status and response time

Every entry carries the user (id, email and name), the organization, the IP address and the user agent, and for a call with a personal access token the token id.

Example: who created API keys this month
index=_audit sourcetype=application "api_key_created" earliest=-30d
| table _time, attributes.user_email, attributes.key_name, attributes.ip_address

Session Management

LogPulse session management provides controls for session duration, concurrent sessions, and forced logout.

SettingDefaultConfigurable
Session duration7 daysFixed
Idle timeoutNonePer organization, in Settings
Session update age24 hoursSession refreshed daily
Cookie cache5 minutesCookie validation caching period
Concurrent sessionsUnlimitedNo limit enforced

Sessions are managed by Better Auth and expire after 7 days. The session token is refreshed every 24 hours. Cookie validation is cached for 5 minutes to reduce database lookups. When a session expires, the user is redirected to the login page. Secure cookies are used automatically in production environments.

Security Best Practices

Follow these recommendations to secure your LogPulse organization:

Require two-factor authentication. In the organization settings you can require every member to set up an authenticator app or a passkey before they can use LogPulse.

Rotate API keys regularly, and use a separate key for each source or environment, so a leaked key can be replaced without touching the rest.

Apply the principle of least privilege. Assign users the minimum role required for their responsibilities. Give a personal access token only the scopes it needs, and use roles to limit which indexes a member can search.

Review the audit log regularly. Set up a monthly review of audit log entries for unusual patterns: failed login attempts, API key creation from unexpected IPs, or role changes.

Use social login for teams. Microsoft, Google and GitHub sign-in centralize authentication and delegate credential management and MFA to the identity provider.

Tip
Start with a security baseline: require two-factor authentication, rotate API keys regularly, and apply least-privilege roles. These practices address the most common security risks.

Enterprise Access Controls (Roadmap)

The following enterprise access controls are planned for the Enterprise plan. These features provide the governance and auditability required for large organizations and regulated environments.

SCIM Provisioning

Note
SCIM provisioning is not available yet. Until then, you add members by invitation or on their first SSO sign-in, and remove them in Settings.

SCIM (System for Cross-domain Identity Management) will let your identity provider manage users in LogPulse. When a user is added or removed in your IdP (Okta, Entra ID, etc.), the change will be reflected in LogPulse without manual user management. Planned behavior:

OperationPlanned behavior
Create userUser account created with role from group mapping
Update userProfile attributes synced (name, email, groups)
Deactivate userAccount disabled; active sessions revoked; API keys suspended
Delete userAccount removed; owned resources transferred to org Owner

Just-in-Time Access

Just-in-Time (JIT) access provides time-bounded elevated permissions for incident response and debugging. Instead of permanently granting broad access, team members can request elevated roles that automatically expire after a configurable duration (30 minutes to 24 hours).

Note
JIT access is planned as an Enterprise feature. It integrates with the audit log to provide a complete trail of who had elevated access and when.

IP Allowlists

IP allowlists for the dashboard and API would restrict sign-in and API calls to specific IP addresses or CIDR ranges for the whole organization.

Note
Organization-wide IP allowlists are not available yet. IP lists do exist for pipeline webhooks: under Settings you keep named lists of addresses and ranges, and a pipeline webhook only accepts calls from the lists you attach to it.

Customer-Managed Keys

Customer-Managed Keys (CMK) allow you to control the encryption keys used to protect your log data at rest. With CMK you would provide your own key, and revoking it would make your data unreadable.

Note
CMK is planned for the Enterprise plan and not available yet.

Audit Log Export

Audit log export allows you to stream or batch-export all audit events to an external system for long-term retention, SIEM integration, or compliance archival. Exported events include full metadata: timestamp, actor, action, resource, IP address, and user agent.

A dedicated export is not available yet. On every plan, audit events are stored in the _audit index: search them with index=_audit, or pull them through the search API with a personal access token.

Export MethodStatus
Search and the search API (index=_audit)Available on every plan
CSV on-demand exportPlanned
JSON scheduled exportPlanned
Real-time SIEM streaming (webhook)Planned
S3 archival exportPlanned