Working with confidential or sensitive information within Gtmhub could be handled in two different ways. 

The first approach is setting custom permissions to a dedicated OKR session. This allows you to select who within your organization can access a given session and/or contribute to it.

But sometimes the sensitive information lives in a session where everyone within your organization has access to. In this case, there's another approach that Gtmhub supports: Private OKRs functionality.

What is a private OKR?

Many times, individuals wish to set private OKRs. Sometimes, these objectives are set privately between a person and their supervisor.

For various reasons, it may be impractical to have such private objectives visible to everyone. For example, these could be personal development objectives such as “Get along better with colleagues” or “Improve writing skills”.

Private OKRs allow you to create and align OKRs with restricted rights. A private OKR is visible for the objective owner and their managers.

Pro-tip: 

Avoid assigning Key Results to other teammates for a private OKR as they won't be able to see the Objective as long as it's marked as private.

How to create a private OKR?

Here's how to create a private OKR:

  1. Navigate to an Open session in your account
  2. Click the Add new objective button
  3. Choose Private from the drop-down menu in the Privacy section
  4. Save

Pro-tip:

You can edit the Objective and mark the Privacy as Visible to everyone. Here's how to do that:

  1. Select the Objective
  2. Click no the Ellipsis (3-dotted) button > Edit Objective
  3. Change the Privacy by choosing Visible to everyone
  4. Save

Visibility of a private OKR

Private OKR details are visible to both the objective owner and their managers.
It's easy to spot it both from the Objectives list view (OKRs > Objectives)... 

... and in the Alignment view (OKRs > Alignment BETA).

For the rest of the organization, the private OKR appears with restricted access - users would see where it fits in the session tree or the nested view but won't be able to get information on the objective attributes such as objective name, key results, owner.

The private OKR won't appear in the objectives list view but only in the Alignment view.

All private OKRs contribute toward session progress. If tagged they'll be highlighted in the Alignment view and progress on private OKRs will be calculated in Pulse and Statistics but they will still remain with restricted access.

Did this answer your question?