Goals / OKRs - Add Approval Flow for Goal / OKR Assignment
in progress
T
Teamflect Product Team
Merged in a post:
Separate “create” vs “assign” permissions for Company Priorities
C
Craig
Summary
Allow organisations to restrict who can create Company Priorities, while still enabling all colleagues to link their objectives to those priorities.
Problem
We have defined a small number of Company Priorities at the top level (e.g. CEO-led objectives), and want all colleague objectives to cascade from these.
Current behaviour forces an either/or decision:
If creation is restricted, colleagues cannot assign Company Priorities to their objectives
If creation is enabled, colleagues create new Company Priorities in error, creating noise and requiring manual clean-up
While Teamflect supports controlling who can assign goals through permissions, there isn’t currently a clean separation between creation and usage in this scenario.
Request
Introduce a permission model where:
Only admins (or defined roles) can create Company Priorities
All colleagues can select and link existing Company Priorities to their objectives
Optionally, enable a “hidden / admin-only” Company Priority type that is not visible in creation flows but is available for linkage
Outcome
Maintains a clear, controlled set of company priorities
Ensures all objectives align to strategy
Removes admin overhead of fixing incorrect priorities
Improves discipline and quality of OKR alignment
T
Teamflect Product Team
marked this post as
in progress
Teamflect Product Team
marked this post as
planned