How do I use Journeys with my team?

Use a Journey for a shared goal and separate Socras for the decisions, drafts, or deliverables the team needs. Give each Socra an assignee and keep its status current.

Confirm access first

Teammates need access to the Account and to the relevant Journeys work. An Account owner manages membership in Admin under Directory → People. Adding a person can affect Workspace seat charges; check the Account's billing before adding members.

Journey access is separate. Review Privacy, Space permissions, and direct sharing. Choose a role that fits the work: Viewer for reading, Commenter for discussion, Editor for changing the work, and Admin for managing its access.

An Admin role on a Journey does not make that person an Account owner. Confirm that a teammate can open the Socra before assigning it. Assigning a person is not a substitute for granting access.

Keep the shared background current

Put the goal, constraints, and established decisions in Journey Context. Each Socra keeps the conversation for its own piece of work. A teammate with Commenter access or higher can post updates and reply in the conversation. Use No AI when the update does not need an AI response.

Assignments and mentions can produce notifications. Check the intended person before submitting them.

When the work reaches a decision, state it and its reasons in the conversation. Marking the Socra Resolved can update Context on resources where AI Context Updates is enabled. Review the Memory updated event and resulting Context before the team relies on it.

When someone leaves the work, review direct shares and inherited access with the resource owner. Removing one direct share does not remove access supplied elsewhere.