Restricted Content
Stay organized with collections
Save and categorize content based on your preferences.
Restricted content is potentially sensitive content about an individual.
Restricted content can be marked as Restricted or Restricted+ depending on
the sensitivity of the content. Restricted and Restricted+ content may
occasionally be stored in Google Issue Tracker. To mitigate the risk of this
information being visible, content in Google Issue Tracker that contains or is
suspected to contain sensitive content will be marked with a restricted flag.
This restricted flag will restrict access so that the content can only be viewed
by those with a business need (and never by the general public). Attempts to
access content marked as restricted (both successful and unsuccessful) will be
logged and auditable.
Restrict existing content
To restrict existing content, you must be an Issue Admin, the author of the
comment, or the uploader of the attachment.
To restrict existing content:
Open an issue.
To the right of the comment or attachment, click the Comment actions
icon and choose Restriction settings.
Choose the appropriate restriction level for the comment or attachment, and
then click Set.
Restrict new content
To restrict new content:
Click the restricted icon.
In the dialog, choose the appropriate restriction level for the content, and
then click Set.
After you set the restriction level, the Issue Tracker UI marks the content with
an indicator.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-04 UTC.
[null,null,["Last updated 2025-02-04 UTC."],[[["\u003cp\u003eRestricted content in Google Issue Tracker, potentially containing sensitive information, is flagged and access is limited to authorized personnel.\u003c/p\u003e\n"],["\u003cp\u003eContent can be marked as \u003cem\u003eRestricted\u003c/em\u003e or \u003cem\u003eRestricted+\u003c/em\u003e based on sensitivity, with access attempts being logged and monitored.\u003c/p\u003e\n"],["\u003cp\u003eIssue Admins, comment authors, and attachment uploaders can restrict existing content by adjusting the restriction settings.\u003c/p\u003e\n"],["\u003cp\u003eNew content can be restricted during creation by selecting the desired restriction level before submission.\u003c/p\u003e\n"],["\u003cp\u003eRestricted content is visually indicated within the Issue Tracker UI for easy identification.\u003c/p\u003e\n"]]],[],null,["# Restricted Content\n\nRestricted content is potentially sensitive content about an individual.\nRestricted content can be marked as *Restricted* or *Restricted+* depending on\nthe sensitivity of the content. Restricted and Restricted+ content may\noccasionally be stored in Google Issue Tracker. To mitigate the risk of this\ninformation being visible, content in Google Issue Tracker that contains or is\nsuspected to contain sensitive content will be marked with a restricted flag.\nThis restricted flag will restrict access so that the content can only be viewed\nby those with a business need (and never by the general public). Attempts to\naccess content marked as restricted (both successful and unsuccessful) will be\nlogged and auditable.\n\nRestrict existing content\n-------------------------\n\nTo restrict existing content, you must be an Issue Admin, the author of the\ncomment, or the uploader of the attachment.\n\nTo restrict existing content:\n\n1. Open an issue.\n\n2. To the right of the comment or attachment, click the **Comment actions**\n icon and choose **Restriction settings**.\n\n3. Choose the appropriate restriction level for the comment or attachment, and\n then click **Set**.\n\nRestrict new content\n--------------------\n\nTo restrict new content:\n\n1. Click the restricted icon.\n\n2. In the dialog, choose the appropriate restriction level for the content, and\n then click **Set**.\n\nAfter you set the restriction level, the Issue Tracker UI marks the content with\nan indicator."]]