Skip to content

Enterprise · for IT, security and records leads

Document management your IT, security and records teams can all sign off on.

Content Central runs in the cloud or on your own servers, signs people in the way your directory already does, and keeps the audit trail and retention your auditors ask about. Live in 30 days.

Book a technical demo Security review answers
Documents arrive from scan stations, email, folders, the Office add-in and API connections into Content Central, which runs in the cloud or on your own servers; people sign in with Active Directory or SAML and MFA, in a browser.COMING INCapturePoint 6 scan stationsEmail: Microsoft 365, Gmail, IMAPWatched folders and XML hand-offsOffice and Outlook add-inAPI connectionsContent Centralsearch · workflows · signatures · retentionYour serversWindows · IIS · SQLIn thecloudSIGN-INActive Directory · SAML 2.0MFA codesEveryone works in a web browser
How Content Central sits in your environment, whichever way you run it.

Three people evaluate it. Here is each one's page.

For IT

What you will run

  • In the cloud, or on your own servers (Windows Server, IIS and SQL Server): your choice
  • Everyone works in a web browser; approval queues switch to cards on a phone
  • Ribbon add-in for Word, Excel, PowerPoint, Outlook, Visio and Project
  • Revocable API connections, scoped to chosen catalogs, with an expiry
  • Lookups from any ODBC database; exports to QuickBooks, Sage 50, Sage X3, Workday and Epicor

For security

What you will review

  • Active Directory, or SAML 2.0 single sign-on with Okta, Microsoft Entra ID or ADFS
  • Authenticator-app codes, required for every user if you choose
  • Permissions by catalog, document type and field, and by field value (one branch, one department)
  • A stated reason required before sensitive documents open
  • New API keys need a system admin who signed in recently

For records

What you will answer for

  • Retention per document type, with a destruction schedule
  • Legal holds: any document kept indefinitely, overriding its schedule, with who set it
  • Every login, search, view, download, change and deletion logged; you choose how long events are kept
  • Version history on every document, check-out and check-in
  • Archive-grade PDF/A output for scanned records

Go-live

Live in 30 days. That is a commitment, not an estimate.

No year-long rollout. Start with the departments that hurt most; the rest follow in the same shape.

1. Plan

We

Map document types, fields, folders, permissions and first workflows with you

You

One owner per department; your sign-in details

2. Set up

We

Install or provision Content Central, connect sign-in, scanning and the systems you run

You

A server, or nothing if you choose the cloud

3. Train

We

Train administrators and users on your own documents

You

Time from the people who will use it every day

4. Go live

We

Stay beside your team as real work runs through it

You

Start filing

The admin model

Departments run their own corner. IT keeps the keys.

Layers, not one superuser
System administrators, administrators with specific rights, and catalog administrators who run their own department’s catalog without touching anyone else’s.
Permissions that only add
Rights add up from the groups a person is in. There is no hidden deny to debug when someone cannot see a file.
Copy a department
Duplicate a catalog, or a workflow, to set up the next department in the shape of the last one.

Migration

Four ways in, and one way out.

Files on shares
Bulk import existing files and folder trees from your file shares with the admin import tool.
Another system’s documents
Hand-offs with a descriptor file that sets the catalog, type and fields, or a watched folder.
Paper
CapturePoint 6 at each scan station splits, reads and files the backfile straight into Content Central.
Email
Shared mailboxes on Microsoft 365, Gmail or IMAP, captured with sender, date and subject as fields.
And out again
A full export of your documents and their metadata is available whenever you need it.

Your security review

The questions your reviewers will ask, answered plainly.

Where are our documents stored?
In the cloud, or on your own servers inside your network and your backups. Your choice.
How do people sign in?
Local accounts, Active Directory, or SAML 2.0 single sign-on through your identity provider, plus authenticator-app codes.
Can we prove who opened a document?
Yes. Views, downloads, searches, changes and deletions are logged with the user and time, and logins with IP address and browser.
Can a department see only its own records?
Yes, by catalog and document type, and down to a field value such as branch or department.
What can another system do through the API?
Only what its key allows: deliver documents, look them up and download them, in the catalogs it is scoped to. Keys expire and can be revoked.
How are documents emailed out?
Optionally as password-protected, encrypted ZIP files, and admins can require that for every attachment.
How Ademero handles security

Alongside Content Central

CapturePoint 6 at every scan station

A Windows app for the PCs by your scanners, in the mailroom, AP and records. It splits each stack into documents, works out what they are, reads them on that PC and files them into Content Central with their fields, over a revocable API connection. Pages are not sent anywhere to be read.

Cortexa, if you want private AI

The AI behind CapturePoint 6 and Paige, available on servers you own, quoted for your hardware and workload.

About Cortexa

Bring IT, security and records to one demo. We will answer all three.

A free technical demo on your own documents: sign-in, permissions, the audit trail, retention, and one workflow you run today.

Book a free demo (863) 937-0272

Since 2002, more than 1,000 organizations have used Ademero software. Fortune 500 companies and government agencies review our security every year and keep renewing.