Skip to content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Compliance Portal

Publish selected compliance information through a controlled public portal

View as Markdown

The Compliance Portal is the public-facing counterpart to an organization’s private Probo workspace. It lets an organization share approved compliance information without granting visitors access to the console.

A portal can present certifications, commitments, references, files, and custom links selected by the organization. Portal content is managed separately from internal records so publishing a compliance program record does not automatically expose it publicly.

Commitment groups organize related public statements. References and files provide supporting material. Review each item for confidential, personal, or security-sensitive information before publication.

The portal supports visitor authentication and NDA-controlled access for protected material. A custom domain can present the portal under an organization-owned hostname. These controls reduce unintended disclosure but do not replace content classification and approval.

Portal availability depends on the trust-center service configuration in a self-hosted deployment. The configuration name is retained for compatibility; the product name is Compliance Portal. Operators must configure public URLs, OAuth behavior, email delivery, TLS, and domain routing consistently.