Conveyor

What is Conveyor?

Conveyor is a security review platform. Security, trust and sales teams use it to run a customer-facing Trust Center, answer security questionnaires and control who can see sensitive documents such as audit reports and policies. Prospects request access, sign an NDA where required, and review the material themselves.

Conveyor makes the security review faster. The review is one part of a larger response, though. The same tender asks for a technical memo, a hosting description and a proposal. The bid team writes those from whatever version of the security material they last saw, while the approved version sits in the Trust Center.

Let the documents your security team cleared back every claim in the response

Cobl reads the Trust Center documents and folders you connect in Conveyor, along with the access requests prospects have made. That material becomes context inside the deal workspace, next to the questionnaire response, the technical memo, the sales deck and the proposal for the same deal.

The result is consistency across the RFP response. The technical memo describes encryption the way the policy describes it, and the proposal refers to the audit report that is actually current. A security reviewer and a commercial evaluator read different documents, and they find the same answer in both.

What Conveyor and Cobl look like on a live deal

A mid-market deal reaches the security stage. The buyer's security team requests access to the Trust Center and reviews the audit report and the data protection policy. In parallel, procurement sends the RFP pack, with a technical section on hosting, encryption and backups. The bid manager connects the relevant Conveyor folders to the Cobl deal workspace. The technical memo and the RFP response draw on the same cleared documents the buyer's security team is reading.

The access request is useful context in its own right. It shows who on the buyer side asked for access and when, which tells the bid team where the security review stands while the rest of the response is being written. The security team is not pulled back in to re-explain what it already published, and nothing leaves the workspace without review.

Key features of the Cobl Conveyor integration

Trust Center documents as source material

Cobl draws on the documents and folders you connect in Conveyor: audit reports, policies, security overviews and whatever else your team published. The response is built from the approved version, not from a copy saved to someone's desktop last year. When the Trust Center is updated, the next draft works from the update.

Access requests on the deal

Authorization requests show who on the buyer side asked for access and when. Attached to the deal, that context tells the bid team the security review has started. It sits alongside the documents being written, instead of in a notification only the security team sees.

One security answer across every document

The questionnaire response, technical memo, deck and proposal share one source. A statement about hosting or encryption reads the same in each. That matters when the documents arrive together and a reviewer compares them line by line.

Cleared answers kept for the next bid

Security answers approved in one response go into the Shared Drive and feed later bids. The Trust Center stays the reference for what is current. The Shared Drive holds how your team phrased it for buyers, so the next response starts from wording that already passed review. Technical documentation in Confluence and past responses in SharePoint feed the same workspace, as does the opportunity record in Salesforce.

Frequently asked questions

Does Cobl integrate with Conveyor?

Yes. Cobl connects to Conveyor so Trust Center documents and prospect access requests can inform the technical memo, the proposal and the RFP response for a deal. The approved security material reaches every document in the workspace, not only the questionnaire.

What Conveyor data does Cobl access?

The Trust Center documents and folders you connect, and the authorization requests linked to the deal. Content you do not connect is not part of the deal context. Cobl reads through the access the connected account already holds.

Does Cobl replace Conveyor for security questionnaires?

No. Conveyor runs the security review and the questionnaire workflow for your security team. Cobl runs the rest of the response and makes sure it says the same thing as the material that team already cleared. The two cover different documents in the same deal.

Some of our Trust Center documents are behind an NDA. Does that matter?

Cobl uses them as context for drafts that your team reviews. What goes to the buyer is what your team approves, so detail from an NDA-gated document only appears in a response if someone decides it belongs there. The access rules in Conveyor stay as they are.

Can this help with the security section of an RFP?

Yes. The security section of an RFP usually asks questions your Trust Center already answers. Connected to the deal, those documents feed that section directly. More on how Cobl itself handles data sits on the security page.