Organization
An Organization is the top-level tenant in AISafe. Assessments, findings, reports, integrations, team members, and billing all live inside an organization. You create your first organization on sign-up. You can belong to multiple organizations if you work across teams or companies.
Your organization contains projects, each of which owns a source and can run continuous capabilities. AISafe tracks and bills the credits funding this activity at the organization level. See Credits & billing.
Identity
Each organization has a human-readable code (e.g. ACME) that becomes part of each assessment and finding ID in the system. An assessment for the Acme organization might carry the ID AIS-ACME-TLP, and a finding on that assessment would be AIS-ACME-TLP-001. These IDs are immutable and appear in URLs, reports, CSV exports, and support tickets.
Members and roles
Each organization member receives one of four roles: owner, admin, manager, or member. The role determines what a member can do across the organization. See Getting Started → Invite your team for the full role overview.
| Role | Key capabilities |
|---|---|
| Owner | Full control: billing, member management, integrations, organization deletion. The organization requires at least one owner. |
| Admin | Manage members and integrations, configure organization policies, create and manage projects. |
| Manager | Create assessments, triage findings, run reports. Cannot manage members or billing. |
| Member | Read-only access to assessments, findings, and reports within their team scope. |
Teams
Teams group members for assessment access control. You can bind a team to specific repositories via integration connections, which scopes what that team can see and run. For example, the frontend team sees frontend repos, the backend team sees backend repos. Each team sees its bound repositories. A member belonging to multiple teams inherits the union of those teams' access.
Custom roles
Owners can create custom roles with scoped permissions beyond the four built-in roles. A custom role lets you grant a subset of capabilities. For example, you can give a compliance auditor report-only access, or give a developer assessment-creation rights without finding triage. You manage custom roles under Settings → Roles and can assign them to any member like a built-in role.
Organization policies
Organizations can enforce policies including personal GitHub connection permissions, admin approval requirements for personal Git connections, and SLA windows for finding remediation. Owners and admins configure these under Settings.