Date: Fri, 29 Mar 2024 12:57:18 +0000 (UTC) Message-ID: <1062861648.1.1711717038670@6c0ee52670f3> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_543033579.1711717038650" ------=_Part_0_543033579.1711717038650 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This feature has been deprecated since the OKR permissions are not separ= ately handled in objective cycles. Now OKR permissions are managed from rol= es and permission tab of company directory. Read https://amoeboids.atlassian.net/wiki/spaces/UP/= pages/2281111558/UpRaise+roles+and+permissions?search_id=3D43c8dcf5-349d-46= 95-a7d2-6066ab3bbdd4
While creating an objective at Individual, team or company level no= n-admin users may get a message "you can't add objectives to this cycle. On= ly UpRaise admin/super admin can add objectives for all teams" becaus= e UpRaise allows admins & super admins to set permissions for OKRs that= restrict or allow certain users from creating new objectives or editing ex= isting once.
This is completely dependent on an organisation's strategies and no= rms they follow to decide who should have access and who should not. When y= ou receive such message, you can simply contact your UpRaise admin or super= admin.
In this section