Protect Static HTML with Google SSO

Use internalpage when you already have a static HTML report and need a private link that coworkers can open after Google sign-in.

This is useful for:

• notebook exports
• model evaluation reports
• data quality reports
• static dashboard snapshots
• launch or release summaries

1. Prepare the HTML file

Export the report as .html or .htm.

Keep the file safe to show to every allowed viewer. Do not include API keys, database credentials, raw access tokens, or customer secrets in the HTML source.

2. Log in once

Save a personal API token with the CLI.

npx @internalpage/cli auth login

The CLI stores the token and reuses it for later commands.

3. Create the private page

Publish the HTML file with a readable slug.

npx @internalpage/cli pages create ./report.html --slug weekly-report

The command returns the page ID and the private viewer URL.

4. Share the viewer URL

Send the viewer URL to your team. Viewers are redirected through Google sign-in before the page is served.

Access can be workspace-wide or limited to selected emails.

5. Update the same page

When the report changes, replace the latest version instead of sending a new file.

npx @internalpage/cli pages update pg_xxx ./report.html

Store the page ID in your script or CI configuration so future runs update the same private page.

When to use another tool

Use a full application host or a Zero Trust application proxy when the thing you need to protect is a running web app, admin UI, or staging service.

Use internalpage when the thing you need to share is a finished browser-viewable artifact such as an HTML report, Markdown document, or OpenAPI spec.