Skip to main content

Feedback Scope Settings Reference

Use these settings to create or update a feedback scope, choose where it applies, and control who can use it. This reference explains each field and the rules that apply to it.

Feedback Scope Settings Reference

Use these settings to create or update a feedback scope, choose where it applies, and control who can use it. This reference explains each field and the rules that apply to it.

What do I fill in when I create or edit a feedback scope?

Go to Modules > Feedback > Feedback Scopes and select New Scope to create one, or open an existing scope and select Edit. Use the form to define the scope details, choose its context, and set who can submit feedback in it.

  • Scope Title: Enter a short, unique name for the scope. Use a title that clearly tells users what the feedback is about. This field is required.

  • Scope Description: Add a clear description of the scope and its purpose. Use it to explain what kind of feedback belongs here and any important context. This field is required.

How do I choose the right scope context?

Use Scope Context to define where the scope is used. Pick the option that matches the type of feedback you want to collect.

  • General Feedback: Use this for general feedback topics that are not tied to OKRs.

  • Objectives Feedback: Use this when feedback should be linked to OKR objectives.

  • Key Results Feedback: Use this when feedback should be linked to OKR key results.

  • Initiatives Feedback: Use this when feedback should be linked to OKR initiatives.

If you need feedback related to another OKR level, create a separate scope for it. Keep each scope focused so users can choose the right one more easily.

The OKR-linked scope contexts (Objectives Feedback, Key Results Feedback, Initiatives Feedback) appear only when the OKRs feature is enabled on your tenant. If you do not see them, ask the GFoundry team to enable OKRs.

Which permissions affect who can give feedback?

These settings control who can submit feedback in the scope and whether responses stay confidential.

  • Private Feedback Answers: Turn this on if responses should be confidential and not used in public metrics.

  • Read-Only Mode: Turn this on to stop new feedback submissions in the scope. Users can still view previously submitted feedback.

  • Feedback Permissions: Choose who can use the scope. The available options are Team Managers Only, Self Feedback Only, or Team Managers or Self-Feedback Only.

Use Team Managers Only when only managers should give feedback. Use Self Feedback Only when users should review themselves. Use Team Managers or Self-Feedback Only when both are allowed.

What else should I check before saving?

Make sure the scope is Enabled if you want users to use it. If it is disabled, users cannot submit feedback in that scope. Save the form after reviewing the title, description, context, and permissions.

If you are editing an existing scope, check that the settings still match the feedback process you want. Small changes to context or permissions can change who sees the scope and how they use it.

Did this answer your question?