Cannot Create or Edit an OKR
If OKR creation or editing is rejected, record the displayed error message. There is no current “move to Phase 4” action or requirement to complete every analysis.
Quick diagnosis
| Symptom | Check |
|---|---|
| No new-objective action | Correct company, selected OKR cycle and creation permission |
| Cannot select a cycle | Company/cycle context and relevant planning/OKR cycle status |
| Field validation error | Required or invalid fields highlighted by the form |
| 403 / access denied | Role, led subtree, ownership and record permissions |
| Structure cannot change in an approved plan | Structural lock resulting from plan approval |
| Cannot write in a closed cycle | OKR cycle closure lock |
| Limit error | Company's effective entitlement/license limit |
1. Check the workspace and cycle
Open the correct cycle in Goals & Tracking → OKR Cycles. Make sure you have not selected another company or cycle with a similar name. Planning-cycle and OKR-cycle activation/closure rules are separate.
2. Check permissions and unit scope
A Team Lead writes within their led subtree. A Member does not create objective structure; they update progress for key results they own/contribute to and progress/status for their initiatives. Reading a record does not grant editing permission. See Roles & Permissions.
3. Check record status
An approved plan can lock objective/KR structure; permitted actual/progress updates are a different operation. A closed OKR cycle also rejects progress changes. Company users are read-only while their company is suspended.
4. Focus areas and alignment
A missing focus area link is not a general objective creation prohibition. Link the relevant priority and review gaps in Reports → Goal Alignment Matrix or the cycle's Health view. Creating an objective does not require creating three or five focus areas first.
If the problem remains
Send the company, OKR cycle, operation, role, record ID and sanitized error text to your administrator. Do not share tokens or personal information in screenshots. Do not raise your role unnecessarily to bypass an access failure.