Team sharing

Go to Settings → Organization and click Create organization. Enter a display name and a URL-safe slug (lowercase letters, digits, hyphens). The slug must be globally unique.

You become the org's owner automatically.

From the same page, enter a GitHub handle or an email address and pick a role. Only admin and owner can invite.

• An email invite sends a transactional notification (if Resend is configured).
• A handle invite is in-app only — the invitee sees a banner on their Overview.

Invites are secured by identity: when someone accepts, the new membership is bound to their verified auth.uid() — a forwarded invite email can only be redeemed by the identity it was addressed to.

Agents write org-owned lore by passing the org slug on memory.write:

memory.write {
  scope:  "repo::myteam/api",
  key:    "deployment-checklist",
  value:  "Always run smoke tests on the staging env before promoting to prod.",
  org:    "my-team"          // org slug
}

Authorization is derived server-side — the write is accepted only if the caller is a write-capable member. A viewer or non-member is rejected.

Instead of passing org on every write, an admin can bind a scope to the org so writes auto-route:

Go to Settings → Organization → Shared scopes → enter a scope string (e.g. repo::myteam/api) → click Bind scope.

After binding, any write under repo::myteam/api by a write-capable member routes to the org automatically. A non-member writing under a bound scope gets a graceful fallback to personal lore (never rejected) with a notice in the response.

In the Explorer, use the All · Personal · {org} filter to narrow to your org's lore. Org-owned memories show an ownership badge next to the scope badge. The detail panel shows the owning org and who last updated the memory.