Skip to main content

Organizations

In AuditHub, an organization is the top-level workspace. It groups the users, projects, and shared configuration needed to run security tools and collaborate during an audit or review.

A user can belong to multiple organizations, but only one is active at a time in the UI. See Organizations for how to select or switch your active organization.

Why organizations matter​

An organization:

  • Defines the collaboration boundary: members can see and work on the same projects.
  • Scopes access control: permissions, roles, and membership apply at the organization level.
  • Scopes project data: projects, versions, tasks, findings, issues, and threads live inside an organization.
  • Holds shared configuration used by tools (e.g., organization-wide libraries of [V] specs, hints, and detectors).

What an organization represents​

Conceptually, an organization can be associated with a real team or entity working on one or more codebases (e.g., an audit firm, a protocol team, or a client team). It is the "container" for all work in AuditHub:

Organization model​

The organization model is defined by what AuditHub currently uses. Key attributes include:

Identity​

  • Organization name: The name of the organization.

Limits​

  • User limit (optional): The maximum number of users allowed in the organization (support users may not count toward this limit).

Members and access​

The organization model captures who can access the organization and what role they have (e.g., auditor vs. developer). Members can be active or pending (invited but not yet onboarded).

See:

Shared tool configuration​

Organizations can maintain shared libraries used by tools, such as [V] specs, hints, or custom detectors. See Tool Configuration for more details.