Clari Security Basics

Overview

Secure your Clari integration: API token management, exported data PII handling, and access control best practices.

Prerequisites

• An approved secret manager and named API-token owner
• A documented data classification for forecast and rep-level exports
• Role-based access groups for production and non-production consumers
• A tested token-rotation and incident escalation path

Instructions

Step 1: Token Management

# Store token in secrets manager
aws secretsmanager create-secret \
  --name "clari/prod/api-token" \
  --secret-string "${CLARI_API_KEY}"

# In CI/CD, load from secrets
export CLARI_API_KEY=$(aws secretsmanager get-secret-value \
  --secret-id "clari/prod/api-token" --query SecretString --output text)

Rotation: Clari API tokens are generated per-user. To rotate, generate a new token in User Settings, update all consumers, then discard the old one.

Step 2: Exported Data PII Handling

Clari export data contains PII (rep names, emails, deal amounts):

def redact_pii(entries: list[dict]) -> list[dict]:
    """Redact PII from forecast entries for non-production use."""
    import hashlib

    redacted = []
    for entry in entries:
        r = entry.copy()
        if "ownerEmail" in r:
            r["ownerEmail"] = hashlib.sha256(
                r["ownerEmail"].encode()
            ).hexdigest()[:12] + "@redacted"
        if "ownerName" in r:
            r["ownerName"] = f"Rep-{hashlib.sha256(r['ownerName'].encode()).hexdigest()[:6]}"
        redacted.append(r)
    return redacted

Step 3: Security Checklist

• [ ] API token in secrets manager, not in code
• [ ] .env files in .gitignore
• [ ] Exported data stored in access-controlled warehouse
• [ ] PII redacted in non-production environments
• [ ] Export download URLs are temporary -- do not cache
• [ ] Audit who has API token access
• [ ] Token regenerated if any team member leaves

Error Handling

Output

Create a security review record with token owner, secret reference, authorized roles, data destinations, redaction status, rotation date, and exception approvals. The record must never contain a live token, temporary download URL, or unredacted forecast/rep data.

Examples

When an analyst leaves, issue a replacement service token in the secret store, update the affected job, prove that it runs with its assigned role, then revoke the former user token. If an export was copied into a test workspace, quarantine it and replace it with redacted data before work resumes.

Resources

• Clari Security
• Clari Developer Portal

Next Steps

For production deployment, see clari-prod-checklist.