Labor0 Docs

Knowledge sources

Beta: Knowledge sources are L0 Nexus capabilities available for evaluation and may change as supported sources expand.

Connect a verified knowledge source when repository context alone is not enough. The source families below are currently usable in Labor0.

Supported source families

Source familyWhat Labor0 can readSetup method
GitHub repository filesRepository filesGitHub App
GitHub issuesIssuesGitHub App
GitHub discussionsDiscussionsGitHub App
Public website crawlPages published at a public URLPublic URL
R2-compatible storageObjects and object listingsManual credential
GCS-compatible storageObjects and object listingsManual credential
Google DriveDrive files and exports available to the selected accountOAuth
DropboxFiles and folders available to the selected accountOAuth
Slack knowledge contentConversation content and configured file metadataOAuth
LinearIssues, projects, comments, and document-like contentOAuth

Notion, OneDrive, and AFFiNE are unavailable for app setup. Labor0 does not offer a connector or source setup path for them. Existing Notion and OneDrive records remain visible in the app for status review and cleanup.

Before you begin

Write down the question the source should answer and choose the smallest useful scope. Confirm the source owner can authorize access and review indexing results. A public website must be reachable without sign-in; storage credentials should be limited to the intended bucket or path.

Choose a source type

Open L0 Nexus > Sources, then select New source. The chooser tells you whether the source requires an active connector.

Provider authorization

Labor0 requests only the read capabilities needed for the selected source. These are the public permission names used by the provider setup; they do not grant broader access than the source row describes.

SourceRequested authorization
GitHub repository files, issues, and discussionsA read-capable GitHub App with metadata, contents, issues, and discussions
Google Drivehttps://www.googleapis.com/auth/drive.readonly, with openid, email, and profile identity scopes
Dropboxfiles.metadata.read, files.content.read, and account_info.read
Slack knowledge contentchannels:history, channels:read, groups:history, groups:read, files:read, and users:read
Linearread
Public website crawlNo OAuth scopes; the public URL is the authorization boundary
R2-compatible and GCS-compatible storageNo OAuth scopes; a manual credential flow authorizes the configured storage access

Procedure

  1. Open L0 Nexus > Connectors when the selected source says that a connector is required.
  2. Select New connector, choose the provider, and complete its protected GitHub App, OAuth, or manual-credential handoff.
  3. Return to Sources, select New source, and choose the source type.
  4. Complete only the fields shown for that type. Select Create source after every required field is present.
  5. Open Indexing and wait for completion. A ready source shows its indexed document count; a failed source offers Retry sync or Resync now when self-service recovery is available.

Example: public handbook

This example indexes a public documentation site and requires no connector.

FieldExample input
Source typeWebsite crawl
NamePublic product handbook
ConnectorNo connector needed
Website URLhttps://docs.example.com/handbook
Include subdomainsNo

Website crawl source form filled with a privacy-safe example and ready to create.

Expected result

After Create source, the dialog closes and the Sources count increases. In Indexing, a successful run shows the source name, indexed document count, and completion time. Do not use the source in Graph Chat until indexing has completed.

Labor0 access boundary

Workspace Viewer and above may view source and connector state, run permitted read-only knowledge and data access, and view messenger bridge state. Workspace Operator and above may use explicitly read-write data bindings. Workspace Admin and above may create, change, archive, reconnect, or disconnect knowledge sources and connectors, and manage messenger installations and channel-to-project bindings.

Provider-side organization or account approval may still be required. Linking a provider actor and binding a project channel do not bypass Labor0 membership or project access.

If indexing does not finish

Symptom: the source remains unavailable. Likely cause: authorization changed, the source is too broad, or indexing is still running. Safe recovery: read the app status, reconnect or narrow the source there, and wait for a fresh status.