LibraryIf something lands in the wrong organizationv1 · Updated Report

If something lands in the wrong organization

Use this when an agent or a person wrote something into an organization whose readers should not see it: personal notes in a team organization, one client's material in another client's organization, internal plans in a public one. It is a recommendation; the person whose material it is decides what happens to it.

Act in this order

  1. Stop writing there and say what happened. Tell the person what landed where, and who can read that organization: its members, or anyone when it is public.

  2. Put it where it belongs first. Copy the document into the right organization with the explicit copy operation, or rewrite it there, and check that the copy is complete. A copy carries no history, comments or links from the original.

  3. Delete it from the wrong organization. Archiving is not enough: an archived document stays readable to every member. A deleted document goes to the trash, where members can restore it for 30 days; after that its content is removed for good. Deletion is not an instant erasure from every backup or derived record (Ownership, portability, deletion, and retention). When 30 days is too long for the material, ask Oddlynew whether it can be removed sooner.

  4. Clean up what still carries it. A passage written into another document of that organization, a comment, or the anchor text of a link that cites the material is not removed with the document; edit those too. When the material went into an existing shared document, removing it from the current text leaves it in that document's earlier versions, which members can read; ask Oddlynew whether those versions can be removed.

  5. Tell the person who could read it. Say plainly who had access and for how long. The person decides whether to tell anyone else.

  6. Prevent the next one. Add a line to the organization's AGENTS.md that names what does not belong there and where it goes instead (Write a useful AGENTS.md). Agents read it before they write.

Why it happens

An agent usually works inside one organization and treats it as home, so its results drift there even when they are meant for other readers. The fix is a check before every write: which organization, and who can read it. When material looks sensitive and the right readers are unclear, the agent asks the person which organization it belongs in before writing (Work across several organizations).

Oddlynew PublicSign in

Referenced by