Products and capability map¶
Use this map to find the explanation for the work you need to do. Each linked overview leads to task guides, responsibilities, expected results, recovery and current limitations. You can read these public explanations without access to the engineering repositories.
Availability: This is a documentation draft. The map organizes the current documented feature families; it does not certify complete platform coverage or deployed availability. Several intended journeys have unfinished frontend work or unresolved implementation details. Check the selected guide before relying on a capability.
The platform overview explains how the areas fit together. The glossary defines common terms.
Your account and workspace entry¶
| I need to… | Read |
|---|---|
| Sign in, understand sessions or complete additional verification | Sign-in and sessions |
| Register, activate an account or join an organization | Create an account and join |
| Update my personal profile, select a workspace or understand product choices | Profile and product access |
| Deactivate my account or recover that same account | Account lifecycle |
| Recover a forgotten password | Password recovery |
| Understand the authorization PIN used for protected actions | Authorization PIN |
| Enroll or replace my recorded signature | Signature enrollment |
An account belongs to a person. Organization membership, workforce information and product permissions have separate owners. A signature on file does not grant authority to sign every document.
Set up and administer an organization¶
| Responsibility | Read |
|---|---|
| Create a workspace and understand trial or initial-payment requirements | Workspace creation |
| Maintain workspace details, branches and organization-head designations | Workspace structure |
| Manage membership, roles, permissions and access policy | Membership and authority |
| Understand licensed seats, usage, storage and capacity | Usage and entitlements |
| Review subscriptions, invoices, payment and overdue-payment handling | Subscription and billing |
| Understand trial/paid coverage, renewal grace and current access | Subscription coverage |
| Resolve an original checkout or manage renewal consent | Checkout recovery and saved payment methods |
| Understand suspension, reactivation and recovery of workspace access | Workspace lifecycle |
| Connect eligible workspaces through an enterprise network | Enterprise networks |
Workspace administration is distinct from platform staff operations. Commercial eligibility, a person's product grants and permission to perform an action remain separate. Do not infer a price, trial duration, hosting location or data-deletion outcome from a workspace's display name or status.
Organize and complete work in WorkOS¶
| Work area | What the guide covers |
|---|---|
| WorkOS Home | The starting workspace and its current delivery limits |
| People and organization structure | Directory and staff information, personnel records, reporting structure and organizational routing |
| Leave | Requests, responsibilities, approval and lifecycle |
| Workflow authoring | Define, review and publish reusable processes |
| Requests and workflow execution | Submit work, handle assigned tasks and decisions, correct requests and understand handoffs |
| Deadlines and escalation | Timing policies, due dates, escalation and the effects of authority changes |
| Projects | Project setup, delivery, progress and lifecycle |
| Records and archives | Organize retained information, classify it and understand access and retention |
| Correspondence | Memos, official letters and their governed preparation and handling |
| Cases | Case ownership, investigation, coordinated work and outcomes |
| Shared work | Exchanges between connected workspaces, routing, participation, documents and filing |
| Activity history | Recorded changes and work-item timelines, including coverage and retention limits |
| Document sessions | Uploading, viewing and signing with the applicable session and authority rules |
| Governance authority | Approval bodies, voting and signing responsibilities, delegation and synchronization |
A reusable workflow definition, a submitted request, an assigned task and a retained record are different objects. Use the guide for the item you are changing. Completing one stage does not establish completion of a receiving process.
Communicate and follow updates¶
| Capability | What to understand |
|---|---|
| Messaging and the work inbox | Conversation access, work discussions, messages, attachments and related activity |
| Meetings | Meeting arrangements, participation and their current integration limits |
| Mailbox integration | Connecting a supported mailbox, reading mail and handling connection or delivery problems |
| Notifications and email updates | Inbox, email and live-update meaning, preferences and unsupported channel limits |
A notification draws attention to an event. A conversation discusses work. A decision must still be recorded through its authorized business action. Opening an email or attending a meeting does not, by itself, complete a request or approve a document.
Understand contribution and recognition in HiveOrbit¶
| Question | Read |
|---|---|
| What has been recorded for me or my current team? | Personal and team insights |
| What do department and organization views include? | Department and organization insights |
| What supports a recognition item or contribution claim? | Recognition and evidence |
| How are expectations, policies, profiles and campaigns configured? | Configuration and recognition programmes |
| How is HiveOrbit prepared and enabled for the organization? | Initial setup |
| Why can received evidence wait or be excluded from processing? | Eligibility, retained evidence and recovery |
| Where does evidence come from, and what does its health mean? | Contribution sources and reconciliation |
Read contribution measures, recognition points and awards according to their own definitions. Check period, population, coverage, source delay and calculation limits. These views support investigation and discussion; they do not independently establish a complete assessment of a person's performance.
Use governed assistance in HiveAI¶
| Capability | What the guide explains |
|---|---|
| Entry and access | Product availability, permissions, policy, provider and environment prerequisites |
| Conversations and speech | Conversation ownership, text/voice interaction and result or recovery states |
| Grounded answers and citations | Answer sources, evidence links, authorized reading and limitations |
| Personal memory | Personal context and privacy controls |
| My Day and work assistance | Supported personal work summaries and assistance |
| Organization intelligence | Authorized organizational information and its meaning |
| Briefings and forecasts | Prepared insights, assumptions, evidence and uncertainty |
| Credits, budgets and usage | Spending authority, credit use, reservations and reconciliation |
| Governed actions and approvals | Proposed changes, review, approval, execution and uncertain outcomes |
| Assisted workflows | Reusable assistance and workflow controls |
| Shared work memory | Shared context, authority and lifecycle |
| Secret-access exceptions | Scoped access to Secret-classified content, review and follow-up |
| Governance and incidents | Policy, accountability, audit evidence and incident response |
| Workspace knowledge | Manuals, processing, preview, publication, replacement and recovery |
| Providers and models | Approved model/provider choices and operational boundaries |
| Private Cloud | The implemented but disabled private capability boundary |
| Platform Support knowledge | How authorized staff prepare and publish support guidance |
| Platform staff assistance | Staff-specific context and controlled actions |
| Platform staff voice | Staff speech interaction and spoken-response boundaries |
The last three guides describe platform staff responsibilities. Reading them does not grant customer-workspace access or staff authority.
Non-private backend capabilities have default availability subject to the applicable commercial and security controls. Browser delivery and provider provisioning require separate verification. Private Cloud and its private provider/retrieval paths remain disabled; their presence in documentation is not an activation instruction.
Understand platform operations¶
These public overviews explain what the platform's operators are responsible for. Detailed staff procedures, engineering references and recovery commands are delivered through private GitHub documentation.
| Operational area | Public explanation |
|---|---|
| Initial administrative establishment | Initial platform setup |
| Staff roles and access | Platform staff administration |
| Customer support and tenant lifecycle | Support and lifecycle management |
| Offered plans, quotes and contracts | Commercial administration |
| Billing reviews and usage investigations | Billing operations |
| Service observations, audit and organization-data requests | Platform oversight |
| Operational reporting | Platform Insights |
| Staff entry and command surfaces | Platform Command Center |
An operational dashboard is evidence within its stated coverage and time window. It does not certify every customer action, a complete outage history or universal data erasure.
Choose a starting path¶
- New user: begin with account access, joining and workspace selection, then open the guide for your assigned work.
- Manager or process owner: begin with people, authority, workflow execution and deadlines; read the meaning and limits of insights before using them.
- Executive or adoption owner: read the platform overview, commercial responsibilities, governance and lifecycle explanations before defining a rollout.
- Organization administrator: begin with workspace structure, membership, access, usage and billing.
- External participant: start with the exact invitation or shared-work guide relevant to the relationship; confirm which workspace and information you are authorized to access.
- Support or engineering reader: use these explanations for reader context, then follow the separately controlled source-owned procedures appropriate to your role.
If the route you need is unavailable, read that feature's recovery and availability sections. Do not substitute another organization's access, a sample screen or a similarly named action.