Integrations
Plenar integrates with external tools for calendar sync, document linking, task import, and user provisioning. Configure all integrations in Settings > Integrations from your dashboard.
Google Calendar
Syncs time off from calendar events to Plenar availability. When a team member has calendar events that indicate they are unavailable, those dates appear in the availability view and affect scheduling.
Setup
- Go to Settings > Integrations > Google Calendar
- Click Connect Google Calendar
- Authorize Plenar to read your calendar
- Configure sync preferences — which calendars to watch, which event types count as time off
Calendar-synced time off appears alongside manually-entered entries in the Availability view. Both affect scheduling identically.
Per-user configuration
Each team member connects their own calendar. Organization admins can see who has connected but cannot access calendar contents. Only availability data (dates and capacity) flows into Plenar.
What syncs
| Calendar data | Plenar effect |
|---|---|
| All-day events marked “Out of Office” | Full-day time off (0% capacity) |
| All-day events marked “Busy” | Full-day time off (0% capacity) |
| Multi-day events | Time off for each day in the range |
| Recurring events | Each occurrence synced independently |
| Declined or tentative events | Not synced — only accepted events count |
Sync frequency
Calendar data syncs periodically. After initial connection, updates typically appear within a few hours. You can trigger a manual refresh from the integration settings page.
Conflict resolution
If a calendar-synced time-off entry overlaps with a manually-entered entry, both are recorded. The effective capacity for that day is the minimum of the two (i.e., the most restrictive wins).
Google Docs
Link documents to tasks for traceability. When a task has a linked Google Doc, the link appears in the task detail panel.
Setup
- Go to Settings > Integrations > Google Docs
- Click Connect Google Docs
- Authorize Plenar to access document metadata
Linking documents
From the dashboard: Open a task detail panel and click Add Link.
From Claude Code:
"Link this design doc to the auth middleware task"Claude calls plenar_link_artifact with the document URL.
Jira
Import tasks from Jira projects into Plenar. Useful when migrating from Jira-based tracking to Plenar scheduling, or when running both tools in parallel.
Setup
- Go to Settings > Integrations > Jira
- Click Connect Jira
- Authorize and select which Jira projects to sync
Field mapping
| Jira field | Plenar field | Notes |
|---|---|---|
| Summary | Task title | Direct mapping |
| Story points | Estimate (working days) | Configurable ratio (e.g., 1 story point = 1 day) |
| Status | Task status | See status mapping below |
| Issue links (blocks/is blocked by) | Dependencies | Mapped to finish-to-start dependencies |
| Priority | Task priority | Configurable mapping |
| Epic | Goal | Jira epics map to Plenar goals |
| Sprint | — | Not mapped; Plenar computes its own schedule |
Status mapping
| Jira status | Plenar status |
|---|---|
| To Do / Open / Backlog | To Do |
| In Progress / In Review | In Progress |
| Blocked / Impediment | Blocked |
| Done / Closed / Resolved | Done |
Custom Jira statuses can be mapped in the integration settings.
Estimate mapping
Story points convert to working days using a configurable ratio. Default: 1 story point = 1 working day. Adjust this in the integration settings based on your team’s velocity.
Conflict resolution
When the same field is modified in both Jira and Plenar:
- Scheduling fields (dates, assignments) — Plenar wins. These are computed outputs, not manual inputs.
- Status — Last write wins. If a developer moves a Jira ticket to “Done” and Plenar shows it as “In Progress”, the Jira status takes precedence on the next sync.
- Estimates — Plenar wins when changed in Plenar. Jira wins when changed in Jira and not overridden in Plenar.
- Title and description — Jira is the source of truth. Changes in Jira overwrite Plenar on the next sync.
What does NOT sync
- Jira comments, attachments, and custom fields (other than mapped ones)
- Jira sprints — Plenar computes its own schedule
- Jira time tracking — Plenar uses its own estimate system
SCIM
Automated user provisioning from your identity provider (Okta, Azure AD, etc.). When someone joins or leaves your organization in your IdP, SCIM automatically updates their Plenar account.
Setup
- Go to Settings > Integrations > SCIM
- Generate a SCIM token
- Configure your IdP with the SCIM endpoint URL and token
What SCIM manages
- Creating and deactivating user accounts
- Updating user attributes (name, email)
- Group membership (maps to organization roles)
SCIM does not manage project assignments or skills — those are configured per-project in Plenar.
Role mapping
| IdP group | Plenar role |
|---|---|
| Admin group | Organization Admin |
| Default / Member group | Organization Member |
Configure group-to-role mapping in the SCIM integration settings. Users not in any mapped group are provisioned as Members by default.
Provisioning timing
SCIM provisioning is near-real-time for most identity providers. Account creation typically completes within seconds. Deactivation takes effect on the next sync cycle, which varies by IdP configuration.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| User not appearing in Plenar | Not assigned to the Plenar app in your IdP | Assign the user to the Plenar application in your IdP |
| User has wrong role | Group mapping mismatch | Verify group-to-role mapping in SCIM settings |
| Deactivated user still active | Sync delay | Wait for the next sync cycle, or manually deactivate in Plenar |
| SCIM token rejected | Token expired or revoked | Generate a new SCIM token in Plenar and update your IdP |
Data sources
Additional data source integrations are configured in Settings > Data Sources:
- Calendar — Configure Google Calendar sync settings at the organization level
- Directory — Sync team directory from external sources
- Tracker — Connect time tracking tools for actual-vs-estimated comparisons