How Patchnet Projects is organized

This page explains the main ideas in Patchnet Projects, for anyone who wants to know how the pieces fit before they build.

Workspace

Your organization has its own workspace: its own sign-in, its own members, and its own data. Everyone in your organization works in the same workspace. Other organizations cannot see into it.

Projects

A project is a container for one area of work — a client program, a sales pipeline, a team's operations log. It is also the access boundary: you grant people and agents access one project at a time.

Every project has a path that shows who it is for:

• my/private/<name> — your personal projects. Only you can see them unless you share them.
• org/shared/<name> — team projects. Members of your organization can find and use them. This is the usual place for shared work.
• org/private/<name> — team projects that an admin controls. Only people added to them can see them.

Each member also gets a personal journal at my/private/journal for quick capture, notes, and drafts.

Records

A record is one durable item in a project: a decision, a task, a client, a case note. Each record is a readable document with two parts:

• Fields at the top — structured values such as status, owner, due date, or client.
• Body below — the plain-language content.

Records keep a history of who created and last changed them, including which agent made a change.

Record types

Each project defines its own record types and the fields each type has. For example, a client-services project might have clients, contacts, cases, and case notes. Every project starts with a small set of common types — entries, tasks, decisions, and knowledge — and you add the types your work needs.

Record types keep records consistent. When an agent files a case note, it fills in the same fields every time, so you can filter, count, and report on them later. See Design a project with your agent.

Roles

Access is set per project. There are four project roles:

• Reader — find, open, and search records.
• Writer — everything a reader can do, plus create and update records.
• Admin — everything a writer can do, plus share the project and view its activity.
• Owner — everything an admin can do, plus change the project's record types.

See Roles and access for details.

Agents

An agent is an AI assistant that works in your projects. You can use the agent built into Patchnet Projects, or connect your own AI tool over MCP. Either way, the agent acts as you: it can only see and change what your role allows.

The model is the underlying AI model an agent runs on. Your workspace admin chooses the default model for the built-in agent.

See also

• Quick start
• Roles and access
• Connect your AI tool