Project members
Use the projects their organization role and project membership allow. Owners can manage members, policies and sharing boundaries.
Security
Keep project knowledge inside the boundaries you set.
SPM controls which project, sources and history each person or agent can use. Sharing creates a restricted view with its own permissions, expiry and audit trail instead of exposing the underlying project.
Updated July 30, 2026
Access model
The useful context can move. The project boundary stays in place.
A project member, a coding agent and an external partner should not receive the same view. SPM applies identity, project membership and the sharing boundary before project knowledge is retrieved or packaged.
Connected agents
Receive only the tools and project memory allowed by their connector profile and current task. Billing and destructive administration stay outside the agent surface.
External collaborators
Receive a deliberately shared project view. Internal discussions, pricing, unrelated customers or sensitive sources can remain excluded.
Controlled sharing
Share a project view without handing over the project.
A shared view is a separate access decision. It names the audience, applies exclusions, records the source boundary and can expire or be revoked independently.
- 01
Choose the audience
Share with a named teammate, an invited collaborator or a defined audience without opening the complete project.
- 02
Set the boundary
Include the project knowledge the recipient needs and exclude private topics or sources. The boundary can be described in plain language and reviewed before use.
- 03
Issue restricted access
SPM creates a scoped, expiring and revocable view. The recipient does not inherit access to the original project or its hidden material.
- 04
Inspect and revoke
Operators can see what was shared, with whom and under which boundary, then revoke access without deleting the project memory.
Security controls
Evidence follows the memory through its lifecycle.
Organization and project isolation
The organization is the tenant boundary. Project membership and token scope determine which memory can be queried, composed or shared.
Source and integrity evidence
Retained project knowledge carries actor, source and time metadata. Generated context packs and trust exports include stable hashes for later verification.
Temporal and authority lineage
Original intent, working observations, current decisions and superseded history remain distinguishable. Contributions retain their author and authority context.
Retention and audit controls
Retention settings, deletion workflows, legal holds, access logs and trust exports make the memory lifecycle inspectable by authorized operators.
Deployment boundary
Choose where SPM runs without changing how access is governed.
Hosted and private deployment answer where the service and data are operated. Project permissions, sharing boundaries, source evidence and audit history remain part of the same product model.
Hosted SPM
For teams that want SPM operated as a service.
Organizations and projects remain isolated in the hosted environment. SPM operates the application, storage and connector authorization flow.
Private deployment
For organizations that require dedicated or customer-controlled infrastructure.
The same project, permission, sharing and evidence model runs inside an approved private boundary, with deployment responsibilities defined for that environment.