CentrlX agents work only with the records you already have in Centrl, and only within the permissions of the person using them. This document lists every object an agent can reach, the fields it returns, and which actions it can take.
This article covers the following topics:
At a Glance
Types of Access
Read means an agent can retrieve and reason over the field.
Action means an agent can change something — see Actions, below.
Automatic marks a background step the agent performs on its own.
| Object | What it covers | Access |
|---|---|---|
| Documents | Text of files uploaded to Centrl | Read · Automatic |
| Assessments | Questionnaires, their structure, answers, and history | Read · Action |
| Knowledge Base | Your curated question-and-answer library | Read |
| Issues | Findings raised against a partner or an answer | Read · Action |
| Partners | Vendors, third parties, and internal business units | Read · Action |
| Products | Products and services supplied by your partners | Read · Action |
| User profile | The signed-in user's own profile | Read |
Actions
An action is something you ask an agent to do — name it in your agent instructions or in a chat, and the agent will carry it out. Every action works the same way: the agent validates the request, shows you exactly what will change, and writes nothing until you confirm.
| Action | What it does | What you provide |
|---|---|---|
| Update a partner | Changes fields on a partner record. | The partner, plus any of: name, status, description, network company, address, or any custom attribute. |
| Update a product | Changes fields on a product record. | The product, plus any of: name, description, status, review status, or any custom attribute. |
| Create an issue | Raises an issue against a partner. | Issue name, partner, and severity are required. Optionally a description, status, sub-status, due date, attached products, and a category, rationale, or recommendation. |
| Add a clarification | Drafts a clarification question against a specific answer in an assessment. Drafting does not send it. | The assessment, the answer being queried, and the clarification question. |
| Publish clarifications | Sends one or more drafted clarifications to the recipient. Several can go out together. | The assessment and the answers whose drafts are being sent. Optionally a comment, and whether to copy the internal owner. |
Issue and clarification owners are always you. An agent cannot assign an issue to another person, and a clarification is always raised under the account of whoever asked for it.
Some actions cannot be repeated. Creating an issue twice creates two issues, and an answer can only carry one open clarification at a time. If you confirm an action, let it finish rather than asking again.
Nothing is deleted. No agent can delete a partner, product, assessment, document, issue, or user. Actions add records or change fields on records that already exist.
Documents
Access — Read · Automatic
Text extracted from files uploaded to Centrl — policies, certifications, reports, and evidence. Documents are indexed in numbered sections, so an agent can search across everything, then read a specific document in order for fuller context.
Fields available
| Field | What it contains |
|---|---|
| Document ID | The identifier for this version of the file. |
| File name | The file's name as uploaded. |
| File type | The file format, such as PDF or XLSX. |
| Section text | The extracted text of a single section of the document. |
| Section number | Which section of the document the text came from. |
| Total sections | How many sections the document contains overall. |
| Page number | The source page, for formats that have pages. |
| Linked records | The partners, products, or assessments the document is attached to, with their names and types. |
| Relevance score | How closely the section matched the agent's search. |
Agents read text, not files. The original file and its download link are never returned to an agent — only the extracted text of the sections relevant to your question.
Files from connected integrations are added automatically. When an agent fetches a file from SharePoint or Google Drive, it makes that file searchable in the same step, so the document becomes available to later searches. This happens on its own as part of fetching the file — there is nothing to set up, and it only ever adds a new document.
Assessments
Access — Read · Action
Published questionnaires the signed-in user has access to. An agent can read an assessment's status and progress, walk its sections and questions, open any individual answer, inventory its attachments, and review who did what and when.
The assessment record
| Field | What it contains |
|---|---|
| Assessment ID | The assessment's unique identifier. |
| Assessment name | The questionnaire's name. |
| Status | Workflow status of the assessment. |
| Sub-status | Secondary workflow state, where one is set. |
| Partner | The partner the assessment was sent to, with its name and ID. |
| Recipient | The person the assessment was addressed to. |
| Published date | When the assessment was published. |
| Due date | When responses are due. |
| Evaluation due date | When the review is due. |
| Answers past due | Whether answers have passed their due date. |
| Total questions | Number of questions in the assessment. |
| Answered questions | Number of questions answered so far. |
| Evaluated questions | Number of answers that have been reviewed. |
| Open questions | Number of questions still outstanding. |
| Flagged answers | Number of answers flagged during review. |
| Percent answered | Completion rate for responses. |
| Percent evaluated | Completion rate for reviews. |
| Evaluation score | Score awarded during evaluation. |
| Maximum evaluation score | The highest score the assessment could achieve. |
| Grade | The grade awarded, with its name, description, and the score band it covers. |
| Scale type | The scoring scale the assessment uses. |
| Total issues | Number of issues raised against the assessment. |
| Clarification count | Number of clarifications raised. |
| Attached file count | Number of files attached across the assessment. |
| Requested document count | Number of documents formally requested from the recipient. |
| Summary of findings | The written summary recorded on the assessment. |
| Smart evaluation status | Where automated evaluation has reached, where it is used. |
| Custom attributes | Every custom assessment field your company has configured. |
Sections and questions
| Field | What it contains |
|---|---|
| Section name and number | Each section and subsection, nested as they appear in the questionnaire. |
| Question count | How many questions the section holds. |
| Section status | Where the section stands. |
| Evaluation comments | Review comments on the section, each with its author, date, and whether it was written by automated evaluation. |
| Question number and text | The question as it appears to the recipient. |
| Answer type | The kind of answer expected, such as Yes/No, Text, or Choice. |
| Answer value and comments | What the recipient answered, and anything they added alongside it. |
| Grade | The grade given to the answer during review. |
| Risk level | The risk recorded against the answer. |
| Flagged | Whether the answer was flagged during review. |
| Answered / evaluated | Whether the question has been answered, and whether it has been reviewed. |
| Mandatory | Whether the question is required. |
| Has attachments | Whether files are attached to the answer. |
| Has requested documents | Whether documents were formally requested for this question. |
| Issue count | Number of issues linked to the answer. |
Answer detail
| Field | What it contains |
|---|---|
| Everything above | Opening a single answer returns all the question and answer fields listed above, plus the following. |
| Evaluation comments | Each review comment on the answer, with its author and date. |
| Attachments | The files attached to the answer, with their names and identifiers. |
| Requested documents | Each document requested for this answer, and whether it has been provided. |
Attached documents
| Field | What it contains |
|---|---|
| Question | The question and answer the file is attached to. |
| Fulfils a request | Whether the file answers a formal document request, and which one. |
| File name and size | The file as uploaded. |
| Attached on | When the file was attached. |
| Attached by | Who attached it. |
Activity history
| Field | What it contains |
|---|---|
| Action | What happened, such as publishing the assessment, assigning answers, or adding a clarification. |
| Who | The person who took the action. |
| When | When it happened. |
| Comment | Any comment recorded with the action. |
| Target user | The person the action was directed at, where one applies. |
| Question or section | The part of the assessment the action related to. |
Two ways to reach an answer. An agent can search all answers by meaning — asking about encryption finds relevant answers even where the wording differs — or walk an assessment section by section to a specific question. Searching returns the question and answer text with a relevance score; walking returns the full detail above.
Actions available: an agent can draft and send clarification questions against individual answers. It cannot publish, send, reassign, or close the assessment itself, and it cannot change an answer or a grade.
Knowledge Base
Access — Read
Your curated library of approved questions and answers, also known as the Answer Library. Agents use it for general policy and reference questions that aren't tied to a specific document or assessment.
Fields available
| Field | What it contains |
|---|---|
| Entry ID | The knowledge base entry's unique identifier. |
| Question and answer | The question text together with the curated answer. |
| Question number | The entry's identifier within the library, where one is set. |
| Answer type | The kind of answer recorded, such as Yes/No, Text, or Choice. |
| Partner | The partner the entry applies to, when it is partner-specific. |
| Relevance score | How closely the entry matched the agent's search. |
Issues
Access — Read · Action
Findings raised during an assessment. An agent can list the issues on an assessment, or narrow to the issues linked to one particular answer.
Fields available
| Field | What it contains |
|---|---|
| Issue ID and number | The issue's identifiers. |
| Name | The issue title. |
| Description | The detail recorded on the issue. |
| Severity | How serious the finding is. |
| Status | Where the issue stands. |
| Owner | The person responsible for the issue. |
| Partner | The partner the issue was raised against, with its name and ID. |
| Created on | When the issue was raised. |
| Due date | When the issue should be resolved. |
| Target completion date | The date targeted for completion, where one is set. |
| Source | Where the issue originated. |
| Linked answers | The assessment answers the issue relates to. |
Actions available: an agent can raise a new issue against a partner. It cannot edit, reassign, resolve, or close an existing one.
Partners
Access — Read · Action
Records from your Partner Directory — vendors, suppliers, third parties, and internal business units. Agents can list partners, find one by name or ID, and filter on your custom attributes.
Fields available
| Field | What it contains |
|---|---|
| Partner ID | The partner's unique identifier in Centrl. |
| Partner name | The partner's name as it appears in your directory. |
| Status | Lifecycle status, such as Active or Inactive. |
| Description | Free-text description of the partner. |
| Company domain | The partner's linked company on the Centrl network, where one exists. |
| Assessment count | Number of assessments associated with the partner. |
| Document count | Number of documents attached to the partner. |
| Issue count | Number of issues raised against the partner. |
| Product count | Number of products linked to the partner. |
| Custom attributes | Every custom partner field your company has configured, under your own labels. |
Actions available: an agent can update a partner's name, status, description, network company, address, and any custom attribute. Partner IDs and record counts are read-only. An agent can also raise an issue against a partner.
Products
Access — Read · Action
The products and services your partners supply. Agents can list every product for your company and filter by product or owning partner.
Fields available
| Field | What it contains |
|---|---|
| Product ID | The product's unique identifier in Centrl. |
| Product name | The name your company uses for the product. |
| Description | Free-text description of the product. |
| Status | Whether the product record is active. |
| Review status | Where the product sits in your review workflow. |
| Owning partner | The partner that supplies the product, with its name and ID. |
| Document count | Number of documents attached to the product. |
| Custom attributes | Every custom product field your company has configured, under your own labels. |
Actions available: an agent can update a product's name, description, status, review status, and any custom attribute. Product IDs and the owning partner link are read-only.
User Profile
Access — Read
An agent can read the profile of the person using it, so it can address them correctly and apply their permissions. There is no way for an agent to browse your user directory or look up anyone else.
Fields available
| Field | What it contains |
|---|---|
| User ID | The signed-in user's identifier. |
| Full name | The user's display name. |
| User type | Whether the user is a subscribed user or an external guest. |
| Company name | The company the user belongs to. |
| Language | The user's language preference. |