A private label does not, by itself, settle who can view a shared conversation or scheduled task. Nor does it establish whether a control concerns an app permission or settings that apply generally to all conversations.
What the label does not establish
| Reader question | What remains unsettled |
|---|---|
| Who can open a shared item? | Help documentation says that anyone with a link created from a personal account can view the shared conversation or scheduled task. A private label alone does not demonstrate that link-based access has been excluded. |
| What does a permission cover? | App permissions are separate from settings that apply generally to all conversations. A label alone does not identify the scope of the relevant control. |
How to check it
For a shared conversation or scheduled task, readers should check the sharing arrangement rather than rely on the label. The documented access rule is that anyone who has a link created from a personal account can view the shared item.
Permissions also require a separate check. An app permission should not be treated as a setting that applies to all conversations, and a general conversation setting should not be treated as an app permission.
What readers must still confirm
Before treating shared content as private, readers still need to confirm:
- Whether the item is accessible through a personal-account link.
- Whether anyone who obtains that link can view the conversation or scheduled task.
- Whether the relevant control is an app permission or a setting that applies generally to all conversations.
- Whether the current sharing arrangement matches the intended access level.
Without those checks, a private label remains a description rather than proof of restricted access or a defined permission scope.