Only me
You are still reviewing the draft.
Only the signed-in owner can open it.
Sending this link does not grant someone access.
SHARING GUIDE / CHOOSE YOUR AUDIENCE
A client report. Two reviewers. One link.
To share an HTML page privately with share/artifacts, keep it owner-only while reviewing, then choose Restricted access. Allow specific verified email addresses, one exact email domain, or a password. Save the settings, check the recipient experience, and send the share link. You can set an expiration or change access later without changing that link.
Choose the right accessWHAT YOU ARE SENDING
The report.WHO YOU ARE SENDING IT TO
The people you choose.01 / MATCH ACCESS TO THE JOB
“Private” can mean a draft for yourself, a named client, or a group with a password. Start with the audience, then choose the setting that matches.
You are still reviewing the draft.
Only the signed-in owner can open it.
Sending this link does not grant someone access.
A client report is for two named reviewers.
Each person signs in with the exact email you allowed and verifies it.
A forwarded link alone does not admit a different account.
Anyone with a verified email at one domain may read it.
The signed-in, verified email must match the domain you entered.
This checks an email domain, not team membership. Subdomains do not match automatically.
Your audience needs access without signing in.
The reader enters the page password to open the HTML.
Anyone with both the link and password can get in. It does not identify a particular person.
You intend to make the page public.
The link opens without a password or email check.
This is public sharing, even if the URL is hard to guess.
02 / WORKED SHARING EXAMPLE
You have reviewed a proposal and want Maya and Leo to open it. Someone who receives a forwarded link should still need permission. Choose Restricted → Specific people, add their exact emails, and leave password and domain access off.
Want to create the proposal first? Explore a complete proposal example, then bring your own approved material to your agent.
03 / FROM REVIEW TO RECIPIENT
Open the HTML draft with your agent and check the content, sources, and sensitive details. Approve publishing when it is ready. New pages are owner-only unless you explicitly choose another audience.
In your dashboard, open the page and find Who can open this? Select Restricted, then enable Specific people, Email domain, or Password. Use only the methods you want to grant access.
Enter the approved email addresses, exact domain, or password. Optionally set Stop sharing on. Select Save sharing and check the Current summary before copying the share link.
Test the link in a separate browser session. Your owner account can open the page even when others cannot. Confirm that an intended recipient can get in, then send the same share link to your audience.
Sign in with the account that owns the page. Saving email addresses does not send invitations; send the share link yourself. Need a connection first? Connect your agent.
04 / HELP YOUR READER GET IN
Open the link, sign in or create an account with the allowed email, and verify that email if prompted. A domain rule requires the exact domain, such as example.com; mail.example.com is different.
If access fails, check which account is signed in, verify the email, and ask the owner to confirm the address and expiration. Signing in alone does not grant permission.
Open the link and enter the password from the owner. A share/artifacts account is not required for this method. Send the password separately from the link when practical.
If it does not work, ask the owner whether the password changed or access expired. Do not paste the password into the address bar.
05 / WHEN THE WORK IS OVER
Changing access cannot recall screenshots, saved copies, or content already loaded in a reader’s tab. New access checks use the current settings.
Need to correct the content? Update the HTML at the same link. Updating the HTML keeps the existing audience and expiration.
06 / KNOW WHAT PRIVATE SHARING COVERS
No. A hard-to-guess link can still be forwarded. A noindex instruction asks search engines to leave a page out of results; it does not decide who may open it. Use access settings for that. Read Google’s explanation of noindex.
Access controls limit who can load the page. They do not prevent an authorized reader from copying it, and they are not end-to-end encryption. Review sensitive material before publishing and use a system approved for your data requirements.
Safe Static checks disable scripts, forms, embeds, and active API calls. HTTPS images and fonts may still load from their original hosts, which can receive those requests. Remove external assets if that is inappropriate for your material.