Organizations

An Organization is the Enterprise shape of TDE: one owner, a roster of developers, a shared Organization Brain and one place where the owner can see what the team shipped and what it cost.

Everything below assumes an active Enterprise subscription. Buying one creates the organization, its database and its Organization runtime automatically.

Roles

Ownership is the account that holds the Enterprise subscription. It is not a role another member can be given: promoting someone to admin never grants access to the reports below. That is deliberate — the promise a developer gets is that their teammates cannot browse their work, and only the person who owns the bill sits outside it.

Projects

Before deliveries can be reported under a human name, the repository has to be bound to the organization from the TDE desktop. Binding registers the project's canonical host/owner/repository key together with a display name and the developer who bound it.

Registration is idempotent: any number of developers can bind the same repository, the display name is refreshed, and the original binding is kept as the historical record. The attribution is taken from the authenticated license, so it always names the developer who actually performed the binding.

Registered projects are listed under Account → Organization → Projects. Every active member sees the list; only the owner sees who bound each project (you always see your own).

Organization reports

Account → Reports → Organization is the owner view of the team's month. The tab only exists for accounts that own an active organization; for everyone else it is not rendered at all.

The report is built from the finished-work items your team publishes to the Organization Brain — stage recaps, pull-request pointers and decisions.

Filters. Organization (when you own more than one), month, member and project. Every filter lives in the URL, so a filtered report can be bookmarked or shared with another owner. Month navigation only offers months that actually contain deliveries.

What it shows.

• Totals — deliveries, distinct tasks, pull requests and active members.
• By member — deliveries, tasks, PRs and last delivery for each member, including members who have not shipped yet.
• By project — the same figures per registered repository.
• Recent deliveries — the 50 most recent items with their kind, task, stage, pull request, author and date.

What it does not show. The report carries titles and metadata only. It answers that work happened and where, and never turns a dashboard read into a bulk export of recap bodies. Reading a body is a separate, deliberate act — see below.

Organization knowledge on the Brain page

Account → Brain → Organization is where the owner reads what the team published. It is the same owner-only boundary as the report — membership is not enough and neither is admin — and it exists for the opposite need: the report counts deliveries, the Brain page opens one of them.

What the owner can read. The consolidations members published at stage completion: stage recaps, pull-request pointers and decisions, searchable by title and body, filterable by author, project and kind. Opening one shows its published body as plain text, together with its task, stage, pull request, author and checksum.

What stays private. A member's personal Brain. It lives in that member's own Sync database and no organization surface can reach it — not the report, not this page, not the owner. Only what a member deliberately publishes when a stage completes ever reaches the Organization Brain.

TDE Pass spend

When your team uses TDE Pass, the report also attributes spend to the organization's projects for the selected month. The figures come from the billing gateway, are restricted to the registered project keys, and are broken out per member and per project alongside the delivery counts. Cost is shown in US dollars.

Usage is an addition to the report, never a precondition for it:

• If the gateway cannot be reached, the delivery figures still render and the spend section reports itself as unavailable.
• If one member's usage cannot be read, that member's spend shows as — and the report says the totals are incomplete, rather than quietly counting them as zero.
• Work done outside the registered projects is not attributed to the organization.

Related

• Brain memories — browsing your own memories and your organization's published knowledge on the website.
• Licensing and sync — activating devices and the leases that keep a fleet consistent.
• Brain, decisions and recall — what the Organization Brain stores and how deliveries get there.
• Pricing — what an Enterprise subscription includes.