Integrations
Paměť connects to where your knowledge already lives.
Email, documents, chats, CRM, shared drives. Paměť is designed to read from the systems your company runs on today, within the permissions you already have, rather than asking anyone to move their work somewhere new.
- Read-only by design
- Within existing permissions
- Indexed in place
Eight categories
Eight places your company already keeps its memory.
Most of what a company knows sits in a handful of systems: the mailboxes, the document libraries, the chat channels, the CRM, and the drive nobody has tidied since the office move. Paměť is designed to reach into each of them and read what is there.
Paměť · source map
- EmailExample
- Microsoft 365Example
- TeamsExample
- Google WorkspaceExample
- SlackPlanned
- CRMExample
- Shared drivesExample
- Knowledge basesPlanned
Illustrative — categories, not live connectors
- Example
- a category Paměť is designed around
- Planned
- intended, not yet offered
Availability depends on your deployment
Where the knowledge lives
What each system remembers.
Every category holds a different slice of the company's memory. Email holds the promise, the CRM holds the outcome, and the document library holds the quotation both refer to. Paměť is designed to read across them, so the answer does not depend on which one someone thought to search.
Labels are indicative. Example integration: a category Paměť is designed around. Planned: intended, not yet offered.
- Example integration
Correspondence
Email
Quotations sent, objections raised, promises made. Most of a client relationship lives in threads.
- Example integration
Documents & suite
Microsoft 365
The proposals, spreadsheets and decks a company produces, and the versions in between.
- Example integration
Mail & calendar
Outlook
Who wrote to whom, what was agreed in the reply, and the meeting invitation that dates it.
- Example integration
Chats & meetings
Microsoft Teams
Project channels, decisions taken in a thread, and the meeting nobody wrote up afterwards.
- Example integration
Document libraries
SharePoint
Project sites, contract folders and the quotation library, with the structure that explains them.
- Example integration
Drive, Docs & Gmail
Google Workspace
Shared drives, working documents and mail for companies that run on Google.
- Planned
Channels & threads
Slack
Client and project channels where the reasoning behind a decision was typed out as it happened.
- Example integration
Accounts & opportunities
CRM
Deal stages, loss reasons and account notes: the structured record beside the unstructured story.
- Planned
Controlled documents
Document management
Approved revisions, sign-offs and the history of a controlled document in a dedicated DMS.
- Planned
Tasks & tickets
Project management
Boards, tickets and status updates that show what was done, by whom, and where it slipped.
- Example integration
File servers & folders
Shared drives
Network drives and project folders, including the final-final version everyone actually uses.
- Planned
Wikis & handbooks
Internal knowledge bases
Process pages, handbooks and wikis: the knowledge someone once took the time to write down.
How connectors work
Read-only. Permission-scoped. Left in place.
A connector is the part of Paměť that reads from one of your systems. It is designed to do as little as possible: read, understand, link, and leave everything where it found it.
- 01
Read-only access
Connectors are designed to read, not write: nothing in the source system is meant to be edited, renamed, moved or deleted. Depending on configuration, the account a connector uses can be limited to read permissions only.
- 02
Scoped to existing permissions
Access is designed to follow the rights your systems already enforce. A person is meant to receive answers only from records they could open themselves. How that mapping works depends on the source system and on your deployment configuration.
- 03
Indexed in place
Records stay in the system that owns them. Paměť builds an index and a map of the links between records; it is designed not to become a second file server or a parallel archive.
- 04
Nothing moved
There is no migration project and no cut-over weekend. Connectors can be added one at a time, starting with the sources that hold the most client and project history, and are designed to be removed again without touching the source.
- Access
- Read-onlyNo write scope requested
- Scope
- Existing permissionsMirrored from the source system
- Location
- Indexed in placeRecords stay in SharePoint and Outlook
- Languages
- CS · SK · ENDetected per record
What it reads
- Documents
- Chats
- Meeting notes
Out of scope by design
- Write to the source
- Move or rename files
- Change permissions
- Copy records into a new archive
Illustrative configuration — options depend on deployment
An illustrative connector record for one Microsoft 365 tenant in the demo workspace. The fields show the design intent; the options available to you depend on your systems and deployment.
Talk to us about your systems
Your systems are not on the list?
Most companies run on a mixture: one suite for mail and documents, a CRM from another vendor, a project tool the delivery team chose, and a shared drive older than all of them. Tell us what you use. We will say plainly what Paměť is designed to read today, what would take work, and what we would not recommend.
What helps us answer quickly
- 01
Which systems hold the history
Mail, documents, chat, CRM, drives, and anything older that still holds client or project records.
- 02
Roughly how many people would ask
A team of ten and a company of four hundred call for different configurations.
- 03
Which languages the records are in
Czech, Slovak, English, or a mixture within the same thread.
Boundaries
What Paměť does not do.
Compatibility is also about what stays the same. Three things Paměť leaves alone on purpose.
It does not replace your tools
Your mail client, your CRM and your document library keep doing their jobs. Nobody is asked to give up a system they rely on.
Instead · Paměť sits beside them as the place to ask.
It does not move your files
Records stay in the systems that own them, under the permissions those systems enforce. Paměť is designed to index in place, not to relocate anything into a new archive.
Instead · An index and a map of the links, nothing more.
It does not require a new workspace
There is no new tool for the whole company to adopt, and no content for anyone to migrate before the first useful answer.
Instead · One question, answered from what already exists.
Common questions
Questions we hear about compatibility.
Short answers to the questions that come up first. For anything specific to your environment, ask our team.
- We run Microsoft 365 and a CRM from another vendor. Is that a problem?
- No. The point of a memory layer is to connect systems that do not talk to each other. Each source gets its own connector; the links between a quotation, an email and a CRM note are made in Paměť, not in the source systems.
- Do we have to connect everything at once?
- No. Most companies are best served by starting with the two or three sources that hold the most client and project history, usually mail and a document library, and adding others once the first answers have proved useful.
- Does anyone have to change how they file things?
- No. Connectors read what is already there. Folder structures, naming conventions and half-finished tagging schemes are inputs, not prerequisites, and nobody has to maintain a wiki for the memory to work.
- What about systems we retired but still hold archives from?
- Old archives are often the most valuable source, because they hold the history nobody remembers. Whether a particular archive can be read depends on its format and where it sits, so this is one to ask our team about.
- Will employees need a new login?
- Paměť is designed to work with the identity your company already uses, so that permissions can be mirrored consistently rather than managed twice. The exact options depend on your deployment configuration.
- Can it read on-premises systems?
- Deployment options depend on your environment. On-premises and hybrid sources are a conversation about architecture as much as about connectors, and we would rather have it early. Ask our team.
Tell us what you run on.
Book a demo and bring the list of your systems. We will show what Paměť is designed to read from each of them, and say plainly where it is not there yet.
- EU data storage
- GDPR-conscious
- Access-controlled
- Enterprise-ready