Organizations

Organizations represent departments or divisions within your company. They sit between the company and teams in Nembl's entity hierarchy: Company > Organization > Team > Individual. Organizations scope resources, set requirements for their teams, and define SLAs that cascade downward.

Entity Hierarchy

Company (Acme Corp)
├── Organization (Engineering)
│   ├── Team (Frontend)
│   ├── Team (Backend)
│   └── Team (QA)
├── Organization (Product)
│   ├── Team (Product Management)
│   └── Team (Design)
└── Organization (Operations)
    ├── Team (IT Support)
    └── Team (DevOps)

Organizations group related teams and provide a management layer for resources, policies, and reporting.

Organization Levels

Nembl supports hierarchical organization levels to reflect real-world company structures. An organization level defines where an organization sits in the hierarchy (e.g., Division > Department > Group).

Configuring Organization Levels

1. Navigate to Settings > Company > Organization Levels.
2. Define your levels from highest to lowest. For example:
   • Level 1: Division
   • Level 2: Department
   • Level 3: Group
3. Click Save.

When creating an organization, you select its level and optionally assign a parent organization at the level above.

Example Multi-Level Structure

Division: Technology
├── Department: Engineering
│   ├── Group: Platform
│   └── Group: Applications
└── Department: IT Operations
    ├── Group: Infrastructure
    └── Group: Security

Creating an Organization

1. Navigate to Settings > Organizations.
2. Click Create Organization.
3. Enter the organization name.
4. Select the organization level (if levels are configured).
5. Optionally select a parent organization.
6. Add an optional description.
7. Click Save.

Managing Organization Settings

Basic Information

Edit the organization name, description, and parent at any time from the organization detail page.

Organization-Scoped Resources

Organizations can own and scope the following resources:

Adding Teams to an Organization

1. Open the organization from Settings > Organizations.
2. Click Create Team (or move an existing team into the organization).
3. The team inherits the organization's policies and has access to organization-scoped resources.

See Groups & Teams for details on team configuration.

Org-Scoped Policies and Cascading

Policies defined at the organization level cascade to all teams and individuals within that organization. This enables patterns like:

• An Engineering organization that denies workflows:delete on production-tagged workflows for all its teams.
• A Finance organization that requires sensitivity: high tagging on all secrets.
• An Operations organization that allows agents:configure so all its teams can set up AI intake agents.

Cascading follows the hierarchy: Company policies apply to all organizations, organization policies apply to all teams within that organization. See Policies & ABAC for the full evaluation model.

Deleting an Organization

1. Navigate to Settings > Organizations.
2. Click on the organization to delete.
3. Click Delete Organization.
4. Choose how to handle child resources:
   • Move teams to another organization
   • Delete teams and their associated resources
5. Confirm the deletion.

Deleting an organization does not delete requests or audit history. Historical records retain the original organization reference for compliance.

Reporting and Visibility

Organization-level views aggregate data from all teams within the organization:

• Request volume -- total requests across all teams, broken down by status
• SLA performance -- compliance rates rolled up from team-level SLAs
• Capacity -- team workload distribution across the organization
• Audit trail -- all actions taken within the organization's scope

These views are available to organization managers and company admins from the organization detail page.

Best Practices

• Mirror your real org chart. Organizations should reflect how your company is actually structured, not an idealized version.
• Use organization levels for large companies. If you have divisions containing departments, set up levels to capture that hierarchy.
• Set policies at the right level. Company-wide policies go on the company. Department-specific restrictions go on the organization. Team-specific rules go on the team.
• Keep organizations stable. Reorganizations affect policy cascading and reporting. Plan changes carefully and communicate to affected teams.