# The same issue for two audiences

Fictional demonstration for an invented product, Lantern. These are writing examples, not tested product behavior. No real incident, customer data, or security control is represented.

## External help article: A shared page will not open

Audience: the person invited to read a page. Owner: Customer Support. Status: Example draft.

Quick answer: Check that you are using the account that received the invitation. Ask the page owner to confirm the invitation is still valid. If access still fails, contact support with the time of the error and non-sensitive error text.

Steps:
1. Confirm which account received the invitation.
2. Sign in with that account through the product's known sign-in page.
3. Ask the owner to check the invitation and intended role.
4. If unresolved, contact the designated support channel. Do not send your password or a private document's contents.

Expected result: You can open the specific page you were invited to read, or support has enough non-sensitive context to investigate.

## Internal support runbook: Investigate a page-access report

Audience: authorized support staff. Owner: Support Operations. Status: Example draft.

Quick answer: Confirm the requester's identity using the company's approved process, check the relevant invitation and role records with authorized tools, and escalate inconsistent permissions to the responsible administrator.

Internal-only fields: incident reference, authorized diagnostic record location, escalation owner, and restricted investigation notes. Leave these fields blank in a public article. Do not copy customer records into this sample.

Steps:
1. Follow the approved identity-verification procedure.
2. Check the specific invitation and role within your authorized scope.
3. Record the relevant observation in the restricted case record.
4. Escalate a suspected permission defect. Do not grant broader access as a workaround.
5. Send the customer only the approved explanation and next action.

## Before publication

- Replace invented product behavior with verified steps.
- Confirm the owner and reviewer.
- Remove internal diagnostics and private links from the external article.
- Configure the actual audience in the publishing product.
- Test the public article as signed out and the internal article with an unauthorized test account.
- Record the test result. A label saying internal does not restrict access.
