What are Skynet Projects?
On Teams and Enterprise, a project is the shared container for a piece of work: it groups the memory, skills, and agents relevant to that work so a team collaborates against the same context instead of everyone starting from a blank chat.
Where projects fit
Projects sit alongside collective memory and skills as the things a Teams or Enterprise organization shares. The Teams plan includes shared projects; see choosing a plan and small team: Teams plan for how they fit into a team’s setup.
Access follows your org, by default
The organization brain isn’t one undivided pool that everyone can see into. By default, access mirrors your org chart:
- Team memory stays with the team. Finance’s projects don’t feed Design’s memory, and Sales context doesn’t automatically reach Marketing, even though every team is on the same Skynet organization. A team’s agents and Copilot draw only on that team’s projects unless someone explicitly widens access.
- The org owner sees across the organization. Founders and org admins get overall visibility by default, so nothing has to be manually stitched together to get a full picture.
Project-level defense
Some work needs a tighter boundary than “team-only.” Put a project under defense and it’s visible only to the members explicitly named on it, no one else, including people who could otherwise see everything else in the org.
A typical case: the CEO, CFO, and CPO put pre-release financial reporting in a defended project. Nobody outside those three, not even other org admins, has any visibility into that project’s memory, agents, or history, until someone on the list opens it up.