Skip to main content
It needs to be Approved in Assuric first. Until it is, you can’t add it as a resource and it won’t appear on your Trust Centre. See Approve, then publish.
Uploading to your evidence bank and publishing to your Trust Centre are 2 separate steps. Add the certificate as a resource under Trust Centre → Page Content. Full walkthrough in Choosing what to publish.
No. Link to it from your site instead, or put it on your own domain so it sits at trust.yourcompany.com. See Set a custom domain.
Framework status doesn’t sync automatically from DSPT or IASME. Update it in the admin, or get in touch and we’ll sort it.
Custom frameworks are enabled per workspace, and Add Framework stays greyed out until they are. Get in touch and we’ll turn them on for yours. See Choosing what to publish.
No. It’s a flat fee, with unlimited access requests.
You need admin permissions. Ask someone who already has them to upgrade you.
It’s the slug in your public Trust Centre URL. In trust.assuric.com/assuric/public, the workspace ID is assuric.
Yes. Most companies only need one view, since folders tend to split resources up nicely, but a second view helps when different audiences need different resources, like separate UK and US customers. See Setting up your Trust Centre.
Only for content managed inside Assuric. A document from an external tool needs to be uploaded, or its published link updated, manually.
Yes. Framework badges show Active or In Progress status, so customers can see where you stand. See Choosing what to publish.

Setting up your Trust Centre

Get your Trust Centre live, with resources organised the way your customers expect.

Choosing what to publish

Which documents customers actually ask for.