Settings
Settings control how Plenar schedules work and how your team is configured.
Scheduling controls
These live in the Controls panel of the right-hand schedule sidebar. Changing one opens a New Plan so you see the impact before applying.
| Setting | Default | What it does |
|---|---|---|
| Skill scheduling | On | When on, Plenar considers each member’s skills when assigning tasks, matching task skill requirements to the people who have them. |
| Lead time | 5 days | Tasks within this many working days of their scheduled start resist being moved. Prevents Plenar from reshuffling imminent work. Adjustable from 1 to 30 days. |
| Finish started milestones | On | Milestones with work already in progress are prioritized, so the team finishes started work before picking up new milestones. |
When to adjust
Skill scheduling — Leave on when your team has specialized roles (frontend, backend, design) and you want Plenar to route work to the right people. Turn off for generalist teams where anyone can pick up anything.
Lead time — Increase for teams that need more stability (e.g., 10 days if context-switching is expensive). Decrease if your team is comfortable with last-minute schedule changes.
Finish started milestones — Leave on unless you want Plenar to freely reorder work across milestones. Turn off if milestone boundaries are soft and you care more about overall throughput.
Integrations
| Integration | What it does |
|---|---|
| Google Calendar | Syncs time off from calendar events to Plenar availability. Configured per user. |
| Google Docs | Link documents to tasks for traceability. |
| Jira | Import tasks from Jira projects. |
| SCIM | Automated user provisioning from your identity provider. |
Configure integrations in Settings → Integrations. See the Integrations guide for setup details.
Organization settings
Members
Manage organization members, roles, and invitations. Members can be assigned to multiple projects. Organization admins can invite new members and manage roles.
Availability types
Plenar ships a fixed set of time-off types (PTO / Vacation, Sick Leave, On-Call, Conference / Training, and more). For each type your organization can:
- Enable or disable it as an option when logging time off
- Relabel it to match your team’s wording
- Adjust its capacity effect — zero (0%) or a percentage reduction (for example, 50% for on-call)
You can’t add brand-new type keys — the set is fixed — but enabling, relabeling, and adjusting capacity covers most team patterns. See Availability for the full list and defaults.
Data sources
Configure external data sources for calendar sync (Google Calendar), directory sync, and time-tracking integrations.
API tokens
Each project can have API tokens for MCP and programmatic access.
- Go to Settings → API Tokens
- Click Generate Token
- Set a name (e.g., “Claude Code”) and role
- Copy the token — it is shown only once
Token roles
| Role | Preview changes | Apply changes | Manage settings |
|---|---|---|---|
| Planner | Yes | Yes | Yes |
| Contributor | Yes | No | No |
Use Planner for Claude Code sessions where you want the agent to apply changes autonomously. Use Contributor if you want Claude to preview changes but require you to apply them from the dashboard.
See Connect Claude Code for how to use tokens with Claude Code.