Documents
Cora PPM End-User Guide
A working guide to the Documents feature in Cora PPM — what it is, why teams rely on it, how manufacture-to-order, pharma, capital projects, and government-contracting customers typically configure it, and step-by-step instructions for everyday use.
Quick Facts
Lives At | Project, Company, Task, Risk, Issue, Register & Benefit level |
|---|---|
Version Control | Check-out / check-in, toggled per project type |
On Every Upload | Automatic virus scan |
Storage | Database or File System — admin-configured |
1. What is Documents?
Documents isn't one screen — it's a repository capability that shows up everywhere a project needs supporting files. The same document engine appears in several places, and it behaves identically wherever you meet it — same categories, same check-out rules, same custom fields:
Project Documents — the main tab on a project, for anything tied to that specific project.
Company Documents — an organisation-wide area for files not tied to any one project, such as templates or standard specifications reused across many jobs.
Task Documents — a lighter document list inside a task on the Task Manager / Gantt.
Linked-Entity Documents — Risks, Issues, Cost Book Estimations, Cost Book Budgets, Custom Registers, and Benefit records each carry their own attached documents, filtered inline from the same repository.
At its core, Documents lets you upload a file or link to one already stored elsewhere, file it under a category, describe it with whatever custom fields your organisation has defined, and — where a project type requires it — lock it while someone edits it so two people can't overwrite each other's work.
2. Why Does a Customer Use It?
One File, Many Owners: A document uploaded once to a project can be linked — not copied — onto a Risk, an Issue, a Task, a Register entry, or a Benefit. Everyone points at the same file, so there's only ever one version to go stale.
Version Control Without the Chaos: Where check-out is switched on, checking a document out stops anyone else changing it until it's checked back in. The version number increments automatically and the swap is written to project history.
Governance That Runs Itself: Every upload is scanned for viruses before it's usable, zip archives can be checked for disallowed file types hidden inside them, and an administrator can hand a document off to an external records system (EDRMS) for formal retention.
Speaks Your Industry's Language: Categories and custom Document Fields are configured by your own administrator, so a document can carry a Drawing Number, a CLIN, a Batch ID — whatever term your business actually uses — without waiting on custom development.
3. Common Use Cases by Project Type
Documents ships as a set of general-purpose building blocks — categories, custom fields, check-out, PDF markup, and the EDRMS hand-off. Below is how each of these project types typically arranges those blocks. None of this is a pre-built template inside Cora PPM — your administrator sets it up using the configuration screens covered later in this guide.
Manufacture-to-Order (MTO) ?
Categories for Engineering Drawings, Bill of Materials, Customer Purchase Orders, Test/Inspection Certificates, and Shipping Documents.
Check-out switched on for drawings and BOM revisions, so a design change mid-build can't be overwritten by a second edit.
Custom fields such as Drawing Number, Revision Class, and Work Order Reference.
The approved drawing is linked directly onto the shop-floor Task it's being built against, instead of a second copy floating around.
Document Markup used to redline a drawing PDF during design review.
Pharma & Life Sciences ?
Categories for Protocols, Batch Records, SOPs, Validation/Qualification evidence (IQ/OQ/PQ), and Regulatory Submissions.
Check-out switched on broadly — controlled documents, one editor at a time.
Custom fields such as GxP Classification, Effective Date, and Study/Protocol ID.
Controlled copies handed off to an EDRMS for validated, retention-governed storage outside Cora PPM.
Worth Knowing: Cora PPM does not include electronic signature or a Draft / In Review / Approved workflow state on documents out of the box. If your quality process needs e-signature or a formal approval chain, that has to be satisfied by the EDRMS or QMS the document is pushed to — or by applying the generic Workflow module to a custom register — not by the Documents grid itself.
Capital Projects ?️
Categories for Design Basis, Permits & Approvals, Contractor Submittals, Cost Estimate Backup, and Progress Photos.
Custom fields such as Discipline, Submittal Number, and Contract Package.
Backup documents linked directly onto the Cost Book Estimation or Budget line they support, so the evidence travels with the number.
Standard specifications and drawing templates held in Company Documents and reused across every capital project.
Government Contracting (GovCon) ?️
Categories for the Contract & its Modifications, CDRLs, Compliance/Audit Evidence, and Past Performance.
Custom fields such as CLIN, Deliverable Due Date, and Classification/Distribution Statement.
Check-out on, plus an EDRMS hand-off where the contracting agency requires records to live in a specific system of record.
The zip-content extension check is worth confirming with your security office — GovCon environments often mandate file-type allow-lists on inbound attachments.
4. Acronyms Used on This Page
Terms shown as code below are literal Cora PPM interface or configuration values. Others are industry terms customers commonly map into a category or custom field — Cora PPM has no built-in knowledge of them.
Acronym | Stands For | Context |
|---|---|---|
| Project Portfolio Management | The product category Cora PPM belongs to. |
| Electronic Document and Records Management System | Cora PPM term — the external system a document can be pushed to or pulled from for formal retention. |
| Manufacture-to-Order | Project type discussed in this guide. |
| Government Contracting | Project type discussed in this guide. |
| Good "x" Practice (e.g. GMP, GLP, GCP) | Industry term; a common custom Document Field value in pharma, not a Cora PPM concept. |
| Contract Data Requirements List | Industry term; a common GovCon document category. |
| Contract Line Item Number | Industry term; a common GovCon custom Document Field. |
| Installation / Operational / Performance Qualification | Industry term; pharma validation evidence categories. |
| Standard Operating Procedure | Industry term; a common pharma document category. |
| Portable Document Format | The only file type Document Markup (annotation) supports. |
| Database / File System | Cora PPM term — the two places uploaded files can be physically stored, set by an administrator. |
5. Step-by-Step Guide
Every walkthrough below applies wherever you find a Documents list — Project, Company, or Task — unless a step says otherwise.
Reading the Screen
The left-hand pane lists categories, each showing how many documents it holds. The Hide Empty Categories / Show Empty Categories button trims the tree down to categories that actually contain something. The right-hand grid lists the documents in whatever you've selected, with columns for file type, category, check-out status, name, version, a Properties link, who added it and when, file size, and (for PDFs) markup.
Uploading a New Document
Click the category you want the document filed under in the left-hand tree, then click
Addabove the grid.Stay on the
Upload Filestab. Drag your file onto the drop zone, or use the file picker — you can select more than one file at once.Save. The file is uploaded, virus-scanned, and appears in the grid under the category you chose.
If a document shows as disabled or won't open right after upload, the virus scan probably hasn't cleared it yet — see the FAQ below.
Adding a Hyperlink Instead of a File
Click
Add, then switch to theLink to Documenttab.Set Type to
HyperLink. Enter aNameand aLink— the link must start withhttp://orhttps://.Save. The link appears in the grid like any other row, minus a file size — clicking the name opens it in a new tab.
Linking an Existing Document Onto Another Record
Use this instead of uploading a second copy when the same file also belongs on a Risk, Issue, Task, Register entry, or Benefit.
Open the target record and click
Addon its Documents section.Switch to
Link to Document, set Type toProject Document. The existing project document list appears with aLink Documentcheckbox column.Tick the document(s) you want and Save. The record now shows the document without a second file having been stored anywhere.
A linked document can't be deleted from its original location until it's unlinked everywhere it's used.
Editing a Document's Properties
Click
Propertieson the document's row (shows asViewinstead if you only have read access).Update Name, Link, Category, or "Available for Markup", plus any custom fields your administrator has added.
Save.
Checking a Document Out and Back In
Only appears if your administrator has switched on check-out for this project type. If you don't see a Check In/Out column, this project doesn't use it.
Click
Check Outbefore you start editing your local copy. The row now readsCheck Infor you, andChecked Out(with your name in a tooltip) for everyone else — they can't check it out or delete it while you hold it.When you're done, click
Check In. Upload the revised file — keep the same file name. If you check in without choosing a new file, you'll be asked to confirm that's intentional.Save. The version number increments by one and the check-out/check-in is recorded in project history.
Only the current version is kept — there's no browsing of prior revisions, so treat the version number as a change counter rather than a full revision archive.
Marking Up a PDF
Only available where your organisation has licensed and enabled Document Markup, and only for PDF files.
Click the
Markupicon on a PDF row (shows as a view-only eye icon if the document is checked out by someone else, or if you only have view rights).Add your annotations and save. The icon changes to show the document now carries markup, so reviewers can tell at a glance which files have comments on them.
Renaming, Exporting, and Deleting
Rename — open the rename option from the document's row, update the
Document Nameand, if needed, itsCategory. The file extension can't be changed.Export the List — use
Export to Excelon the grid toolbar to get the current document list as a spreadsheet.Delete — click the delete icon on the row. It's disabled — with a tooltip explaining why — if the document is currently checked out or currently linked to another record; resolve that first.
6. For Administrators
What to Configure | Where | Effect |
|---|---|---|
Custom Document Fields | Document Fields admin screen | Add labelled fields (text, number, date, dropdown, user list, or checkbox), mark them required, and choose whether they show as a grid column by default. |
Categories | Categories admin screen | Define the folder structure documents are filed under, restrict which categories accept uploads, and control portal visibility. |
Check-Out | Project Type configuration (with a per-project override) | Turns the Check In/Out column and lock behaviour on or off. |
Storage Location | General Document Configuration | Choose whether uploaded files are stored in the database or on a file-system path. |
Zip Content Check | General Document Configuration | Blocks disallowed file types hidden inside uploaded zip archives. |
7. FAQ
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article