Campaign Manager - Administration Guide

Part 3 of 5 - Roles, permissions, configuration, infrastructure, audit, and power-user tips

1. Roles & Permissions

Permission Model

flowchart TD
    Check["Does user have permission X for company Y?"]
    Check --> Super{"Super User?"}
    Super -->|Yes| Allow["ALLOWED"]
    Super -->|No| DenyOvr{"DENY override for this company?"}
    DenyOvr -->|Yes| Block["BLOCKED"]
    DenyOvr -->|No| AllowOvr{"ALLOW override for this company?"}
    AllowOvr -->|Yes| Allow
    AllowOvr -->|No| Group{"Permission group for this company?"}
    Group -->|Has it| Allow
    Group -->|No| Global{"Global permission?"}
    Global -->|Has it| Allow
    Global -->|No| Block

Three-tier model: (1) Permission Groups = collections of permissions assigned to users per company, (2) Overrides = individual Allow/Deny per user per company (Deny always wins), (3) Super User = flag that grants all permissions automatically.

Permission Groups

A Permission Group is a named set of permissions that can be assigned to users on a per-company basis. Think of it as a role - for example, "Campaign Editor", "Reviewer", "Admin". Users can belong to different groups in different companies, enabling fine-grained access control across the multi-tenant platform.

Permission Overrides (ALLOW / DENY)

Overrides are per-user, per-company exceptions to group-based permissions. Two types:

• ALLOW override - grants a specific permission to a user in a specific company, regardless of their group membership.
• DENY override - blocks a specific permission for a user in a specific company, even if their group grants it. DENY always wins over ALLOW.

Super User

A boolean flag on the user record. When enabled, the user has all permissions in all companies automatically. No group membership or overrides are checked - the system short-circuits to "allowed" immediately. Use sparingly - typically reserved for system administrators.

Permission Scopes

Authentication

Company Isolation (Multi-Tenancy)

Permission Categories (170+ permissions)

2. Permission Override Precedence

The system evaluates permissions in a strict 5-layer order. Understanding this precedence is critical for managing access correctly.

flowchart TD
    Check["Check permission X
for user in company Y"]
    Check --> S{"Super User?"}
    S -->|Yes| A["ALLOWED
(all permissions, always)"]
    S -->|No| D{"DENY override
for this company?"}
    D -->|Yes| B["BLOCKED
(DENY always wins)"]
    D -->|No| AO{"ALLOW override
for this company?"}
    AO -->|Yes| A
    AO -->|No| G{"Permission group
for this company?"}
    G -->|Has it| A
    G -->|No| GL{"Global
permission?"}
    GL -->|Has it| A
    GL -->|No| B

    style A fill:#F2FCF3,stroke:#00BC19
    style B fill:#FFF2F2,stroke:#DC2626

3. Configuration & Settings

Company Settings

Campaign Settings

User Preferences (Per-User!)

AI Model Configuration Impact

Feature Flags (Permission-Based)

Feature flags in Campaign Manager are implemented as permissions, not separate toggles. To enable or disable a feature for a user, add or remove the corresponding permission from their permission group.

4. Infrastructure & Background Processes

File Storage Architecture

File organization: /{companies}/{companyName}/{campaignFolder}/{phaseFolder}/{stepFolder}/{fileName}

Scheduled Background Jobs

The system runs 8 background schedulers. Some maintain system health, others directly affect what users see.

Intercom Integration

If enabled, the system provides HMAC and JWT tokens for secure Intercom widget embedding. This enables in-app customer support chat.

Dictionary System

Maintains a controlled vocabulary (currently for CSS classes). When a dictionary entry is deleted, it cascades: the class is removed from all steps and document templates that reference it.

5. Audit Trail

What's Tracked

Every change to these entities is recorded with who, when, and what changed:

• Campaigns, Phases, Steps
• All CC Items (computation variables)
• Environment variables
• Document templates
• Campaign i18n labels
• Permission groups and overrides
• AI model configurations
• LLM API keys

Can You Restore Previous Versions?

Yes, partially. The system can restore specific CC items to a previous state from the audit history. You select a business transaction (a grouped set of changes) and the keys to restore. The current items are deleted and replaced with the audit snapshot. A new snapshot is created after restoration for lineage.

6. Non-Obvious Features & Power-User Tips