Skip to main content

​
Overview

Organizations define administrative and data-governance boundaries in CaseBender. Open Settings → Account → Organizations to view the organizations available to your role.
  • Super Admins can view all organizations and create new ones.
  • Organization Admins manage their current organization through the Organization item.
  • Other roles do not receive organization-management controls unless their permissions explicitly allow them.
For the broader authorization model, see Access Control.

​
Organization structure

An organization can represent a root organization, business unit, department, or team group. Organizations can also be assigned a parent to create a hierarchy.
Organization names must be unique across the CaseBender instance, not only within the same parent organization.

​
Create an organization

The Settings interface presents organization creation to Super Admins. The operation also requires an administrative server session.
1

Open Organizations

Go to Settings → Account → Organizations.
2

Start creation

Select Create organization.
3

Enter a name

Provide a unique name with between 2 and 100 characters.
4

Create the organization

Submit the form. Open Manage from the organization list to configure additional details and governance settings.

​
Manage organization details

Select Manage for an organization to open its detail page. The available fields are organized into three tabs.

​
Basic Info

Use this tab to manage:
  • Name and description
  • Organization type
  • Parent organization
  • Contact email
  • Time zone
Advanced hierarchy and contact fields are limited to Super Admins. Organization Admins can update fields permitted for their current organization.

​
Governance

Governance settings establish defaults and constraints for data handled by the organization.

​
TLP defaults

  • Default TLP is applied when a workflow does not provide another value.
  • Maximum TLP limits the highest Traffic Light Protocol level available to the organization.
Choose values that match your data-sharing policy. For details about TLP-aware authorization, see Access Control.

​
Retention and jurisdiction

Configure:
  • Data retention period in days
  • Jurisdiction
  • Data-classification settings
  • Export-controlled status
The default retention period for a newly modeled organization is 1,095 days unless your deployment or administrator establishes another value.
Governance changes can affect data handling across an organization. Review retention, jurisdiction, TLP, and export-control values with the appropriate security, privacy, and legal owners before saving.

​
Administrators

The Administrators tab separates active and pending Organization Admins. Authorized administrators can use the invitation form to add an Organization Admin. Role assignment controls who can modify organization, team, and member settings. Apply least privilege and review elevated assignments regularly.

​
Deactivate an organization

The organization list prevents a deactivation request when the organization still contains teams or users. Move or remove those dependencies before attempting the action. Deactivated organizations remain identifiable with a Deactivated status because organization removal uses a recoverable lifecycle state rather than immediately erasing the record.
Do not rely on the destructive control shown on an organization’s detail page. Use the supported action from the organization list and verify that all dependent teams and users have been handled.

​
Access model

  • Super Admins have platform-wide organization visibility.
  • Organization Admins are presented with their current organization.
  • Organization management and data access are separate concerns.
  • TLP and scoped roles can further limit which records a user can access.
  • The server remains the enforcement point even when the interface hides unavailable actions.

​
Operational recommendations

​
Design the hierarchy first

  • Use stable organizational boundaries.
  • Avoid unnecessary hierarchy depth.
  • Assign a parent only after confirming the intended reporting and governance relationship.

​
Protect governance settings

  • Document the owner of each retention and classification decision.
  • Treat export-control changes as privileged operations.
  • Review default and maximum TLP values after reorganizations.

​
Review administrators

  • Maintain at least one accountable administrator for every active organization.
  • Remove elevated access promptly when responsibilities change.
  • Verify pending assignments during periodic access reviews.

​
Troubleshooting

​
I do not see Create organization

Only a Super Admin can create an organization. Organization Admins manage their assigned organization.

​
The organization name is rejected

Use at least two characters and choose a name that is not already used anywhere in the instance.

​
I cannot deactivate an organization

Confirm that it no longer contains teams or users. If the interface still blocks the action, contact a Super Admin.

​
I cannot edit an advanced field

Organization type, hierarchy, and selected contact settings require Super Admin access.

​
API access

Organizations can also be managed through scope-controlled API endpoints:

​
Related guides