Feature · Document Management System

Document management system that lives on the account, not next to it.

A document management system (DMS) is not document automation. The DMS job is storage, retrieval, access control, and lifecycle management of document artifacts: the signed proposal, the countersigned master services agreement, the archived SOW, the renewed addendum, the historical pricing sheet. Strkr runs the DMS layer natively on the CRM record so the artifact lives on the same account the deal lived on, respects the same permission model, carries into the same audit log, and retrieves through the same search surface. One subscription covers the CRM and the DMS. No per-document storage fee. No seat tax on a document platform that cannot see the pipeline.

Start free trial See pricing
What a document management system actually does

Seven DMS jobs that sit outside document automation.

Document automation generates documents. A document management system holds, retrieves, and governs the documents after they exist. The seven jobs below are the DMS surface, separate from the drafting shape. A team buying document automation often forgets the DMS layer and ends up with signed PDFs scattered across email, Dropbox, and a legacy drive.

Attach to the record

Every document lands on the account.

Every signed proposal, master services agreement, SOW, invoice, renewal addendum, and change order attaches to the account record. The common failure where "where is the signed Acme MSA from 2023" takes a day of email archaeology does not happen because the artifact is on the account record with the signing date and the countersign receipt.

Permission-aware access

The DMS respects the CRM permission model.

Access to documents inherits from the Strkr permission model. A rep sees documents on accounts the rep owns. Legal sees documents across the full tenant with legal filters. The CFO sees financial documents across all accounts. The common failure where a DMS has a separate permission model that drifts from the CRM does not happen.

Search across accounts

Find every document matching a query.

Cross-account search: find every document that references a legal entity, every SOW signed in Q3 under 100k dollars, every renewal addendum that applied the 2024 pricing. The DMS search surface sits inside the CRM, so the search respects permissions and returns results in the record context.

Retention management

Retention windows per document type.

Documents carry retention windows per type: HIPAA-regulated documents at six years, financial documents at seven, standard commercial documents at the tenant default. The retention engine purges documents on schedule or extends on legal hold. The common failure where "we are storing twenty years of signed PDFs we were supposed to purge" does not happen.

Legal hold

Freeze retention on named cases.

Legal can place a hold on documents tagged to a case, matter, or account. The hold freezes retention and locks the documents from modification or deletion. The audit log carries the hold placement, the scope, and the released state. The common failure where a legal hold request takes three weeks to execute does not happen because the hold is a one-click action in the UI.

Version chain

Original draft through countersign receipt.

Every document carries its version chain: the original draft, the approved version, the sent version, the signed version, the countersigned version. A six-month-later audit reconstructs the full chain. The common failure where "which version did we actually countersign" has no answer does not happen because the version chain is pinned.

Audit log integration

Every access event lands on the chain.

Every DMS action (open, download, forward, delete attempt, retention expiry, legal hold placement) lands on the audit log keyed on the document and the account. A compliance query like "who accessed the Acme MSA in the last 90 days" is a filter on the audit page. The log is append-only with cryptographic integrity.

How Strkr DMS differs from document automation

Six distinctions that matter for the right stack.

Document management system and document automation sound similar but solve different problems. The six distinctions below help a team shape the right stack. A team may need both. The buyer who understands the distinction avoids buying a DMS when they need automation or buying automation when they need storage.

DMS vs automation

Storage versus generation.

Document automation generates documents from templates and typed records. A DMS stores and governs documents after they exist. The two jobs are complementary. A team drafting 300 proposals a month needs both: the drafter to generate the proposals and the DMS to store the signed ones with retention and audit.

DMS vs file share

Record-aware versus folder-structured.

A file share (Dropbox, Google Drive, SharePoint) stores documents in folders. A DMS stores documents against records (accounts, opportunities, contracts) with the record context. The common failure where a signed PDF lives in a Google Drive folder nobody knows about does not happen because the artifact is on the account.

DMS vs CLM

Storage versus lifecycle.

A contract lifecycle management (CLM) platform owns the pre-signature negotiation, the clause library, the approval routing, and the obligation tracking on signed contracts. A DMS owns the storage, access, retention, and audit of the artifacts. Many teams run a CLM for the contract shape plus a DMS for everything else.

DMS vs e-sig storage

Native CRM versus vendor storage.

DocuSign and PandaDoc store signed envelopes in their own libraries. The Strkr DMS pulls the signed PDF back onto the account record through the native integration so the artifact lives in the CRM. The e-signature library stays as the source for the signed envelope certificate. The CRM holds the operational copy with the record context.

DMS vs intranet wiki

Transactional versus narrative.

Strkr Docs is a Confluence-style internal wiki for narrative content: runbooks, process documentation, team knowledge base. The DMS is for transactional artifacts: signed contracts, invoices, proposals. The two surfaces are separate because the governance shapes are different. The wiki does not have retention windows and legal hold. The DMS does.

DMS vs ECM

Record-centric versus enterprise content.

Enterprise content management (ECM) platforms like OpenText or Documentum manage every document type across every department. The Strkr DMS is scoped to the CRM shape: documents attached to accounts, opportunities, contracts, and projects. For teams with a broader ECM scope, Strkr integrates through the open API without trying to replace the ECM.

The engineering underneath

What makes the DMS production-grade.

A DMS that stores PDFs is a file share. A production DMS has to carry version chains, permission awareness, retention windows, legal holds, audit log integration, and cross-account search with query latency that scales. Strkr ships the primitives that keep the DMS holding up at scale.

Encrypted at rest

Per-tenant key hierarchy.

Documents encrypt at rest with per-tenant key hierarchies managed through KMS. The common failure where a DMS stores signed PDFs in plain text does not happen. Key rotation is a tenant setting. Compliance walkthroughs confirm the encryption posture through the standard SOC 2 and HIPAA audit documentation.

Content-addressed storage

Deduplication and integrity.

Content-addressed storage deduplicates identical documents and verifies integrity on every retrieval. The common failure where a signed PDF subtly corrupts over time without anyone noticing does not happen because the content hash verifies on every read. Storage efficiency is a side benefit.

Full-text indexed

Search across every document.

Documents index for full-text search on upload. Cross-account search returns results in the record context with permission filtering applied. The common failure where "I need to find every document that mentions Section 7.2" takes a day of grep does not happen because the search is a first-class query surface.

Retention engine

Scheduled purge, legal hold aware.

The retention engine runs daily, computes documents past retention, applies legal holds, and purges or extends per policy. The common failure where "we have twenty years of documents we were supposed to purge" does not happen because the retention engine runs as scheduled infrastructure rather than an occasional manual purge.

Audit integration

Every DMS action joins the chain.

Every DMS action (open, download, forward, retention event, hold placement) emits a structured audit event. The audit log is append-only with cryptographic integrity. A compliance query joins DMS events with CRM record events and flow run events in one filter. The chain is complete.

Open API

Document in, document out.

The open API covers inbound (upload a document, attach to a record, apply tags) and outbound (retrieve a document, generate a signed URL for download, query metadata). Third-party tools integrate through the API. The common failure where a DMS traps documents in a proprietary format does not happen.

Where teams land in practice

Three DMS deployment patterns from live customers.

A 60-seat SaaS, a 180-seat professional services firm, and a 420-seat healthcare company all run the Strkr DMS layer. The platform plumbing stays the same. The retention windows, the permission model, and the search patterns flex to the business. The compliance posture holds across all three.

SaaS pattern

Proposals and renewals, moderate retention.

A 60-seat SaaS runs the DMS across 300+ documents a month: signed proposals, order forms, renewal addendums. Retention is seven years for the signed artifacts. Legal hold fires on three or four cases a year. Search across accounts resolves in seconds. The DMS is a background utility that the sales team never has to think about.

Services firm

SOWs and change orders, long retention.

A 180-seat professional services firm runs the DMS across SOWs, change orders, delivery acceptance letters, and client correspondence. Retention is ten years. Legal hold fires on client disputes a few times a year. Search by client, by date range, and by document type is a daily operation for the delivery team.

Healthcare company

HIPAA retention, BAA chain of custody.

A 420-seat healthcare company runs the DMS with HIPAA retention (six years from last touch) across proposals, BAA addendums, and clinical partnership agreements. The audit log carries the BAA chain of custody for every PHI customer. Strkr is HIPAA compliant with a BAA available.

Legal hold event

Case freezes retention across accounts.

When a legal dispute arises, counsel places a hold on all documents tagged to the matter. The hold freezes retention and locks modification. The audit log carries the hold placement, scope, and release. Discovery requests resolve from the DMS search surface rather than a cross-system archaeology project.

Quarterly retention review

Compliance checks the purge log.

Quarterly, the compliance officer reviews the retention purge log. Documents purged in the quarter and documents on legal hold both get reviewed. The common failure where a document is purged while under legal hold does not happen because the retention engine respects the hold flag before purging.

Compliance walkthrough

DMS satisfies the auditor in one meeting.

When a regulator or SOC 2 auditor walks the DMS, the chain of custody is a URL with filters. The encryption posture is documented. The retention engine logs are queryable. The permission model is auditable. The common failure where a DMS walkthrough takes a six-week engagement does not happen.

Document management system built into the CRM record.

Strkr runs the DMS layer natively on the account record with signed artifacts, permission-aware access, retention windows, legal hold, cross-account search, and audit log integration. Flat $50 per seat with no per-document storage fee.

Start free See pricing
Common questions

What buyers ask about this feature.

What is the difference between a document management system and document automation?

Document automation generates documents from templates and typed records. A document management system (DMS) stores and governs documents after they exist. The two jobs are complementary rather than overlapping. A team drafting 300 proposals a month needs both: the drafter to generate the proposals and the DMS to store the signed ones with retention and audit. Strkr ships both layers natively on the CRM record. The drafter reads the typed record and generates the document. The DMS attaches the signed artifact to the account with the version chain, permission inheritance, retention window, and audit integration. One subscription covers both. No per-document storage fee.

Can Strkr replace our existing document management system like SharePoint or iManage?

For CRM-adjacent documents (signed proposals, master services agreements, SOWs, invoices, renewal addendums, change orders), yes. The Strkr DMS attaches the artifacts to the account record with permission inheritance, retention windows, legal hold, cross-account search, and audit log integration. For broader enterprise content management covering every department (HR files, operations manuals, engineering specs), Strkr integrates with the ECM through the open API rather than trying to replace it. Many teams run Strkr for the revenue-adjacent documents and keep SharePoint or iManage for the broader ECM scope. The handoff happens through the open API.

How does the Strkr DMS handle legal hold?

Legal counsel places a hold on all documents tagged to a case, matter, or account through a one-click action in the UI. The hold freezes retention and locks the documents from modification or deletion. The scope can be a single document, every document on an account, or every document matching a tag or date range. The audit log carries the hold placement, the scope, the actor, and the release when the hold lifts. The retention engine respects the hold flag before purging. The common failure where a legal hold request takes three weeks to execute or where a document is purged while under hold does not happen.

What retention windows does the Strkr DMS support?

Retention is configurable per document type and per tenant up to the regulated horizon the business operates under. Healthcare tenants typically retain for the HIPAA six-year window. Financial services tenants typically retain for seven years. Standard commercial tenants default to a configurable window. The retention engine runs daily, computes documents past retention, applies legal holds, and purges or extends per policy. The common failure where "we have twenty years of documents we were supposed to purge" does not happen because the retention engine runs as scheduled infrastructure rather than an occasional manual purge.

Can we search across every document in the DMS?

Yes. Every document indexes for full-text search on upload. Cross-account search returns results in the record context with permission filtering applied. The ops lead can find every document that references a legal entity, every SOW signed in Q3 under 100k dollars, every renewal addendum that applied the 2024 pricing, or every document that mentions a clause from the clause library. The search surface respects the Strkr permission model so a rep running the same search only sees documents on accounts the rep owns. The common failure where "I need to find every document that mentions Section 7.2" takes a day of grep does not happen because the search is a first-class query surface.

Is the DMS included in the Strkr seat price or separate?

The DMS is included in the flat $50 per seat price. No per-document storage fee. No per-gigabyte fee. No tiered storage pricing. The common failure where a DMS vendor advertises a low per-seat price and the real cost is in storage overage fees does not happen because the pricing page is the full price. Teams storing 10,000 signed PDFs a year pay the same as teams storing 100. The retention engine helps teams stay within reasonable storage patterns without ever generating overage invoices. One subscription covers the CRM, the drafter, the DMS, and the audit log.

Related features

Pair this with...

Document Automation Document Process Automation Document Workflow Automation Audit Log Document Signing Automation Document Processing Automation AI Document Automation

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing