LoreGraph product docs

Integrations

Summary

Integrations connect LoreGraph to billing, authentication, email, and planned knowledge-source or workflow systems.

Who this is for

Workspace admins
IT administrators
Security reviewers

Before you start

Confirm which integrations are available in your workspace.
Review permissions before connecting external systems.
Use planned integrations as roadmap signals, not current availability.

Concepts

Current visible integrations include Stripe billing, Google/Firebase authentication and storage, and email delivery for invitations or notifications where enabled.

Planned integrations include Google Drive, Notion, SharePoint, Confluence, Slack, LMS export, SCIM, and SSO depending on product status and plan.

Integration security should explain connection permissions, what data is imported, how to disconnect, and how imported data is used.

Steps

Review current integrations in settings or billing.
Connect only the systems required for the rollout.
Grant the narrowest permissions available.
Import or sync only approved training materials.
Disconnect integrations that are no longer needed.
Review planned integrations with LoreGraph before promising them to stakeholders.

Settings reference

Setting	What it does	Recommended default
Stripe billing	Manages plan checkout, payment, and billing portal flows.	Use for paid workspace plans.
Google/Firebase auth	Supports account sign-in and workspace access.	Use standard workspace authentication.
Email delivery	Sends invites, notifications, or support messages where enabled.	Use for learner rollout communication.
Knowledge-source imports	Planned connectors for Drive, Notion, SharePoint, Confluence, and URLs.	Treat as planned until enabled.

Example

A Business workspace uses Stripe for billing, Firebase-backed sign-in, and email invites today. The team lists SharePoint import as a planned future workflow rather than a current dependency.

Common mistakes

Promising planned integrations as live features.
Granting broad connection permissions without a clear import need.
Forgetting to document how imported data is used.
Skipping disconnect steps in rollout documentation.