Team Collaboration & Governance

Team work in Phasoric has two deliberately separate layers: ephemeral live editing and durable knowledge-centered discussions, reviews, mentions, and activity.

Work Together on a Note

1. Add teammates and set roles under Settings → Workspace collaboration & governance.

2. Open a note and use Note inspector → Team discussions.

3. Anchor a discussion or review to the whole note, a Markdown heading path, or a portable block ID.

4. Mention current workspace members explicitly, assign a reviewer, and resolve or reopen the thread when the work changes.

Phasoric fingerprints anchored content. If the referenced section changes or its heading path disappears, the inspector marks the anchor as changed or missing instead of silently presenting old context as current.

What Persists

• Discussion subjects, comments, explicit mentions, assignments, review states, and resolve/reopen actions are durable hosted records.
• Note and workspace activity entries form a durable audit trail and state changes commit with their activity entry.
• Live editor awareness, name, color, role, and connection state, travels through Yjs awareness and is not written to the collaboration ledger.

Access Boundary

• Durable anchored discussions require the Team & Collaboration plan and current workspace membership.
• Viewer can read workspace knowledge and activity. Commenter adds anchored discussions and replies. Reviewer also requests and completes assigned reviews. Editor adds note/metadata editing, live Yjs sessions, automation management, Forge review, and public sharing. Workspace Admin manages non-admin members, assignments, and policy for that workspace. Workspace Owner alone can grant or manage Workspace Admin access.
• Live relay rooms use server-issued, one-time, 90-second grants. Room IDs are HMAC-derived so note paths are not exposed in the transport URL.
• Membership and Editor-or-higher permission are checked when a writable grant is issued and consumed, then membership is rechecked during the active session. Role or membership changes revoke outstanding grants.
• Mentions accept current workspace member IDs only. Workspace Owners and Workspace Admins control assignments; assignees must have Reviewer access or higher.

The workspace activity feed composes anchored discussion events with governance events such as member role changes, decision reviews, policy changes, and public-share operations. It remains bounded, attributable, and separate from ephemeral presence.

Phasoric collaboration stays centered on knowledge and review. It is not a general-purpose team chat system, and no persistent presence history is created.