---
sourceDocument: Xanadu Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/governance-risk-compliance

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Configure 360° relationship registries and views

# Configure 360° relationship registries and views {#ariaid-title1}

* Release version: Xanadu
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure 360° view configurations with the sn_bcm.admin role.

## Before you begin

Role required: sn_bcm.admin

## Procedure

1. Navigate to All360° View ConfigurationsConfigure 360° Views.
2. To configure the relationships for the records, navigate to 360° View ConfigurationsRelationship Registries.  
   The form is shown in the example.

3. On the form, fill in the fields.  
   {#configure-relationship-registries-views__table_epy_qrq_f5__entry__2}

   | Field | Description |
   |-|-|
   | Name | A descriptive name for this registry. |
   | Table | The table for which you want to define a relationship. |
   | Relationship type | The type of relationship you are defining: * One-to-many * Many-to-many * Scripted: a custom relationship from the ServiceNow AI Platform * One-to-one: any relationship that is available as a field in the selected table {#configure-relationship-registries-views__ul_m5g_h2d_pqb} |
   | Active | Select if the relationship is active. |
   | Relationship | The relationship table of the selected relationship type. For example, if you are defining relationships for the Entity table and select a many-to-many relationship type, the list of relationship tables consists of all many-to-many relationships that apply to the Entity table. |
   | Relationship table | The table name you selected in the Relationship field. |
   [Table 1. Create new relationship registry]

   {#configure-relationship-registries-views__table_epy_qrq_f5}
4. Select Submit.
5. To configure 360° views for the records, navigate to 360° View ConfigurationsConfigure 360° Views.  
   The form is shown in the example.

6. Save the record.  
   The Relationship Registries related list appears.
   Figure 1. Relationship registries
7. Choose Select Relationships.
8. On the form, fill in the fields.  
   {#configure-relationship-registries-views__table_lsf_x52_qqb__entry__2}

   | Field | Description |
   |-|-|
   | Name | A name to identify this relationship. |
   | Data relationship | The data relationship you previously defined. |
   | Relationship table | The table associated with the selected data relationship. |
   | Node position | The sector you previously defined to which you want to add this relationship. |
   | Filter | Enter conditions to define the types of relationships you want to display. For example, you could define conditions for all controls with failures. |
   | Configuration | The configuration defined for the relationship. |
   | Table | The table defined for the relationship. |
   | Order | Based on the Order value given the position of element in the 360º view will change. For example, if you change the order value from 0 to 1 for an element, the position will be moved to next in the 360ºview. |
   [Table 2. DataNav Config to Data Relationship]

   {#configure-relationship-registries-views__table_lsf_x52_qqb}
9. Select Submit.  
   The new view you have defined is now available on the 360º view.Figure 2. Selecting a new view

   For more information on 360° views configurations, see [Configure 360º views](https://www.servicenow.com/docs/TsiS9svYN92ii0A0HZAG~w#configure-360-views "After the data registry has been defined, you can configure the 360° Relationship Visualization to effectively display the relations you created.").
{#configure-relationship-registries-views__steps_bx5_z55_fyb}

*[\>]: and then