Publish deliberately
Choose a public page or require an approved request for documents. Evidence must belong to the workspace and be confirmed by a person; a scanner proposal alone cannot be published.
Show the current state
Published framework readiness uses the dashboard’s engine. A planned framework cannot be published, and an empty center does not invent a score or document.
Review before sharing
Check visibility, recipient access and document sensitivity before sending a link. This is selected evidence, not a certification or assurance report.
Example: a procurement evidence request
A prospective buyer asks how a vendor governs its AI support tool. The workspace admin chooses the relevant framework view and a confirmed, non-revoked policy record. She checks that the document is appropriate to share, then uses a page that requires an approved request for document access. The buyer sees only what was deliberately published. A readiness percentage is still an internal calculation, so the admin describes the underlying evidence and limits rather than calling it certification.
Before sharing a Trust Center link
- Confirm the evidence belongs to the right workspace and was accepted by a person.
- Remove revoked, outdated or sensitive material that should not leave the team.
- Choose public visibility or approved-request access for documents deliberately.
- Check the published view as an external visitor and revisit it after evidence changes.
Common questions
- Can a scanner suggestion be published directly?
- No. The publishing path requires evidence confirmed by a person and rejects revoked evidence.
- Is the page a compliance certificate?
- No. It is a selected view of workspace evidence and computed readiness. Buyers should inspect the supporting records and ask their own questions.
Bring the question into a review
Explore a fictional Fencia walkthrough or tell us which system and evidence your team needs to review.