> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thepublive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# BFSI Compliance

> Implementing Publive for Banking, Financial Services, and Insurance

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](/dxp/documentation/guides/workflows/approval-flow):

```
Draft → Approval Pending → (Compliance Review) → Published
```

See the [Maker-Checker Guide](/dxp/documentation/guides/workflows/maker-checker) for detailed implementation steps.

## Content access controls

Use the `access_type` metadata to control content visibility:

```bash theme={null}
# 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

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)