Organizations in CodeCleared

Learn how CodeCleared organizations separate tenants, roles, billing, and feature entitlements.

Purpose

An organization is CodeCleared’s tenant boundary for people, repositories, policies, billing, and entitlements.

Who

Owners manage the organization; admins manage authorized configuration; triage users record finding ignores, license overrides/honors, and scoped license allowances (project unit / repository); members use permitted resources (scan/sync). Organization-wide package allowances and whitelist appends require admin/owner.

Prerequisites

You must be invited to, or create, the organization.

How it works

Choose the organization before connecting repositories or reviewing results. Manage members and roles from organization settings. Owners/admins can also set scan data retention there (capped by the billing plan — see Billing).

Business rules

Billing and feature entitlements are live at the organization. Data and access do not cross organizations. Scan retention preference cannot exceed the plan cap.

Scenarios & edge cases

Wrong organization: switch before importing. Ownership change: retain at least one owner before removing another. Contractor exit: remove membership promptly.

Limits

Role permissions and plan capabilities limit configuration and data access.

Common errors

Believing an admin role transfers billing between organizations.
Connecting a repository to the wrong tenant.