Organization guidance
Set shared rules and working defaults once. Give authorized work a consistent reference for how the organization operates.
Context OS / Teams
Bring the reasoning behind the work into a shared record, with clear guidance and access for the people who need it.

01 Shared with intention
Shared work needs more than a collection of chats. Keep the guidance, the project record and the responsibility for changes clear.
Set shared rules and working defaults once. Give authorized work a consistent reference for how the organization operates.
Keep scope, decisions, open questions and handoffs together. Make the reasoning available to the people with project access.
Use the applicable approval policy to control updates. Where review is required, assess a proposed change against the current record.
Each layer has a different job.
Organization membership and project access are separate.
02 Keep the reasoning connected
A planning session settles the pilot scope. A teammate takes over delivery. With project access, they can start from the agreed direction, see the open questions and carry the next step forward.
A compatible agent with permission can use that same project context. Proposed updates that require approval are reviewed before becoming part of the record.
Explore capture, review & continueDecision: Start with a three-site pilot before committing to a production run.
Why: Installation effort and calibration support need to be understood at real customer sites.
Who will own calibration and support at each pilot site?
Engineering: compare the two shortlisted sensors and prepare the pilot checklist.
03 A deliberate way in
Start with an individual account, then join an organization by invitation. Organization creation depends on your plan’s permissions.
View plans & create an accountAn organization owner invites you. Signing up alone does not enroll you in an organization.
Organization membership does not grant access to every project. Project permissions determine who can view or edit.
Authorize compatible tools within the access available to you. Local organization sync also requires the applicable approvals.
04 Clear responsibilities
Keep organization guidance and project permissions distinct. Review who should participate in each project.
A changed record requires a fresh proposal. Approval applies to the revision being reviewed.
Client compatibility, requested permissions and approval presentation vary. Connect tools with the access the work needs.
Make the direction clear before the work changes hands.
Compare plan details for organization creation and available capabilities.