Skip to main content

Organizations & Workspaces

Organizations are the top-level entity in Hooklistener that contains all your webhook workflows, team members, and settings. Understanding how Organizations work is essential for team collaboration and resource management.

Overview

An Organization in Hooklistener represents your company, team, or project. All your Bridges, Sources, Destinations, Secrets, and other resources belong to an Organization.

Key features:

  • Centralized management: All webhook workflows in one place
  • Team collaboration: Invite team members to your Organization
  • Shared resources: Bridges, Secrets, and API Keys shared across team
  • Billing management: Single subscription for entire Organization
  • Access control: Manage who can access what
  • Usage tracking: Monitor webhook volume and quotas

Organization Structure

What Belongs to an Organization

Every Organization contains:

Webhook Resources:

  • Bridges (Sources + Destinations)
  • Filters
  • Transformations
  • Secrets
  • API Keys

Team:

  • Organization members
  • Invitations (pending)
  • Roles and permissions

Configuration:

  • Billing and subscription
  • Notification preferences
  • Signing secrets
  • Usage limits and quotas

Data:

  • Events (incoming and outgoing)
  • Issues
  • Circuit breaker states
  • Metrics and analytics

Organization Isolation

Organizations are completely isolated from each other:

  • No data sharing: Events, webhooks, and configurations are private
  • Separate billing: Each Organization has its own subscription
  • Independent quotas: Usage limits per Organization
  • Isolated secrets: Secrets only accessible within their Organization

Creating an Organization

Your First Organization

When you sign up for Hooklistener, your first Organization is created automatically:

Default name: Based on your email (e.g., "John's Organization") Owner: You (the person who signed up) Plan: Free plan to start

Creating Additional Organizations

You can create multiple Organizations for different projects or teams:

  1. Click your profile in the top-right
  2. Select "Create Organization"
  3. Enter Organization name
  4. Click "Create"

Use cases for multiple Organizations:

  • Separate client projects
  • Different business units
  • Development vs Production environments
  • Personal vs Company use

Switching Between Organizations

If you belong to multiple Organizations:

  1. Click your Organization name in the top-left
  2. Select the Organization you want to switch to
  3. All resources will change to that Organization's

Organization Settings

Access Organization settings from the dashboard:

Navigate to: Organization Settings (gear icon)

General Settings

Organization Name:

  • Displayed throughout the dashboard
  • Used in notifications and emails
  • Can be changed anytime

Organization ID:

  • Unique identifier for API calls
  • Cannot be changed
  • Used in API endpoints

Billing & Subscription

Current Plan:

  • Free, Team, or Enterprise
  • Feature limits and quotas
  • Billing cycle

Usage:

  • Current webhook volume
  • Events per month
  • Quota utilization

Payment:

  • Payment method
  • Billing history
  • Invoices

Contact support for detailed plan information.

Notification Preferences

Configure how your Organization receives alerts:

Email Notifications:

  • New Issues
  • Circuit breaker events
  • High failure rates
  • Usage quota warnings

Webhook Notifications:

  • Send alerts to Slack, Discord, etc.
  • Configure custom webhooks
  • Set notification filters

Notification Channels:

  • Email
  • Slack
  • Discord
  • Telegram
  • Custom webhooks

Signing Secret

Organization-wide signing secret for webhook verification:

Purpose:

  • Verify webhooks sent FROM Hooklistener to your services
  • Validate webhook authenticity
  • Prevent spoofing

Management:

  • Generate new signing secret
  • Roll signing secret (update without downtime)
  • View current secret

See Signing Secrets for detailed information.

Team Management

Organization Members

View and manage team members:

Navigate to: Organization Settings → Members

Member information:

  • Email address
  • Role (Owner, Admin, Member)
  • Joined date
  • Last active

Roles and Permissions

Owner:

  • Full access to everything
  • Billing and subscription management
  • Delete Organization
  • Transfer ownership
  • One Owner per Organization

Admin:

  • Manage all webhook resources
  • Invite and remove members (except Owner)
  • Manage API keys and Secrets
  • Cannot manage billing or delete Organization

Member:

  • Create and manage Bridges
  • View Events and Issues
  • Create Transformations and Filters
  • Cannot manage team or billing

Inviting Team Members

Add team members to collaborate:

  1. Organization SettingsMembers
  2. Click "Invite Member"
  3. Enter email address
  4. Select role (Admin or Member)
  5. Click "Send Invitation"

Invitation process:

  1. Invitation email sent to recipient
  2. Recipient clicks link in email
  3. If no account: Create Hooklistener account
  4. If existing account: Accept invitation
  5. Member added to Organization

Invitation expiration:

  • Invitations expire after 7 days
  • Resend if expired
  • Cancel pending invitations

Removing Team Members

Remove members when needed:

  1. Organization SettingsMembers
  2. Find the member
  3. Click "Remove"
  4. Confirm removal

What happens:

  • Member loses access immediately
  • Resources they created remain in Organization
  • Cannot be undone (must re-invite)

Considerations:

  • Review their API keys (may want to revoke)
  • Check any personal integrations
  • Communicate with team about removal

Resource Sharing

All resources within an Organization are shared among members:

Shared Resources

Bridges:

  • All members can see all Bridges
  • Edit permissions based on role
  • Events visible to all members

Secrets:

  • All members can use Secrets
  • Only Admins and Owner can view/edit
  • Used in {{SECRET_NAME}} references

API Keys:

  • Created per member or shared
  • All API keys have Organization-level access
  • Track usage per API key

Transformations:

  • Reusable across Bridges
  • All members can use existing transformations
  • Create and edit based on role

Access Control Best Practices

  1. Principle of least privilege:

    • Give members minimum required role
    • Promote to Admin only when necessary
    • Owner should be primary account holder
  2. Separate Organizations for isolation:

    • Different clients → Different Organizations
    • Production vs Development → Different Organizations
    • Strict isolation required → Separate Organizations
  3. Regular access reviews:

    • Review member list quarterly
    • Remove inactive members
    • Audit API keys and usage

Organization Limits and Quotas

Each plan has different limits:

Free Plan

Events: 1,000 per month Bridges: 3 Destinations: 10 total Team members: 1 (just you) Event retention: 7 days API Keys: Not available

Team Plan

Events: 100,000 per month Bridges: Unlimited Destinations: Unlimited Team members: Up to 10 Event retention: 30 days API Keys: Unlimited Transformations: Unlimited Secrets: Unlimited

Enterprise Plan

Events: Custom (millions+) Bridges: Unlimited Destinations: Unlimited Team members: Unlimited Event retention: 90 days (configurable) API Keys: Unlimited Transformations: Unlimited Secrets: Unlimited Dedicated support: Yes SLA: 99.9% uptime

Contact support for complete plan details.

Monitoring Organization Usage

Usage Dashboard

Navigate to: Organization Settings → Usage

Metrics displayed:

  • Total events (incoming + outgoing)
  • Events by Bridge
  • Quota utilization
  • Trend over time

Usage breakdown:

  • Incoming events count
  • Outgoing events count
  • Failed deliveries
  • Retry attempts

Quota Alerts

Set up alerts before hitting limits:

Warning thresholds:

  • 80% quota used
  • 90% quota used
  • 95% quota used

Actions when approaching limit:

  • Upgrade plan
  • Optimize webhook volume
  • Review and delete unused Bridges

What happens at limit:

  • New webhooks are rejected
  • Existing webhooks complete processing
  • Retries continue
  • Upgrade to resume service

Best Practices

Organization Setup

  1. Choose meaningful names:

    • Company name or project name
    • Easy to identify
    • Professional (visible to team)
  2. Set up billing early:

    • Add payment method
    • Choose appropriate plan
    • Set up billing alerts
  3. Configure notifications:

    • Set up critical alerts
    • Add notification channels
    • Test notification delivery

Team Collaboration

  1. Invite team members early:

    • Share the workload
    • Enable collaboration
    • Build redundancy
  2. Use descriptive resource names:

    • Clear Bridge names
    • Documented Secrets
    • Tagged resources
  3. Establish conventions:

    • Naming patterns
    • Tagging strategy
    • Documentation standards

Security

  1. Protect Owner account:

    • Strong password
    • Enable 2FA
    • Monitor login activity
  2. Regular access reviews:

    • Quarterly member audit
    • Remove inactive users
    • Review permissions
  3. API key management:

    • Rotate keys regularly
    • Track key usage
    • Revoke unused keys

Scaling

  1. Monitor usage trends:

    • Track growth over time
    • Plan for capacity
    • Upgrade before limits
  2. Optimize webhook volume:

    • Use filters to reduce unnecessary processing
    • Batch when possible
    • Review and cleanup unused Bridges
  3. Plan for growth:

    • Upgrade plan proactively
    • Add team members as needed
    • Implement processes early

Troubleshooting

Can't Access Organization

Problem: Organization not showing or access denied

Possible causes:

  • Removed from Organization
  • Invitation not accepted
  • Signed in with different account

Solutions:

  • Check invitation email
  • Confirm email address
  • Contact Organization Owner
  • Verify correct account

Quota Exceeded

Problem: Webhooks being rejected, quota limit reached

Solutions:

  1. Immediate:

    • Upgrade plan
    • Pause non-critical Bridges
    • Wait for quota reset (monthly)
  2. Long-term:

    • Upgrade to higher plan
    • Optimize webhook volume
    • Use filters to reduce events

Missing Resources

Problem: Bridges or resources not visible

Possible causes:

  • Wrong Organization selected
  • Resources were deleted
  • Insufficient permissions

Solutions:

  • Switch to correct Organization
  • Check with team about deletions
  • Request permission upgrade

Invitation Issues

Problem: Team member can't accept invitation

Possible causes:

  • Invitation expired
  • Email spam filter
  • Wrong email address

Solutions:

  • Resend invitation
  • Check spam/junk folder
  • Verify email address
  • Use different email if needed

Workspaces (Coming Soon)

Note: Workspaces are a planned feature for organizing resources within an Organization.

Planned features:

  • Group Bridges by project or environment
  • Workspace-level permissions
  • Isolated resources within Organization
  • Workspace-specific quotas

Stay tuned for updates!

Next Steps

Now that you understand Organizations:

  1. Invite team members to collaborate
  2. Configure Signing Secrets for security
  3. Manage API Keys for programmatic access
  4. Review available plans to find the right fit
  5. Set up notifications for alerts

Your Organization is the foundation of your webhook automation. Set it up properly from the start to enable smooth collaboration and scaling as your needs grow.