Theory dictates that OKRs should be transparent to the whole organisation - transparency is one of the key pillars of OKR benefits. That being said there are always cases where you would like to limit the visibility of specific OKRs, because of sensitivity of information or you are working on a project where full transparency is not optimal. In this case Gtmhub allows you to set custom permissions for your OKR cadence.
Planning sessions default behaviour
By default planning sessions are visible to the whole organisation and each team member can create/update/delete objectives as long as they belong to a role that can manage OKRs.
Changing permissions for planning sessions
If you wish to change the default behaviour for a planning sessions, e.g. make it private to a certain group of people, or change who gets to create/update/delete objectives and key results within the session you can change the default permissions in order to achieve the desired results.
Use case: Objectives accessible to a limited group of users
In this case we want to limit the access to objectives to certain individuals or a group of people that belong to a role in Gtmhub. For the sake of simplicity all users that have access to the planning session will be able to manage all aspects of objectives but define who has access to the session. Only one person will be able to modify the permissions.
- Go to OKRS > Manage sessions
- Create a new session or edit an existing one.
- Click on Advanced section of the session create/edit pop up.
- From Permissions section add the people/roles that you would like to have access to this session
- Create/save your session
Use case: Planning session visible to everyone, updatable by specific users
In this use case we need the whole organisation to be able to see our objectives progress, however only specific users will be able to create/update/delete objectives within the session. Similar as above we can first select he users that will be doing the updates, and then select everyone in the account.
All you need to do now is create/save the session.