Feature 1
Publish approved assurance content
Choose the governed information customers can see and preview it before publication.
- Configure sections
- Set visibility
- Preview and publish
Capability
Trust Centre Publishing
Configure and publish a branded site for sharing approved security, privacy and compliance information.
The outcome
Give customers and partners a reliable destination for current assurance information.
How it helps
How Trust Centre Publishing works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Control restricted access
Let visitors request sensitive material and keep approval with the organisation.
- Mark content restricted
- Review guest requests
- Grant access
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Branded public site
- Draft and publish workflow
- Public and restricted access
- Policies and resources
- Compliance and subprocessors
- FAQs, updates and custom domain
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Artefact Library
Maintain approved assurance files and make selected artefacts available through the Trust Centre.
Explore capabilitySubprocessor Directory
Maintain and publish the third parties involved in delivering your service, with the context customers need for assurance and privacy review.
Explore capabilityTrust Centre Assistant
Answer prospect and customer questions from the organisation's approved Trust Centre content through a self-service conversational assistant.
Explore capabilityPolicy Publishing and Versions
Publish approved policy versions with effective dates, visibility, distribution and complete version history.
Explore capabilityAvailable in:Trust Management
Used in:Customer Security Assurance
Customer proof
Trust Centre Publishing in practice
See how customers use this capability as part of a broader security, governance or compliance outcome.
Questions and answers
Questions about Trust Centre Publishing
Practical answers to common questions about managing this responsibility well.
Why does trust centre publishing matter?
Give customers and partners a reliable destination for current assurance information.
What should trust centre publishing include?
It should cover branded public site, draft and publish workflow, public and restricted access, policies and resources and compliance and subprocessors, with enough context to support action and explain decisions.
Who should be responsible for trust centre publishing?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep trust centre publishing current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for trust centre publishing?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Trust Centre Publishing in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.