DOCSEARCHbyAlgolia
Submit Docs

Plane Documentation

website·Indexed 36 days ago

https://docs.plane.so/

Agentic work infrastructure for managing projects, knowledge, and team collaboration. Includes guides for startups, growing teams, and enterprise organizations, covering workspace setup, work item tracking, cycle-based planning, RBAC, and SSO integration.

Tokens
117.8K
Snippets
188
Records
964
Agent score
70%

What's inside Plane

  1. Overview of IdP Group Sync

    IdP Group Sync allows workspace administrators to map groups from an identity provider (IdP) to specific access levels within Plane. When a user signs in via SSO, Plane reads their group memberships and automatically grants the corresponding access. This ensures that onboarding and offboarding are handled automatically as group memberships change in the IdP.

    Availability: Group syncing is currently available only on self-hosted Commercial and Airgapped Editions.

    Supported Providers:

    • OIDC: Supports sync on login and scheduled offline sync.
    • LDAP: Supports sync on login and scheduled offline sync.
    • SAML: Supports sync on login only (groups are only present in the login assertion).

  2. Overview of Plane Workflows and Approvals

    Workflows in Plane act as guardrails to ensure work items follow a team's agreed-upon path. They allow administrators to define permitted state transitions, restrict who can perform those transitions, and implement approval gates. Every project has one default workflow; Enterprise Grid users can create additional workflows scoped to specific work item types.

  3. Overview of Plane Intake

    Intake is a project-level feature that allows users with the Guest role to submit work items (such as bug reports, feature requests, or service tickets). These submissions are held in a separate triage area where Admins and Members can review, manage, and decide whether to accept them into the project's main workflow.

  4. Overview of Workspace Audit Logs

    The workspace audit log provides a time-stamped, append-only, and tamper-evident record of key actions across a workspace. It is designed for compliance, security reviews, and incident investigation. Entries cannot be edited or deleted by any user, including administrators. Access is restricted to workspace Admins and Owners; it is hidden from members and guests.

  5. Overview of Plane Wiki Collections

    Collections act as folders for organizing wiki pages within a Plane workspace. Every wiki page must reside in a collection. While pages can be nested within other pages, collections themselves are organized as a flat list in the sidebar and cannot be nested inside one another.

  6. Overview of Plane MCP Server

    The Plane MCP server allows AI tools that support the Model Context Protocol to interact with your Plane workspace. It enables users to create work items, plan cycles, and query projects using natural language. The server communicates directly with Plane's API and does not consume Plane AI usage; the AI model is provided by the client tool. Access is managed via OAuth, and permissions are based on the user's workspace and project roles.

  7. Overview of Bitbucket Integration in Plane

    Integrating Bitbucket with Plane allows users to link Bitbucket pull requests (PRs) with Plane work items. This enables automated state updates and visibility of development activity within project planning.

    Supported Versions:

    • Bitbucket Cloud (bitbucket.org)
    • Bitbucket Data Center (Self-hosted)

    Important Limitation: The integration supports pull request automation only. Direct issue synchronization between Bitbucket and Plane is not available.

  8. Overview of Plane AI Agents

    AI agents are configured assistants within a Plane workspace that perform tasks autonomously based on defined instructions and triggers. Each agent has its own identity, appearing in the workspace members list under 'Agents and apps', and can be mentioned using @ or assigned to work items like a human teammate.

  9. Overview of Plane AI Skills

    AI Skills are reusable instructions saved in Plane AI that can be triggered in chat using slash commands. Instead of retyping complex prompts, users can invoke a saved skill by its name (e.g., /weekly-update). Skills support variables to adapt to different work items, projects, or users. AI Skills require Plane AI to be enabled for the workspace.

  10. Overview of MCP Connectors in Plane AI

    MCP (Model Context Protocol) connectors allow Plane AI to access real-time data from external services (e.g., GitHub pull requests, Sentry error data, Granola meeting notes) during conversations. Connections are per-user; each workspace member must authenticate the connector with their own credentials. Connectors are managed in Workspace Settings → Integrations → Connectors.

  11. Overview of Workspace Governance

    Workspace Governance allows workspace administrators to define shared configurations (states, workflows, work item types, and custom properties) once at the workspace level. When enabled, projects reference these shared resources rather than defining their own. This ensures consistency and compliance across the workspace.

    Critical Warning: Enabling governance is a permanent, one-way change. Once enabled, it cannot be disabled. Project admins will permanently lose the ability to independently create or edit states, workflows, work item types, templates, automations, and recurring work items.

  12. Overview of Plane GitHub Integration

    Plane integrates with GitHub Cloud, GitHub Enterprise Cloud (GHE.com), and GitHub Enterprise Server (self-hosted) to synchronize issues and pull requests.

    Key capabilities include:

    • Issue Syncing: Bidirectional synchronization of titles, descriptions, states, assignees, and labels. Triggered by the plane label on GitHub and the github label in Plane.
    • Comment Syncing: Bidirectional synchronization of comments between GitHub issues and Plane work items.
    • PR State Automation: Automatically moves Plane work items to specific states based on pull request events (opened, sent for review, merged, or closed).
    • User Attribution: Maps personal GitHub accounts to Plane users so updates are attributed to the individual rather than a bot.