Mercor wiki is a collaborative knowledge base built for modern teams who need structured, up to date information at scale. The platform helps organizations document decisions, processes, and context in a way that stays accessible as teams grow.
Designed for both technical and non technical readers, mercor wiki emphasizes clarity, discoverability, and security. Teams use it as a single source of truth that can be searched, linked, and updated in real time.
| Key Aspect | Description | Impact | Example Use |
|---|---|---|---|
| Knowledge Organization | Spaces, pages, and tags to structure content logically | Improves findability and reduces duplicated work | Product specs in one space, onboarding in another |
| Real Time Collaboration | Multi user editing, comments, and inline mentions | Accelerates decisions and aligns distributed teams | Draft RFCs with engineering and product live |
| Search & Navigation | Full text search, page links, and breadcrumb navigation | Reduces time spent locating information | Find API contracts by keyword or owner |
| Permissions & Security | Role based access, granular page permissions | Protects sensitive data while enabling broad access | Limit payroll details to finance and HR |
| Integration | Webhooks, Slack, Jira, GitHub, and SSO | Keeps workflows in context without switching tools | Link merge requests to wiki pages automatically |
Getting Started with Mercor Wiki
New users benefit from a guided onboarding flow that explains core concepts like spaces, pages, and permissions. Editors can start writing immediately using markdown shortcuts and rich text tools side by side.
The editor supports headings, lists, code blocks, embeds, and version history. Each change is timestamped and attributed, making it easy to track who updated what and why.
Organizing Content with Spaces and Tags
Spaces act as top level containers for related pages, such as product lines or departments. Within each space, teams can create a hierarchy of pages and link them together to build a connected knowledge graph.
Tags provide an additional navigation layer, allowing pages to appear in multiple contexts without duplication. This is especially helpful for cross functional topics like security policies or incident retros.
Collaboration and Review Workflows
Mercor wiki includes built in review workflows where pages can be submitted for approval before publishing. Reviewers can comment, suggest edits, and approve changes without leaving the platform.
Version history lets teams compare drafts, revert unwanted changes, and audit decisions over time. This is valuable for compliance, legal reviews, and postmortem analysis.
Integrations and Developer Experience
Native integrations connect mercor wiki with the tools teams already use, including Slack for updates, Jira for tasks, and GitHub for code references. Webhooks enable custom automations and data sync.
An open API and markdown import tools make it straightforward to migrate from other platforms or to build custom workflows. Detailed documentation and SDKs lower the barrier for developers.
Operational Best Practices and Recommendations
- Define clear ownership for each space and page to avoid orphaned content
- Use tags consistently to enable cross functional discovery
- Leverage review workflows for policy, spec, and release notes pages
- Integrate with Slack and Jira to keep tasks and documentation in sync
- Audit permissions and version history quarterly to maintain security
FAQ
Reader questions
How does mercor wiki handle permissions for sensitive pages?
Permissions are managed at space, page, and block level, allowing owners to set view, edit, and comment access for individuals or groups. SSO and audit logs help enforce governance policies.
Can I link pages across different spaces in mercor wiki?
Yes, cross space links let pages reference each other while keeping content organized in distinct spaces. These links remain functional even when pages are moved or renamed.
What happens during a migration from other wiki tools to mercor wiki?
Import tools support common formats like CSV and markdown, and mapping templates simplify field conversion. A migration guide and dedicated support help minimize downtime.
Does mercor wiki support offline editing or mobile access?
Web offline caching allows limited editing without a connection, and the responsive design ensures a smooth experience on mobile devices. Native mobile apps are in active development.