Skip to main content
Publive provides enterprise governance features essential for the Banking, Financial Services, and Insurance (BFSI) sector.

​
Key Requirements

RequirementPublive Feature
Content approval before publishingMaker-checker workflow via Approval Pending status
Audit trailPost created_at, updated_at, published_at, approver fields
Access controlAPI key-based authentication, role separation
Content versioningDraft/Published state separation
Compliance reviewsApproval Pending → review → Published flow

​
Implementing Maker-Checker

For BFSI compliance, every piece of content should go through the approval flow: 
Draft → Approval Pending → (Compliance Review) → Published
See the Maker-Checker Guide for detailed implementation steps.

​
Content Access Controls

Use the access_type metadata to control content visibility: 
# Create compliance-restricted content
curl -X POST \
  'https://cms.thepublive.com/publisher/123/post/' \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Internal Compliance Update",
    "type": "Article",
    "status": "Draft",
    "primary_category": 200,
    "meta_data": {"access_type": "Paid"}
  }'

​
Audit Trail

Every post includes timestamps and attribution:
FieldPurpose
created_atWhen the content was first created
updated_atLast modification timestamp
published_atWhen content went live
memberContent creator
updated_byLast editor
approverWho approved publication
sourceContent origin system

​
Best Practices

  1. Separate API keys for content creators (makers) and approvers (checkers)
  2. Always use Approval Pending status before publishing
  3. Track all state changes using the post timestamps and attribution fields
  4. Use categories to organize content by compliance domain (regulatory, investor relations, customer communications)