Multi-Department Setup Guide¶

Learn how to configure Zotniq for multi-department deployments within your organization.

SDK v1 note

Some examples on this page reference the legacy client.with_policy_group() method that shipped in an earlier SDK. The v2 team architecture makes policy groups obsolete — mint one team API key per department instead and pass the correct key to each Zotniq(api_key=...) call. The narrative on this page is being rewritten for the team-key model.

Overview¶

Zotniq supports a hierarchical structure for managing different departments with different policies:

Your Organization
├── License (zot_lic_xxx)
├── Policy Groups (Departments)
│   ├── Engineering
│   ├── Marketing
│   ├── Sales
│   └── Default
└── Policies
    ├── Engineering Policy (strict secrets blocking)
    ├── Marketing Policy (allow masked PII for analytics)
    └── Sales Policy (mask financials, allow names)

Multi-org management

Managing multiple separate companies under one account isn't a self-service feature today. Contact sales if you need it and we'll scope what's possible.

Policy Groups (Departments)¶

Policy groups allow different departments to have different rules under the same organization license.

Use Cases¶

Department	Policy Focus
Engineering	Strict API secret blocking
Marketing	Allow masked PII for analytics
Legal	Block all sensitive data
Sales	Allow customer names, mask financials

Creating Policy Groups¶

Via Dashboard:

Go to Organization → Settings → Policy Groups
Click Create Policy Group
Configure rules for this group

Via SDK:

from zotniq import Zotniq

# Initialize with org license
zotniq = Zotniq(api_key="zot_lic_xxx")

# Create instances for different departments
engineering = client.with_policy_group("engineering")
marketing = client.with_policy_group("marketing")
sales = client.with_policy_group("sales")

# Each uses department-specific rules
eng_result = engineering.check(content, "AI_TOOL")
mkt_result = marketing.check(content, "AI_TOOL")

Organization Settings¶

Data Region¶

Configure where data is processed for compliance:

Region	Data Center	Compliance
US	Virginia	SOC2, HIPAA
EU	Frankfurt	GDPR, SOC2
APAC	Singapore	SOC2

Data region + retention

retention_mode is configurable on every org today (FULL vs METADATA). Data-region selection (EU vs US vs APAC) is not a self-service toggle yet — contact sales if you have a residency requirement.

Policies Per Department¶

Create department-specific policies:

Engineering Policy¶

{
  "name": "Engineering Policy",
  "tags": ["engineering", "strict"],
  "rules": [
    {
      "name": "Block All Secrets",
      "dataTypes": ["API_SECRETS"],
      "destinations": ["AI_TOOL", "VENDOR", "CUSTOMER"],
      "action": "BLOCK"
    },
    {
      "name": "Mask PII for AI",
      "dataTypes": ["PII"],
      "destinations": ["AI_TOOL"],
      "action": "MASK"
    }
  ]
}

Marketing Policy¶

{
  "name": "Marketing Policy",
  "tags": ["marketing", "analytics"],
  "rules": [
    {
      "name": "Allow Masked Email",
      "dataTypes": ["PII"],
      "destinations": ["VENDOR"],
      "action": "MASK"
    },
    {
      "name": "Block Financial Data",
      "dataTypes": ["FINANCIAL"],
      "destinations": ["AI_TOOL", "VENDOR"],
      "action": "BLOCK"
    }
  ]
}

SDK Configuration¶

Single Organization¶

import os
from zotniq import Zotniq

# Use license key from org settings
zotniq = Zotniq(api_key=os.environ["ZOTNIQ_API_KEY"])