This site is moving soon to become part of an integrated Appfire documentation and information site for our apps. This site will remain available during the transition to our new and improved site. Once this site is moved over, this banner will be updated with the new site link for easy access.
Take a look here! If you have any questions please email support@appfire.com
OKR restrictions (per-OKR)
What are OKR restrictions?
OKR restrictions are an additional layer of permissions applied to a single OKR. There are 2 types of restrictions that can be applied:
- visibility - you can restrict the visibility of an OKR to a group of chosen users and teams
- editing - you can restrict any editing capabilities of an OKR (including creating sub-items and linking Jira issues) to a group of chosen users and teams
Restrictions applied to specific OKRs are respected in the first place. That means that even if the user has a permission to edit OKRs (defined by his role set on the Permissions page), they might not have permission to edit a particular OKR (if the OKR is restricted and they’re not added to the editing group by the person who restricted this OKR).
https://jqlsearchextensions.atlassian.net/l/cp/Dq7YiQCs
Who can restrict OKRs?
OKR restrictions can be applied by anyone having permission to do so and when the feature is turned on. Having permission to apply restrictions can be configured on the Settings → Permissions page:
with Full access on, anyone will be able to restrict OKRs
with Global settings control on, people added to the list will be able to turn it on/off and the rest will be able to restrict OKRs
with Editing control, anyone will be able to turn it on/off and people added to the list will be able to restrict OKRs
with Global settings and editing control, people added to the lists will be able to either turn the feature on/off or restrict OKRs
with Advanced setup on, any people added to a role that included this permission, will be able to restrict OKRs
When to restrict OKRs?
OKRs are meant to be as transparent as possible. We recommend using this feature only if the OKRs you want to restrict contain sensitive data that cannot be shared with the whole company.
How to turn the feature on/off?
OKR restricting feature can be turned on in the Settings → General settings.
After it’s turned on, an additional icon will be displayed on every OKR detail page. Clicking on the icon shows a configuration dialog, where the restrictions can be set up.
When the feature is on and you’d like to turn it off, you can toggle the feature off in the Settings → General settings. Once disabled, all restrictions applied will be reverted. The setup you had will not be stored on our side, meaning if you decide to turn the feature on again in the future, no restrictions will be re-applied the way they were when the feature was turned on the last time.
Apart from the on/off toggle, you can find another setting related to OKR restrictions. You can choose to either completely hide OKRs with restricted visibility or to show them partially. In both cases, their progress will be counted into the parent OKR’s progress, so the partial visibility allows for a double check if the progress of all top-level elements makes sense.
Using the feature
On every OKR detail page, you will be able to find a locker icon. After clicking it, you will see a dialog with the configuration of the permissions. By default, every OKR is set to “Anyone can view and edit” (respecting other permissions applied).
You can choose:
“Anyone can view, only specific people or teams can edit”- this option will allow restricting editing of a chosen OKR to the group of users and teams added in the list below
”Only specific people or teams can view or edit” - this option allows you to separately define people that can view and the people who can edit the OKR
The user who changes the restrictions is automatically added to restricted groups.
Restrictions are applied immediately after saving.