Setting Up a Portfolio Organization
Create your organization, connect repositories, and run your first portfolio group audit
Setting Up a Portfolio Organization
A portfolio organization is the workspace where investment teams, advisors, and portfolio companies collaborate on group audits across multiple repositories.
For a single-repository audit without a portfolio workspace, import a repository directly from My Audits.
Before you begin
- A CodeDD account
- Git access to target repositories (OAuth, PAT, or SSH — see Repository Connection & Security)
- LOC budget on your account, or a plan to purchase lines during checkout (Common Questions)
Step 1 — Create your organization
On the user dashboard (My Audits), click Create your organization, enter a name, and confirm.
You become the organization initiator with full access to dashboards, audits, and member invitations.
You can also create a billing organization during audit checkout, but portfolio analytics still require creating the organization from the dashboard.
Step 2 — Open the organization dashboard
Navigate to your organization from the dashboard. Initiators and reviewers see portfolio KPIs and audit controls. Submitters can import repositories but do not see portfolio analytics — see Team Members & Access Roles.
Step 3 — Create your first group audit
Click Create New Audit on the organization dashboard.
- Name the group audit (deal name or reporting period).
- Define participants — your team as auditors, portfolio engineers as invitees.
- Send invitations — invitees receive email links to connect repositories and mark audits ready.
Only initiators can create organization-level audits.
Step 4 — Connect repositories
Each invitee (or you, if connecting directly) imports repositories via:
- Git OAuth — GitHub, GitLab, Azure DevOps, or Bitbucket (recommended)
- PAT or SSH where OAuth is unavailable
- CodeDD CLI for local-first audits — CodeDD CLI Guide
After import, CodeDD discovers files and calculates lines of code.
Step 5 — Select audit scope and pay
- Open audit scope selection for each repository.
- Review discovered files and adjust which receive deep LLM analysis.
- Complete checkout if scoped lines exceed your LOC budget.
Purchase additional lines under Account → Billing before or during checkout.
Step 6 — Start the audit
- Invitees mark repositories ready when import and scope review are complete.
- Confirm execution from the group audit workflow.
- Track progress on the organization dashboard.
When processing finishes, portfolio tabs unlock: benchmarks, technical debt, security, architecture, dependencies, development insights, and PDF export.
Step 7 — Invite your team (optional)
From Manage Access, invite colleagues as Reviewer (full report access) or Submitter (repository import only). Up to 10 email addresses per batch.
Details: Team Members & Access Roles.
Troubleshooting
| Issue | What to try |
|---|---|
| No Create New Audit button | Confirm you are an initiator |
| Import fails | Verify Git credentials — Repository Connection & Security |
| Checkout blocked | Top up LOC under Account → Billing |
| Submitter cannot see KPIs | Expected — assign Reviewer for dashboard access |
| CLI audit not appearing | Run codedd auth status and confirm sync completed |