A customer asks for security documentation. You want them to receive the right files and descriptions without exposing your entire internal document library.
In the Sythe platform, Trust portal lets your organization select what to publish. You need permission to update the portal to edit it, and separate publishing authority to release the saved draft.
Document requests need an owner
Open Trust portal and review Profile. Set Who owns this? to the person responsible for document-request email. Choose someone who can respond to the request or route it to the appropriate owner.
Check the public description and organization details before moving on. The page is for a recipient evaluating your company; it should describe the company and evidence accurately rather than imply that publishing a page certifies a framework.
The resource library controls what the buyer sees
Open Resources, then Resource library. The library supports documents, published pentest reports, framework statuses, portal sections, and external links. Select the resource that matches what you intend to share.
For a document, review Public title, Public description, and Public access. Use a description that tells the recipient what the file covers. Do not let a shortened title remove a meaningful scope or date distinction.
Choose supported file-backed documents. The editor identifies limitations for authored policies and Google Drive documents that cannot yet be served through this flow. A document being visible elsewhere in your organization does not establish that the portal can publish it.
A framework status is a claim your organization chooses to display. It is not a file upload or an independent certification decision. Select a status only when your organization can support it.
Preview shows the saved draft
Open Publishing actions and use Save and preview to inspect the saved draft. Read it as a recipient: which resources are visible, which descriptions explain their scope, and what access is offered?
Inspect any Publish blocked items and resolve them before releasing the page. Review submission is available when you want an operator to look first, but it is not a universal prerequisite to customer publication.
After publishing, check the public page in an unauthenticated browser session. That is your verification of the anonymous visitor's experience, separate from what an editor can see while signed in.
A replacement document can change what buyers receive
Document downloads can follow the document's latest version, so treat replacement as a publishing decision too. Confirm that a new version still belongs under the same public description and access setting. Pentest reports become available after engagement publication; an unfinished report is not a substitute.
Before sending the portal URL, confirm that its contact can answer document requests and that the anonymous page exposes only the resources you selected.