Skip to main content

Department Management

Departments in Pollarix allow you to organize surveys, users, and settings into logical units.

Organization Structure

What is a Department?

A department is an organizational unit containing:

  • Surveys - All surveys created within the department
  • Collectors - Survey distribution campaigns
  • Users - Team members with access to the department
  • Contacts - Your contact database
  • Settings - Department-specific configuration
Multi-Department Access

Users can belong to multiple departments with different roles in each.


User Roles & Permissions

Permission Matrix

CapabilityImplementorAdminUserRead Only
Create surveys
Edit surveys
View results
Export data
Manage collectors
Manage users
Department settings
API keys
Webhooks

Role Capabilities

Full department access:

  • Add and remove users
  • Change user roles
  • Modify all department settings
  • Access API keys and webhooks
  • Full survey and collector management

Adding Users

  1. Navigate to SettingsUsersAdd Users
  2. Select role from radio buttons
  3. Enter email addresses (comma-separated)
  4. Click Submit
Bulk Import

Add multiple users at once by separating email addresses with commas.

User Limits by Plan

PlanMax UsersAPI Users
Basic1No
Advance3No
Pro10Unlimited
EnterpriseUnlimitedUnlimited
API Users Don't Count

API users are for integrations and don't count toward your user limit!


Settings Overview

🎨

Appearance

Department name, logo, and language settings

👥

Users

Add, edit, and manage team members

🔑

API Keys

Generate tokens for programmatic access

🪝

Webhooks

Configure event notifications

📧

Email

Custom email domain setup

💬

WhatsApp

WhatsApp provider integration


Appearance Settings

Customize your department's branding and localization:

SettingDescription
Department NameMax 100 characters, visible in navigation
Culture/Languageen-US (English) or he-IL (Hebrew)
Department LogoPNG/JPG, recommended 200x200px minimum

The culture setting affects:

  • Default survey language
  • Date/time formatting
  • UI text direction (LTR/RTL)

API Keys

Pro Enterprise

Permanent Token

Long-lived token for server-to-server integrations:

Using your API token
curl -X GET 'https://api.pollarix.com/survey/department/{id}' \
-H 'Authorization: Bearer YOUR_PERMANENT_TOKEN'
Security Best Practices
  • Store tokens in environment variables
  • Never commit to version control
  • Rotate tokens periodically

Temporary Token

Short-lived tokens for testing:

Use Cases:

  • Testing API integrations
  • Temporary third-party access
  • Development and debugging

Subscription Features

FeatureBasicAdvanceProEnterprise
Surveys31050
Responses/month1005005000
Email collector
SMS collector
WhatsApp collector
Custom domain
API access
Webhooks
AutomationsBasicStandardAdvancedFull
SupportEmailEmailPriorityDedicated

Best Practices

Department Organization

StrategyWhen to Use
By TeamMarketing Dept, HR Dept, Customer Success
By RegionNorth America, Europe, Asia Pacific
By ProductProduct A Surveys, Product B Surveys
By Use CaseNPS Surveys, Support Feedback, Employee Surveys

User Role Assignment

  • Admins - Department leads, survey program managers
  • Users - Survey creators, analysts
  • Read Only - Executives, stakeholders who need visibility
  • API - Integration systems, automation tools

Security Recommendations

  1. Principle of Least Privilege - Assign minimum required role
  2. Regular Audits - Review user list quarterly
  3. Offboarding Process - Remove users promptly when they leave
  4. API Token Security - Rotate tokens, use environment variables
  5. Multi-Department Access - Be deliberate about cross-department access

API Reference

EndpointMethodDescription
/departmentGETList all departments
/department/{id}GETGet department details
/departmentPOSTCreate department
/department/{id}PUTUpdate department
/department/{id}DELETEDelete department
/department/{id}/usersGETList users
/department/{id}/usersPOSTAdd users
/department/{id}/users/{email}DELETERemove user
/department/{id}/api-tokenGETGet API token
/department/api-secretGETGet current API secret

Troubleshooting

User limit reached

Solutions:

  1. Upgrade subscription plan
  2. Remove inactive users
  3. Use API users for integrations (don't count toward limit)
User cannot access department

Check:

  1. User was added to the correct department
  2. User's role has appropriate permissions
  3. User is using correct email to log in
API token not working

Verify:

  1. Token hasn't expired (temporary tokens)
  2. Token is for the correct department
  3. API feature is available on your plan
  4. Regenerate token if compromised

Summary

TaskLocation
Change department name/logoSettings → Appearance
Add team membersSettings → Users → Add Users
Manage user rolesSettings → Users
Get API credentialsSettings → API Key
Configure webhooksSettings → Webhooks
Set up email domainSettings → Email
View subscriptionSettings → Subscription

Your department is now configured for your team!

Was this page helpful?