BFSI Compliance - Publive Docs

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

Key requirements

Requirement	Publive Feature
Content approval before publishing	Maker-checker workflow via `Approval Pending` status
Audit trail	Post `created_at`, `updated_at`, `published_at`, `approver` fields
Access control	API key-based authentication, role separation
Content versioning	Draft/Published state separation
Compliance reviews	`Approval 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/<PUBLISHER_ID>/post/' \
  -H 'Authorization: Basic <BASE64_AUTH_TOKEN>' \
  -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:

Field	Purpose
`created_at`	When the content was first created
`updated_at`	Last modification timestamp
`published_at`	When content went live
`member`	Content creator
`updated_by`	Last editor
`approver`	Who approved publication
`source`	Content origin system

Best practices

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

Last modified on July 21, 2026