# Support Direct answers to questions about Socra products. Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/ Canonical index: https://support.socra.com/llms.txt ## Author a context module Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01kzvan6gk8ndbxakrc0ddmvtx-author-context-modules A module is a persistent, named, versioned specification of what should be. Its content stays upstream from the code and other artifacts that consume it. ## Find the owner first Search before you propose a new module: ```sh socra cortex module search --query "topic" socra cortex map ``` Update the existing owner when one module already owns the concept. Create a new module when the concept has a distinct durable identity. ## Write the specification Keep the content abstract. State the interface, rules, constraints, and reasons that future work must honor. Leave implementation logs, file paths, incident history, and copied source code out. Add a dependency when a reader must understand another module first. Dependencies form a directed comprehension graph. Cortex rejects cycles. ## Get exact approval Show the owner the exact proposed content and dependency changes. Wait for clear approval of that text before you write. Owners must understand every sentence in the modules they own. After approval, create or update the module: ```sh socra cortex module create --name example --content-file module.md --deps foundation socra cortex module update example --content-file module.md --deps foundation ``` Read the result back and flash it to verify the full context: ```sh socra cortex module get example socra cortex flash example ``` ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-12 - Updated: 2026-08-12 - Canonical: https://support.socra.com/articles/art_01kzvan6gk8ndbxakrc0ddmvtx-author-context-modules --- ## Flash modules for a task Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01kzvan6k1a6nvapsmqn0cmzah-flash-modules-for-a-task Flash loads a target module and its full dependency graph into one context bundle. Cortex walks the graph transitively, removes duplicates, and orders foundations before the target. ## Flash before work When you know the owning module, run: ```sh socra cortex flash module-name ``` Read the complete bundle before you change the system. Use it as the source of intent and constraints. Verify current code, services, permissions, and other external state separately because those facts can change after a module was authored. If you do not know the module name, inspect the graph or search: ```sh socra cortex map socra cortex module search --query "topic" ``` If no relevant module exists, continue the task without inventing one. Propose durable knowledge only when it will improve future decisions. ## Fix stale CLI symptoms Cortex CLI is a thin client over the live service. A stale client can show a blank inbox, truncated module lists, or malformed reads. Update first, then retry the same command: ```sh socra update socra cortex flash module-name ``` ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-12 - Updated: 2026-08-12 - Canonical: https://support.socra.com/articles/art_01kzvan6k1a6nvapsmqn0cmzah-flash-modules-for-a-task --- ## Get started with Cortex Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01kzvan6dvffsepc8p9nv25s34-get-started-with-cortex Cortex gives your account one graph for durable knowledge and work. A module records what should be. An issue records work that moves the system toward that specification. Flash assembles the knowledge that an agent needs for the task. ## Prepare the CLI Sign in and install current Socra CLI packages: ```sh socra account login socra update ``` ## Start from the work Cortex uses a pull-based flow. Begin with the task you need to complete. Then look for relevant account knowledge: ```sh socra cortex map socra cortex module search --query "your topic" ``` If a relevant module exists, flash it before you act: ```sh socra cortex flash your-module ``` A new account starts with an empty graph. Continue the task when no module exists. Do not create sample modules or invent account knowledge. ## Keep durable knowledge with permission When a conversation reveals knowledge that will improve future decisions, propose the exact module change to its owner. Write it only after the owner approves that exact text. This keeps each module understandable and trustworthy. ## Coordinate work Use the inbox to see released work that belongs to you: ```sh socra cortex inbox ``` Use `socra cortex issue` and `socra cortex comment` to inspect work and add progress. Issue timelines preserve status changes and authored comments. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-31 - Updated: 2026-08-12 - Canonical: https://support.socra.com/articles/art_01kzvan6dvffsepc8p9nv25s34-get-started-with-cortex --- ## How do I keep Modules current as my systems change? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m14zfqe1asv76cak19t3df27-keep-modules-current Most Module updates can come from the work you already do with your agents. When you explain a changed decision or correct an agent, the agent can find the existing Module and propose an update. A Module records what should be true and why. The repository and running system provide evidence of the current implementation. Before acting, the agent should flash the relevant Module and inspect that evidence. When they differ, decide what needs correction: - If the Module still describes your intended direction, keep it and correct the implementation. - If your direction changed, approve an exact Module update. Then check the affected systems against the new version. - If the work exposes missing knowledge that will matter again, add it to the narrowest Module that owns the subject. An agent can draft changes to the content and dependencies. It shows you the current text and the proposed text before saving anything. The Module owner can approve, revise, or reject the proposal. You can also update Modules directly at [cortex.socra.com](https://cortex.socra.com) or with the Socra CLI. Cortex creates an immutable version each time Module content or dependencies change. A new flash returns the current active version of every Module in the dependency tree. Flash history records which versions Cortex delivered to the agent. A flash is a snapshot. Cortex does not replace knowledge already loaded into an active agent session. If a Module changes after an agent flashed it, have the agent flash it again before continuing. Cortex does not continuously scan your repositories or decide that a Module is stale. Give your agents a standing instruction to surface lasting knowledge when they encounter it and propose the exact Module change. If a system changes outside those agents, include the related Module in the review for that change. When a Module no longer applies, archive it. Cortex preserves its content and history. It blocks the archive while active Modules or Issues still depend on it, or while an enabled Issue Schedule uses it. An archived Module leaves the active knowledge graph and cannot be flashed until it is restored. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m14zfqe1asv76cak19t3df27-keep-modules-current --- ## How do I try Cortex with my existing development process? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m14xx2e6decqcwzdcs8kpcvs-try-cortex-existing-development-process Cortex gives the agent you already use your approved knowledge before implementation begins. Connect the agent through the Socra CLI or a compatible MCP client. Before it plans or edits code, have it flash the Module that owns the subject. Cortex returns that Module and every declared dependency, with foundations first. A Module describes what should be true and why. The repository shows the current implementation. The agent still reads the repository instructions, inspects the code and history, runs the repository’s checks, and verifies current behavior. You can use Modules without moving work into Cortex Issues. A flash needs only a Module name. If you use Cortex Issues, each Issue describes one piece of work and names its owning Module. This gives the agent a direct route from the work to the knowledge it needs. Cortex does not automatically synchronize Cortex Issues with an external tracker. Your existing tests, CI checks, branch protections, review requirements, and deployment approvals continue to control what ships. Cortex does not run those checks or approve a merge. Builders and reviewers can flash the same Module before they inspect the change. Module history records each saved version. Flash history records which Module versions Cortex delivered. It does not automatically link a flash to a commit, CI run, or deployment. ## A low-risk pilot 1. Choose one repository and one recurring decision that agents need to apply. Use a reversible change in an area already covered by tests. 2. Create one Module at [cortex.socra.com](https://cortex.socra.com) or with the Socra CLI. State what should be true and why. Keep its dependencies small. Review the Module and everything it depends on before granting access. 3. Connect one agent through the CLI or MCP. Limit its Cortex access to the knowledge selected for the pilot. If the agent uses a separate Cortex identity, the Viewer role is enough to flash the Module. 4. Put the flash step in the instructions that the agent reads for the repository. For example: “Before changing this area, flash `` in Cortex and read the complete result.” 5. Leave the agent’s repository, merge, and deployment permissions unchanged. Run the change through the same branch, CI, and review process you already use. 6. Have the reviewer flash the same Module. Confirm that Cortex recorded the flash. Review the change and its evidence as usual. 7. If the pilot uncovers knowledge that will matter again, let the agent propose the exact Module change. The owner approves, revises, or rejects the proposal before the agent saves it. Repeat the pilot with real work. Check whether the agent used the Module, applied the knowledge correctly, and produced the evidence the reviewer needed. Expand to another subject after your existing checks continue to catch implementation problems and the Module changes the agent’s work as intended. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m14xx2e6decqcwzdcs8kpcvs-try-cortex-existing-development-process --- ## How do I use Journeys with my team? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19rdzhn7yrveffd184wnhzr-how-do-i-use-journeys-with-my-team Use one shared Journey for a shared goal, then give each decision, draft, or deliverable its own Socra. The Journey carries reusable context between them, while each Socra has its own assignee, status, priority, content, and conversation. ## Add your teammates Only the Account owner can add people to the Account. In Admin, open People, select Add member, and send the invitation. After the person accepts it, share the Journey with them or let its Space permissions provide access. Before assigning a Socra, make sure the person can already access it through the Space or a direct share. Assigning work does not grant access by itself. ## Choose the smallest role they need Use Viewer for reading, Commenter for discussion, Editor for hands-on work, and Admin for people who should manage that Journey's access and privacy. Admin is a role on that Journey. It does not let someone add people to the Account. The Journey owner retains full control. ## Work from shared Context Put the shared goal and constraints in the Journey Context. Create separate Socras for the work the team needs to complete, then use the assignee, status, and priority to make ownership and progress clear. Teammates with Commenter access or higher can post updates, reply in threads, and mention one another. Assignments and mentions appear through the inbox and notifications. When a Socra is Resolved, facts and decisions established by the team can update the Journey Context if AI Context Updates is enabled. Later Socras can use the updated Context. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19rdzhn7yrveffd184wnhzr-how-do-i-use-journeys-with-my-team --- ## How does Journeys remember my work? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19rdzhq7bhmxtxm6600bywc-how-does-journeys-remember-my-work Each Socra keeps its content and conversation. When you mark a Socra Resolved after you or a teammate has added to its conversation, Journeys can compile durable knowledge from that work. It can update the Socra and the Context of its parent Journeys and Space wherever AI Context Updates is on. Later agents can use relevant Journey and Space Context without asking you to repeat the full history. ## What becomes reusable Context Journeys can keep facts, decisions, reasons, constraints, corrections, and open risks that you or a teammate established in text. AI replies help during the conversation, but Journeys does not promote an unsupported AI-only point into durable Context. It does not copy the whole conversation into each parent Journey. Files and images can help the agent during the conversation, but the attachment itself is not copied into durable Context. State or confirm in text any fact or conclusion that later work must reuse. ## Control Context updates AI Context Updates is on by default on each Socra, Journey, and Space. Each switch controls only that resource. Turn it off on every resource whose Context the agent must not change. When Context changes, the Socra timeline shows a Memory updated event. You can see what changed and where it came from, then edit the affected Context if needed. ## Correct outdated Context Editing or trashing the original Socra does not recalculate Context already written to a parent Journey or Space. Open each affected resource and edit its Context directly. Version History lets you restore an earlier version. Later resolved work can replace an outdated point when new human evidence addresses the same subject and scope. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19rdzhq7bhmxtxm6600bywc-how-does-journeys-remember-my-work --- ## How is Journeys different from an AI chat? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19m5dvj36cde0h7r76qemad-journeys-vs-ai-chat Journeys keeps an AI conversation connected to the larger body of work it belongs to. Each conversation belongs to a Socra, which holds one problem, decision, draft, or idea. A Journey connects related Socras and gives them shared context. Later Socras can use relevant knowledge from finished work while each conversation stays attached to the Socra that produced it. ## How the agent works The agent in a Socra works toward the result you ask for. For a decision, it identifies the assumption that determines its recommendation and states what evidence could change it. When another perspective could change the result, the agent can consult one relevant specialist and return one integrated response. You do not need to select several agents or combine their replies. ## What later Socras remember When AI Context Updates is on, finishing a Socra lets Journeys prepare durable context for later work. That context can include facts, decisions, corrections, and judgment that you established. Agent-generated content enters it only after you accept it, correct it, or act on it. You can turn AI Context Updates off for a Socra, Journey, or Space. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19m5dvj36cde0h7r76qemad-journeys-vs-ai-chat --- ## How much work does it take to get value from Modules? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m14wdb07yryx9qt1h617vk9t-get-value-from-modules There is no required number of Modules. Start with knowledge that an agent needs for real work, such as a decision you keep explaining or something agents often get wrong. You can create that Module yourself on [cortex.socra.com](https://cortex.socra.com). Open **Modules**, select **New module**, and write what should be true. You can also add its dependencies there. Your agents can do the writing with you. Continue working with them as usual and explain what should be true when the subject comes up. If the knowledge will matter again, an agent can suggest a new Module. If an existing Module already covers the subject, it can suggest an update. The agent shows you the exact proposed text before changing anything. For an update, it shows the current text and the proposed text. You can approve, revise, or reject it. Cortex preserves the change after you approve it. Your work is to provide judgment. You decide what should be true and explain the context future agents will need. You can write Modules directly when you want full control, or let your agents draft and maintain them as knowledge emerges through your work. Cortex becomes useful when an agent flashes a relevant Module before acting. Even one Module can stop a repeated mistake or save you from explaining the same decision again. As you continue working, you and your agents can add or update Modules when useful knowledge emerges. Your knowledge base grows through real work at the pace your systems require. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m14wdb07yryx9qt1h617vk9t-get-value-from-modules --- ## Troubleshoot Socra Cortex Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01kzvan6tqbp0wznh0p9zdxphc-troubleshoot-cortex ## The inbox is blank or a list looks incomplete Update the CLI, then retry the exact command: ```sh socra update socra cortex inbox ``` Client and service version skew can produce blank inboxes, truncated lists, or malformed reads. ## A module cannot be found Check the graph and search by topic: ```sh socra cortex map socra cortex module search --query "topic" ``` A new account starts empty. Continue your task when no relevant module exists. Propose the first module only when you have durable account knowledge and exact owner approval. ## A flash contains more modules than expected Flash includes every transitive dependency. Inspect the target with `socra cortex module get module-name` and use `socra cortex map` to review its edges. ## A module write is refused Confirm that the signed-in account can edit the module. The module owner must approve the exact content and dependency change before an agent writes it. ## An issue is blocked Read the issue and its timeline: ```sh socra cortex issue get issue_id socra cortex issue timeline issue_id ``` An open dependency keeps the issue out of the ready set. Close completed work as done. Add a resolution comment before canceling work that will not be completed. ## MCP returns 401 or 403 A 401 response means the client needs a current account-scoped OAuth authorization. Reconnect the remote MCP server and complete browser sign-in. A 403 response means the authenticated account or principal lacks permission for that operation. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-12 - Updated: 2026-08-12 - Canonical: https://support.socra.com/articles/art_01kzvan6tqbp0wznh0p9zdxphc-troubleshoot-cortex --- ## What can I use Journeys for? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19rdzhn7vgmn1qq1m3pzt85-what-can-i-use-journeys-for Use Journeys to decide, answer difficult questions, improve drafts, develop plans, or work through ideas. Each Socra keeps one piece of work with the conversation and context that produced it. Related Socras can share background through a Journey. ## Common uses - Compare options and make a decision. - Research a topic and form a recommendation. - Develop a strategy, experiment, or project plan. - Draft or revise an article, proposal, report, or chapter. - Work through a client problem, product question, or coaching goal. ## Start with what you have Tell the agent what result you want. Add any constraints, evidence, tradeoffs, earlier attempts, or conclusions that could affect the result. Rough notes are enough. You do not need a special prompt. Start with text. You can also attach a file or image, record a voice message, or give the agent a URL to read. Ask it to search the web when the work needs outside or current evidence. ## Organize related work Put related Socras in a Journey when they contribute to the same goal. Add background that later work needs to the Journey Context. A sub-Journey can give one part of the work its own goal and Context. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19rdzhn7vgmn1qq1m3pzt85-what-can-i-use-journeys-for --- ## What data leaves my environment when I use Cortex, and who can access it? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m14gt0czfnn9pgc5xbdtgyj9-company-data-and-proprietary-knowledge Cortex is a Socra-hosted cloud service. Information leaves your environment when you or your agents create or update resources in Cortex. ## What Cortex receives Cortex stores the resources submitted to it: - Module content and version history - Module dependencies - Access-control grants - Issues and comments - Flash records, including the requested Module, included versions, caller, and usage metadata Installing the Cortex CLI or connecting the Cortex MCP server does not cause Cortex to scan or upload your repository. Cortex receives only resources that you or your agents submit. An agent may inspect source code as part of its own task. That activity happens at the agent boundary, outside the Cortex service. Any information the agent sends to its model provider is governed by the agent's configuration and your agreement with that provider. ## How Cortex isolates customer knowledge Your Socra Account is the tenant boundary. Cortex derives the Account from the authenticated credential. A client cannot supply a different Account ID to reach another tenant. Every Cortex resource is scoped to that Account. We enforce the Account boundary on reads, writes, searches, and dependency traversal. Cross-account resources are returned as not found. This is logical tenant isolation enforced by our authorization and data-access layers. It is not a dedicated customer database or private deployment. ## How you control access Each Module is its own authorization boundary. You can grant access to individual people, application identities, or groups. - **Viewer:** Can read and Flash the Module - **Commenter:** Has viewer access and can comment - **Editor:** Can change Module content and dependencies - **Admin:** Can manage the Module's access policy - **Module owner:** Has full control A child Module can inherit its parent's access policy or use an independent policy. Assigning someone an Issue gives them access to that Issue, not to the owning Module. Account ownership does not provide routine access to every Module. The Account owner has break-glass authority to repair an invalid access policy. Within Socra, customer content is available only to personnel who need it for support, service reliability, safety, or legal obligations. ## What a Flash can disclose When someone is authorized to Flash a Module, Cortex returns that Module and its complete dependency closure. Cortex authorizes the requested root Module once. It does not run another access check for every dependency in that Flash. Adding a dependency is therefore a disclosure decision. Anyone who can Flash the parent can receive the dependent Module's content as part of the assembled context. Creating the dependency requires access to both Modules. Receiving a Module through a parent's Flash does not grant direct access to that dependency. ## Storage and model processing We store and process Cortex data on cloud infrastructure in the United States. Cortex does not call a model API when it stores, searches, versions, or flashes Modules. If an authorized agent retrieves Cortex knowledge, that content enters the agent's session and may be processed by the model provider configured for that agent. We do not sell customer data or use customer content to train models. Module knowledge is versioned. Archiving a Module removes it from active use but is not an erasure mechanism. Credentials, private keys, and review secrets should never be stored in Modules or Issues. We do not currently offer customer-managed encryption keys, regional data residency, or a private or self-hosted Cortex deployment. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m14gt0czfnn9pgc5xbdtgyj9-company-data-and-proprietary-knowledge --- ## What is a Journey? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m18d3v90ma204hr0fr099paz-what-is-a-journey A Journey carries the goal and context around related thinking in Socra Journeys. Each Socra inside it focuses on one problem, decision, draft, or idea. New Socras can use relevant Context from their parent Journey. When you mark a Socra Resolved after you or a teammate has added to its conversation, Journeys can update the Socra and the Context of its parent Journeys and Space wherever AI Context Updates is on. ## What a Journey keeps Journey Context can include the larger goal, its constraints, relevant background, prior decisions, and the evidence behind them. Resolved work can add facts, decisions, reasons, corrections, and open risks established in text. The Socra timeline shows a Memory updated event when Context changes. You can inspect the source and changes, then edit the affected Context if needed. The conversation remains with the Socra that produced it. Later Socras can use the relevant Journey Context without asking you to reconstruct the same background. ## How related work stays connected A Journey can contain Socras and smaller sub-Journeys. Context flows into the work inside it. Resolved work can then improve the Journey Context that later Socras receive. Use a Journey when several decisions, questions, or drafts contribute to the same larger pursuit. That could be a book, thesis, client engagement, product direction, or another body of work where each part should use what the earlier parts established. ## Creating a Journey You can create a Journey directly in [Socra Journeys](https://journeys.socra.com/) and add Socras or sub-Journeys to it. You can also ask the agent to create one. Once the subject of a Socra is clear, the agent may suggest an existing Journey or a new one when shared Context would help future work. It does not create or move anything until you approve it. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m18d3v90ma204hr0fr099paz-what-is-a-journey --- ## What is a Socra Account? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m15cp3pgg0tden7vnsahwjar-what-is-a-socra-account A Socra Account is the boundary for one organization’s members, access, billing, and resources in Socra. Each Account has a name, a unique handle, and its own directory of people, agents, installed apps, and groups. Your Socra ID identifies you across Socra. An Account membership connects your Socra ID to one Account and gives you a role there. One Socra ID can belong to multiple Accounts. When you open a product or switch Accounts, Socra issues an access token scoped to the selected Account and the person, agent, or app acting inside it. Account-scoped services use that scope to decide which records can be read or changed. ## What belongs to an Account - Cortex Modules, Issues, access grants, and flash history. - Cloud Projects. Each Project then scopes its enabled services, credentials, and usage. - Subscriptions, product licenses, and seat assignments. - The Account directory, including its people, agents, installed apps, and groups. These resources stay within their Account. A directory user or group from one Account cannot be used in another. ## How membership works Each membership has one role: owner, admin, member, or guest. Owners manage Account settings, billing, product access, invitations, member roles, and every group. Admins can administer every group. Members can create and manage groups they own. Guests have limited access and cannot create groups. Creating an Account makes you its first owner. You can also join an Account through an invitation. The Socra ID that accepts the invitation receives the membership. Leaving an Account removes your access to its resources. Your Socra ID and other Account memberships remain active. Every Account must keep an active owner. The last owner must transfer ownership to another active member or delete the Account before leaving. ### Article details - Collection: [Account](https://support.socra.com/collections/col_01kzpmz5b5xgewtk030mkfefv8-account) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m15cp3pgg0tden7vnsahwjar-what-is-a-socra-account --- ## What is the difference between a Journey and a Socra? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19m5sw2709fmpbjncfbc941-journey-vs-socra A Socra holds one problem, decision, draft, or idea. A Journey organizes related Socras and smaller Journeys around a larger goal. The Journey carries the context that work inside it should share. ## Start with a Socra for one result Start with a Socra when one piece of work can reach a clear result by itself. The Socra keeps its content and conversation together. It can live directly in a Space or inside a Journey. A Socra inside a Journey can use relevant context from that Journey. ## Start with a Journey for related work Start with a Journey when several pieces of work contribute to one goal. A smaller Journey is useful when one part needs its own goal and context. You can create a Journey directly in [Socra Journeys](https://journeys.socra.com/) or ask the agent to create one. You can also start with a Socra in a Space and move it into a Journey later. If the agent suggests creating a Journey or moving a Socra, it waits for your approval before making that change. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19m5sw2709fmpbjncfbc941-journey-vs-socra --- ## Who can approve or change a Module, and what happens when rules conflict? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m14qm90gmp2avcfpp398gp3p-module-approval-and-conflicts Each Module has one owner. Only that owner approves the exact words that describe what should be true. An agent can propose a change and show the owner the exact text before and after. The owner approves or rejects the proposal before the agent saves it. You decide who else can change the Module: - The owner always has full access. - Editors can change the content and dependencies. - Admins can make those changes, manage access, and transfer ownership. - Commenters and viewers cannot change the Module. Cortex checks these permissions when someone tries to make a change. Each saved change to the content, dependencies, or owner creates a new version. The history records who made the change and when. ## When a request conflicts with a Module The agent surfaces the conflict and asks the owner to decide. The approved rule remains in force until the owner approves an exact change. If the owner rejects the change, the agent follows the existing rule. Work that requires breaking the rule does not proceed. ## When Modules disagree The disputed rule belongs to the Module that owns the exact subject. The owner of that Module decides what should be true. A change that affects more than one Module requires approval from each owner for the text in their Module. Dependencies control the order in which agents receive knowledge. Cortex provides foundational Modules before the selected Module. A dependency never changes who owns a rule. ## How exceptions work An exception is a rule with a limited scope. The owner approves that scope and records the exception in the Module that owns the subject. A one-off request does not change an approved rule. The existing rule applies until its owner approves the exception. ## What Cortex records Cortex keeps every version of the Module. You can compare changes and restore earlier knowledge. Restoring a version creates a new version, so the history remains complete. ### Article details - Collection: [Cortex](https://support.socra.com/collections/col_01kzpmz5q2hz8avw3tys0tnx4f-cortex) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m14qm90gmp2avcfpp398gp3p-module-approval-and-conflicts --- ## Who can see my work in Journeys? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m19rdzebt2v1x7t4jk83jy6r-who-can-see-my-work-in-journeys Journeys work is private unless you publish it. Private means access-controlled, not necessarily visible only to you. A private Journey or Socra can be seen by people whose Space or parent Journey access applies to it, and by people you add directly. ## How private access works Private Journeys and Socras inherit Space permissions by default. To stop Space-wide access, open Privacy and turn off Space permissions. People who have access through a parent Journey or were added directly still retain their access. Sharing a Journey gives that person access to the Socras and sub-Journeys inside it. Sharing one Socra does not expose the rest of the Journey. ## What each role allows - Viewer can read and react. - Commenter can also post updates. - Editor can also edit content, create and move work, and assign it. - Admin can also manage access and privacy. - The owner has full access and can transfer ownership. When Allow members to add others is on, collaborators can add people at their own role or a lower role. An Admin or the owner can turn this setting off. ## Publishing is different from private access A private Journey or Socra can grant access through Space permissions, a parent Journey, or a direct share. Open Privacy and choose Published to make the work publicly readable. For published work, the Privacy settings determine whether signed-in people can comment or add Socras. Text still in the composer has not been added to the shared timeline. It is stored as an unsent draft in that browser until you send it. ### Article details - Collection: [Journeys](https://support.socra.com/collections/col_01kzpmz5xcaz7jsvq4yry7n9tg-journeys) - Published: 2026-08-30 - Updated: 2026-08-30 - Canonical: https://support.socra.com/articles/art_01m19rdzebt2v1x7t4jk83jy6r-who-can-see-my-work-in-journeys --- ## Why should I use a personal email address for my Socra ID? Company: Socra — Multiply Your Judgment Canonical URL: https://support.socra.com/articles/art_01m151h49f90dwvprddddghxem-personal-email-for-socra-id Use a personal email address that you expect to control as your employment and Account memberships change. Your Socra ID belongs to you. It is the identity you use across Socra, including every Account you join. Your email is the verified sign-in and recovery address attached to it. We use that address to verify a new Socra ID, send email sign-in codes, and reset your password. If your employer controls the address and disables it, you may lose access to those messages and be unable to recover your Socra ID. Your company controls access to its resources through your Account membership. An Account owner can change or remove that membership without owning or deleting your Socra ID. Your company can still send an Account invitation to your work address. You can accept it while signed in to the Socra ID you already own. The invitation address delivers the invitation. Your Account membership records your relationship with the company. ### Article details - Collection: [Socra ID](https://support.socra.com/collections/col_01kzpmz55rkwk7x90cs6d44977-id) - Published: 2026-08-28 - Updated: 2026-08-28 - Canonical: https://support.socra.com/articles/art_01m151h49f90dwvprddddghxem-personal-email-for-socra-id