Skip to content
English
  • There are no suggestions because the search field is empty.

Managing your Trust Portal

A step-by-step guide to setting up and managing the Trust portal

The Trust Portal is a shareable, externally facing page where you can present your organisation's security posture, including compliance certificates, key documents, and control information, to customers, partners, and prospects without giving them access to CyberHQ itself. It lets you demonstrate trust on demand while staying in full control of who sees what and for how long. You manage it from Settings > Trust Portal. This article covers building your portal, managing who can access it, and how external stakeholders request access.

Building your Trust Portal

Navigate to Settings > Trust Portal to set up the content your portal displays. You can populate and control visibility for each of the following sections:

  • Company Information: your Company Name and Domain (both required) and a Description of your organisation and its security approach, shown at the top of every portal page. Visitors can view the portal in light or dark mode, so you can upload a Logo and a Banner for each. If you provide only one file, it is used for both modes. For a banner, you can upload your own image or choose one from the built-in library.
  • Compliance Certifications: evidence of the standards and certifications you hold. Choose which certifications to display. The list draws on your documentation in Catalogue > Security Resources, so add a certificate there first if it is missing. Then set the File Access Protocol, which controls who can download them.
  • Content Collections: grouped content you choose to make available. Primary collections, such as Technologies and Sub-Processors, are shown on the portal's overview page. Secondary collections, such as Key Documentation, are reached from the portal's tabs. Click Add Collection to add one, select a collection to edit it, or use its bin icon to remove it.
  • Controls: control information that demonstrates your security maturity. Choose the framework in Display Framework, tick the controls you want to show (use the search box, or the box at the top of the list to select them all), and click the right arrow (>) to move them into Linked Controls. To take a control off the portal, tick it in Linked Controls and click the left arrow (<). Only one framework's controls can be shown at a time.
  • FAQ: answers to questions external stakeholders commonly ask. Enter a question and its answer, and click Add.

For your certifications and for each content collection you set a File Access Protocol: No Access, Access Controlled (visible only to approved visitors), or Everyone (public), so you decide exactly what is open and what is gated. For a collection, it is under Sensitive Data when you select the collection to edit it. Once configured, click Save at the bottom of the Builder tab to publish your portal and generate the shareable link you can send to external parties.

Sharing your portal link

Once the portal has been saved, its public link appears at the top of the Settings > Trust Portal page. Click the link to preview the portal as a visitor sees it, or use the copy button beside it to copy the link into an email.

 

Set sensitive items to Access Controlled rather than Everyone, so that only approved stakeholders can view them while general information stays open.

Managing access

When someone requests access to gated content, you review and control it from the Access tab of the Trust Portal settings.

  1. Go to Settings > Trust Portal and switch to the Access tab.
  2. Under Review Access Requests, approve or decline each request. Approving requires an expiry date: access is always time-limited, defaulting to one week and adjustable up to a maximum of 90 days. You can include an optional note in the email the requester receives.
  3. To remove access at any time, use the red icon under Manage Current Access. This revokes the user's access in real time and emails them to confirm the change.

How external stakeholders request access

From the visitor's side, gaining access to gated content is self-service and verified by email, so you only ever approve named requesters.

What visitors see. The portal opens on an Overview page showing your company name, domain, description and when the portal was last updated, with a tab for each content collection (for example Technologies, Sub-Processors and Key Documentation). View All expands a collection. A theme button in the header switches the portal between light and dark mode, using the logo and banner you uploaded for each. Visitors ask for gated content with the Request Access button.

The full journey runs as follows:

  1. The visitor opens your portal link and browses whatever you have made public. Anything set to Access Controlled is visible as gated rather than hidden, so they can see that further material exists.
  2. They submit a request with their name, email address and an optional note. If they already have a live or pending request on your portal, CyberHQ recognises it rather than creating a duplicate.
  3. You receive a notification and approve or decline it from the Access tab.
  4. Once approved, the visitor requests a six-digit code by email and enters it to sign in. There is no password and no CyberHQ account.

Sessions are one hour long. That hour is separate from the expiry date you set when approving. A visitor with 30 days of access still signs in again with a fresh code each hour they come back. This surprises people, so it is worth saying in the covering email if you are sending a portal link to someone who will work through a lot of evidence in one sitting.

Revoking access takes effect immediately. If the visitor is signed in at the time, their session ends as you revoke it rather than running to the end of the hour.

Seeing what visitors have done

Your portal keeps an activity log of what external visitors do while they are on it: access requested, approved, declined or revoked, each sign-in, and each file downloaded.

This is more useful than it first appears. It tells you which prospect actually opened your SOC 2 report rather than merely asking for it, which evidence gets looked at most and therefore deserves to be public rather than gated, and it gives you a record of who saw what and when if a customer later asks.