Make the first look useful.
A journalist interested in a software product may want to try it independently. Prepare a test account that makes one representative task easy to find, without requiring access to real customer information. Ask whether the journalist wants access before creating or sending credentials.
Set up a clean workspace.
Use fictional or synthetic sample information and check that it does not contain personal, customer, or confidential data. Give the account only the permissions needed to explore the intended experience. Make sure the sample environment reflects the product accurately, and identify any features that are simulated, unavailable, or different from the public version.
Provide a short starting note.
Include a secure way to sign in, an expiration date if access is temporary, and one or two steps for trying the relevant task. Add the product version or plan being demonstrated, any setup requirements, and a contact for technical questions. Explain what happens to any information the journalist enters and how to request account removal.
Check it before offering access.
Open the account as a new user and follow your own instructions. Confirm the sample data is safe to share, the permissions are appropriate, and the experience works without a staff member intervening. Use your normal secure credential-sharing process rather than putting a reusable password in an unsecured message.
Leave room for independent testing.
Offer the account to a relevant writer with a short explanation of what the product does and why the test might help their reporting. Be available to answer questions and be candid about limitations. The journalist decides what to test, what to conclude, and whether to publish.