--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Manage elements in the grid # Manage elements in the grid {#ariaid-title1} Release version: Australia Updated September 14, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Manage third-party elements in the Elements grid by adding, editing, and deleting records. You can also link AI models to AI use case elements in the Third-party Risk Management application. ## Before you begin Role required: * Vendor Management Workspace: sn_vdr_risk_asmt.vendor_assessor, sn_vdr_risk_asmt.vendor_risk_manager * Third-party portal: vendor_contact {#tprm-elements-grid-manage__ul_mdw_dn2_hkc} For more information, see [Create a task for an internal user](https://www.servicenow.com/docs/kyn77PcE8xCw89s0x~TT2w "Create an internal task to assign follow-up work to an internal user, rather than to a third-party contact, as part of your organization's third-party risk processes."). ## About this task The Elements grid is available on a third party record, on an engagement's Elements tab, and embedded in a collection task in the Vendor Management Workspace or third-party portal. Some fields in the grid are specific to the element's classification. For example, AI model and AI use case elements have fields that don't apply to other classifications. The grid organizes elements into a tab for each classification. Tabs can include: Principal, Facility, Product, AI model, AI use case, and Other. If you create a classification, its tab is added automatically in the order set on the classification record. Depending on your role, the Classification and Third party fields can be read-only when you edit or create an element in the grid. When all fields in the side panel are read-only, the Save button isn't shown. Third-party portal users with the vendor_contact role can access the Elements grid to add and edit elements as part of element collection workflows. Whether a field is read-only depends on the portal user's role and the task context. ## Procedure 1. Open the Elements grid. * From a third-party or engagement record, navigate to the Elements tab. * From a collection task, select Manage elements. {#tprm-elements-grid-manage__choices_open_grid} 2. To add an element, select Add and fill in the fields for the new element. Some fields are static and appear for every element regardless of classification. Other fields are dynamic and appear only for certain classifications. AI use case and AI model elements have additional dynamic fields beyond the static fields shared by every element. For the complete list of dynamic fields for these classifications, see [AI use case and AI model element fields](https://www.servicenow.com/docs/KANqgxmccsL_uHswt3ln3w "The Elements grid displays dynamic fields when you add or edit an AI use case or AI model element in the Third-party Risk Management application."). 3. To edit an element, select it in the grid. A side panel opens showing the element's form. 4. If you're adding or editing an AI model element, select or clear Global AI model. A global AI model is available for linking to AI use case elements across multiple third parties. A local AI model (with Global AI model cleared) is available only within the third party where it was created. 5. If you're adding or editing an AI use case element, link the AI models that the use case relies on. You can link AI models created within the same third party and any AI model marked as global by another third party. 6. Select Save. 7. **Optional:** To delete or unlink and element, select the element in the grid, then select Delete. This option is not available to third-party contacts. On a third party's Elements grid, this permanently deletes the element record and its engagement associations. On an engagement's Engagement elements grid, this only unlinks the element from that engagement; the element record itself isn't deleted and remains available on the third party. {#tprm-elements-grid-manage__steps_a5h_vr2_jkc} ## Result Elements you add appear in the grid. Elements linked to an engagement are available for assessment in your due diligence process. When you open an element in the side panel, certain fields can be read-only depending on your role and the element's context: * For TPR assessors and managers in the Vendor Management Workspace, most fields are editable to support element management. * For third-party portal users with the vendor_contact role, some fields (such as Classification or Third party) can be read-only to maintain data consistency during element collection tasks. * When all fields in a side panel are read-only, the Save button doesn't appear. {#tprm-elements-grid-manage__ul_v5v_jkt_4kc} **Related concepts** * [Monitoring third-party elements](https://www.servicenow.com/docs/Y_fxTAUDrR5N9jLlvmFTVQ "Monitor third-party elements using scalable scoring models, relationship analysis, and due diligence workflow integration in the Third-party Risk Management application to conduct more informed risk assessments as part of your third-party risk program.") **Related tasks** * [Create a third-party element](https://www.servicenow.com/docs/RpYueTUp9lISuofHVuJf1Q "Create a third-party element directly in the Elements grid in the Third-party Risk Management application. Third-party elements are assessed as part of the due diligence workflow.") * [Add a third-party element record to an engagement](https://www.servicenow.com/docs/VAvw45wumV0SAoT8PVGerA "Link a third-party element to an engagement by using the Third-party Risk Management application. After linking the element to an engagement, the third-party risk manager and internal stakeholders can assess it as part of the due diligence process.") * [Complete an element collection task](https://www.servicenow.com/docs/P3nMP9VtTWVLi7ihq55sfQ "Element collection tasks let internal users add AI use case elements and let third-party or engagement contacts add elements on behalf of the third party in the Third-party Risk Management application.")