Account And Settings

This page covers the settings a Knowlume user can control from the web app.

For the main source-to-export workflow, see Quickstart.

Projects

Projects keep sources, selections, and exports organized.

Use a separate project when work has a clear boundary: a research topic, client, course, product area, or report. Use Inbox for one-off material.

Before adding a source, check that the current project is the one where you want the fragments and exports to appear.

Useful project boundaries include "course notes", "competitor research", "news monitoring", "client discovery", or "personal knowledge base". Smaller projects make filtering and later export easier.

Credits And Usage

Depending on your plan, processing sources and exporting selected fragments may consume credits or plan allowance.

Practical habits:

  • start with a small number of sources until you understand the workflow;
  • filter before exporting;
  • export only fragments you expect to reuse;
  • avoid sending very large sources just to see what happens.

Copying a fragment for quick personal use can be useful when you do not need a full export.

Export Preferences

Markdown exports are built from the fragments you select.

Recommended flow:

  1. Review fragments in the source.
  2. Apply filters if the source produced many fragments.
  3. Select the fragments worth keeping.
  4. Save the selection.
  5. Export Markdown.

If your browser supports folder selection, you can configure a project export folder. Otherwise, use the normal download flow.

Integration Webhook

Use an Integration Webhook when another system should receive completed Markdown exports automatically.

Typical destinations include:

  • a notes app automation;
  • an internal workflow tool;
  • a content pipeline;
  • a personal archive.

The webhook is used for export delivery. It is not required for normal downloads.

API Keys

API keys are for automating Knowlume from scripts, agents, or other tools.

Create an API key only when you need an external client to submit sources, read status, fetch fragments, or request exports. Store the key like a password and rotate it if it is exposed.

For examples, see Integrations And API.

Practical Defaults

For most users:

  • keep sources grouped by project;
  • review fragments before exporting;
  • start filters at 5 or higher on each score;
  • raise originality when sources feel generic;
  • use file download first;
  • add webhook or API automation only after the manual workflow is clear.