Authentication Methods
- OAuth
- API Key
- Service Account
OAuth is the preferred method for integrations that support it. LowerPlane redirects you to the provider’s authorization page, where you grant access. Tokens are stored securely and refreshed automatically.Supported by: Google Workspace, Okta, GitHub, GitLab, Slack, Jira, Asana, BambooHR, and many others.
Select the integration
Navigate to Integrations and find the tool you want to connect. Click Connect.
Provide instance details (if required)
Some integrations require an instance URL, tenant ID, or account identifier before OAuth can begin. Enter these when prompted.
Authorize in the provider
You will be redirected to the provider’s login and authorization page. Sign in and grant the requested permissions.
Configuring Sync Frequency
After connecting an integration, you can configure how frequently LowerPlane syncs data.| Frequency | Interval | Best For |
|---|---|---|
| Hourly | Every 60 minutes | Identity providers, critical security tools |
| Daily | Once per day | Cloud providers, version control, most tools |
| Weekly | Once per week | HR systems, background checks |
| Manual | On-demand only | Audit preparation, spot checks |
- Go to Integrations and click on the connected integration.
- Select the desired frequency from the Sync Frequency dropdown.
- Save your changes. The next sync will follow the new schedule.
Changing the sync frequency does not trigger an immediate sync. Click Sync Now if you need fresh data right away.
Managing Connected Integrations
Triggering a Manual Sync
Click Sync Now on any connected integration to start an immediate data sync. This is useful before an audit or after making configuration changes in the connected tool.Refreshing OAuth Tokens
If an OAuth integration shows a token expiration warning, click Refresh Tokens to obtain new credentials without disconnecting and reconnecting.Revoking Access
To disconnect an integration:- Click on the integration in your integrations list.
- Select Disconnect or Revoke Access.
- Confirm the action.
Troubleshooting Connection Issues
OAuth redirect fails or shows a blank page
OAuth redirect fails or shows a blank page
Ensure your browser allows pop-ups from LowerPlane. Some ad blockers interfere with OAuth redirects. Try disabling extensions or using an incognito window.
API key is rejected
API key is rejected
Verify that the API key has not expired and that it has the required read permissions. Some providers generate keys that are scoped to specific environments or regions — make sure you are using the correct one.
Integration shows Error status after initial sync
Integration shows Error status after initial sync
Check the error message displayed on the integration detail page. Common causes include insufficient permissions, rate limiting by the provider, or network connectivity issues.
Sync completes but no evidence appears
Sync completes but no evidence appears
Verify that the connected account has data in the expected scope. For example, an AWS integration scoped to a single region will not collect resources from other regions. Expand the scope or connect additional regions.
Token expired or revoked externally
Token expired or revoked externally
If someone revokes the OAuth token from the provider’s side, the integration will enter an error state. Reconnect the integration by clicking Reconnect and completing the OAuth flow again.
Permissions Reference
Each integration requires specific permissions in the provider. LowerPlane follows the principle of least privilege.| Provider Type | Typical Permissions Required |
|---|---|
| Cloud Providers | Read-only access to security configurations, IAM policies, and resource inventories |
| Identity Providers | Read access to users, groups, MFA status, and authentication logs |
| Security Tools | Read access to findings, vulnerabilities, and scan results |
| HR Systems | Read access to employee directory (name, email, department, status) |
| Version Control | Read access to repositories, branch protection rules, and pull request reviews |
LowerPlane never modifies configurations in your connected tools. All integrations operate in read-only mode unless you explicitly enable write actions for specific use cases.