# Company knowledge base for employee training, with an owner for every source

Give useful work an approved source. A company knowledge base for employee training holds the documents, links and recordings your lessons are built from, each with an owner and a version. In Elvina this is Company Knowledge, available now, where approved sources sit before Creation Studio turns them into training; Google Drive and Notion connect in your workspace with our team after the first step. Dropbox and SharePoint are planned, not available today.

Updated October 26, 2026

## Who this is for, and when

A knowledge owner, an operations director or a compliance lead who is tired of training material that quietly drifts away from the procedure it was built on. The test comes with a policy change that has to reach the field this month. The hard part is finding every lesson that depends on the old version.

## How it works in Elvina

When an approved SOP changes, the intended workflow identifies related lessons and job aids, then proposes targeted updates with the old version still traceable. EPA's guidance on writing standard operating procedures recommends a master list of all SOPs that records each one's version number, date of issuance, author and status, with any history of past versions.

- Add owned documents, permitted URLs and connected Google Drive or Notion sources to Company Knowledge, each with an owner and a version.
- Each lesson, job aid and quiz cites the source version it came from; listing them automatically when a source changes is planned, not available today.
- Your team regenerates those artifacts in Creation Studio and approves them, and the old version stays traceable.
- A person reviews the proposals in the Web workspace before updated content reaches the Learning Platform.

What goes into Company Knowledge, what happens to it and what comes out.

| Input | What happens | Output |
|---|---|---|
| Owned documents, permitted URLs, connected Google Drive or Notion sources | Each source is added deliberately to Company Knowledge | A source with an owner and a version; Company Knowledge is available now |
| An approved source | Creation Studio turns it into training | Lessons, job aids and quizzes that cite the source |
| A new version of a source | The owner records the new version | Flagging the lessons, job aids and quizzes that depend on it is planned, not available today |
| Affected lessons, job aids and quizzes | Your team regenerates them in Creation Studio; a person reviews them in the Web workspace | Approved updates reach the Learning Platform; the old version stays traceable |

## A worked example

A fictional pediatric clinic network stores its vaccine storage procedure in Company Knowledge as version 5, owned by the nursing director. When version 6 changes the temperature log interval, the network needs every artifact that mentions the interval updated without rewriting the whole curriculum.

- Company Knowledge shows version 6 with the director as owner, and the team finds three artifacts citing version 5: one lesson, one job aid and one quiz question.
- The team regenerates those three in Creation Studio from version 6, so each one now cites the new interval.
- The director approves two, rewrites the quiz question herself, and the Learning Platform shows the new content version to learners.

## What to check before relying on it

Company Knowledge is not model-weight training, a CRM or blanket access to company files. Freshness and permissions must be verified per source.

- Every source in Company Knowledge shows an owner and a version.
- Your team can tell which artifacts cite an older source version; an automatic list of them is planned, not available today.
- Superseded versions remain visible for audit.

## Where a person stays in charge

Company Knowledge is not model training, a CRM or blanket access to company files. Each source is added deliberately, and freshness and permissions are verified per source by its owner. Google Drive and Notion connect in your workspace with our team after the first step; other connectors, such as Dropbox and SharePoint, are planned, not available today. Your team regenerates affected material with Elvina; a person decides what changes and when it reaches learners.

## Questions people ask

**Q:** Does adding a document train the model on our data?

Documents become approved sources that drafts cite. Model-training terms depend on your plan and applicable agreement. See the ContentBuilder Privacy Policy and your workspace agreement for data use, service providers and available opt-out choices.

**Q:** How do we know a source is current?

The owner and version are recorded on each source. Your owners keep them current; flagging dependent artifacts when a version changes is planned, not available today, so today your team regenerates them after a change.

**Q:** What belongs in a company knowledge base for employee training?

Owned documents, permitted URLs and connected Google Drive or Notion sources, each added deliberately with an owner and a version. Superseded versions remain visible for audit.

## Sources

Public sources, checked on the date shown.

- EPA's Guidance for Preparing Standard Operating Procedures (EPA QA/G-6), section 2.6: “The organization should maintain a master list of all SOPs. This file or database should indicate the SOP number, version number, date of issuance, title, author, status, organizational division, branch, section, and any historical information regarding past versions.” Source: https://www.epa.gov/sites/default/files/2015-06/documents/g6-final.pdf (checked 2026-10-26).

No launch date is committed for planned features.