> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/ocv-employees/pulse/pulse.md). # Pulse [Pulse](https://pulse.opencoreventures.com) is OCV's internal operations system and the single source of truth for company, investment, and operational information. ## Open Pulse * [Open Pulse](https://pulse.opencoreventures.com) * [Open EvenOne Pulse](https://pulse.evenone.ventures) (EvenOne team) Pulse accounts are invitation-only. Follow the invitation email to confirm your account and set a password. If you cannot sign in or cannot find the information you need, contact an OCV administrator. ## Start here * [Roles and permissions](/ocv-employees/pulse/pulse/roles.md) — understand what each account can see and change. * [Slack](/ocv-employees/pulse/pulse/slack.md) — connect Pulse to Slack and use Pulse commands and link previews. * [Investment pipeline](/ocv-employees/pulse/pulse/pipeline.md) — work with projects as they move through the investment process. ## What Pulse contains ### Companies Company pages bring together the current operating record for each company. Depending on your role, a page may include company details, key dates, updates, KPIs, team members, links, financial information, investments, and related Google Drive folders. ### Projects and the pipeline Projects represent opportunities being researched or evaluated. The [Project Pipeline](/ocv-employees/pulse/pulse/pipeline.md) groups active projects by stage so the investment team can see what needs attention and who owns the next step. ### People The People directory provides searchable profiles and company team-member records. Some personal, compensation, and integration details are restricted by role. ### Dashboard and utilities OCV users may also see the portfolio dashboard, performance views, company data health, salary benchmarking, and Slack alerts. These tools are only visible when your role permits access. ## Using Pulse well * Treat Pulse as the current operational record. Update the relevant record instead of keeping a separate copy of important information. * Keep company and project names, ownership, stages, dates, and links current. * Enter KPI values for the correct period and use the notes field when context is needed. * Use updates and comments in the record where the relevant team can find them. * Do not put credentials, API tokens, or other secrets in descriptions, comments, updates, or links. Access is intentionally limited by role and, for company users, by assigned company. If an action or section is missing, see [Roles and permissions](/ocv-employees/pulse/pulse/roles.md) or ask an administrator rather than creating a duplicate record. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://handbook.opencoreventures.com/ocv-employees/pulse/pulse.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.