---
title: "Using Astra with Agiloft CLM"
canonical: "https://help.agiloft.com/space/HELP/570327053/Using+Astra+with+Agiloft+CLM"
format: markdown
---
Your Agiloft CLM grants you a few additional ways to access and use Astra, formerly Screens. This page discusses those additional options that are unique to the integrated experience with both Astra and Agiloft CLM.

> 📝 For more ways to use Astra day-to-day, visit [Using Astra](https://agiloft-public.atlassian.net/wiki/spaces/Astra/pages/543621131).

# Access Astra from Agiloft CLM> Macro (anchor)



To access Astra from Agiloft CLM:

1. Go to **Setup > Analyze with Astra**.
2. Confirm your KB information and then click Connect.
  1. For Server URL, copy your KB's URL, only copying from `https://` to `.com`, or similar. Don't include the trailing slash.
  2. For KB Name, copy the name of the KB located in the right corner of your KB.
3. Click Connect and then log in with your Agiloft CLM credentials.

The first time you sign in, if prompted, select your data residency from the drop-down list. This choice is applied to the rest of your organization, and cannot be changed. In many cases, this is chosen automatically based on the residency of your KB. CLM customers are allotted 1 workspace per KB.

Logging in redirects you to Astra, where you can begin [Using Astra](https://agiloft-public.atlassian.net/wiki/spaces/Astra/pages/543621131) and [Building Screens in Astra](https://agiloft-public.atlassian.net/wiki/spaces/Astra/pages/545194000). 

# Analyze CLM Documents with Astra

If you use Astra alongside Agiloft CLM, make sure you open documents directly from your KB using the Checkout & Edit option. From there, use the Astra Word app to screen your documents. 

You can technically upload documents directly to the Astra web app, or open a document in Word and run a screen, regardless of whether the contract is in the KB. This will not write results back to your KB for these documents, and is naturally not recommended for those seeking KB integration.

> ✅ If you open the document from Agiloft CLM, the screen results are reflected in Agiloft CLM too, in the Screen Result and Screen Run tables. Share this tip with your users to make sure your Astra data is represented in your KB.

# Use Astra Data in Agiloft CLM

If you run a screen from an Agiloft CLM document, you can review your results in Agiloft CLM in these tables:

- [Screen Runs](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434100): This table stores the overall results of a document screen.
- [Screen Results](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/44434110): This table stores the detailed results for each standard or question evaluated in a screen run.

These tables make it possible to show your results in contracts, company records, and more, and even add automation that acts on those results.

# Obligation Management

With obligation management, you can use [Screen Run Actions](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/120553719) to automatically extract obligations from a contract document and put them directly in the associated Contract record.  
You must be using version 33.2 or later of Agiloft to deploy obligations management successfully.

### Setting Up Obligation Management

To set up obligation management, use the deployment to automatically create the necessary entities:

1. Go to **Setup > Integrations**.
2. Scroll down to Screens, where you should see a message saying Deployed. If not, click the Deploy button. Otherwise, click Upgrade.
3. Scroll down to Obligations and click Deploy. This can take up to 5-10 minutes. If the deployment fails at any stage, raise a support ticket with details of the server, the KB, and the error message. The error message can be found in the red box that appears in the Obligations section after a failed deployment. When the issue is resolved, return here and click Upgrade, which replaces the Deploy button.

Now, add your new fields to the Contract layout.

> 📝 If you’re missing any of the fields or actions listed below, raise a support ticket for assistance, as these entities should have been created in the deployment.

1. Go to Setup [Contracts] and go to the Layouts tab.
2. Add the following fields, which were created in the obligations deployment:
  - Select Attachment to Run Screens On
  - Button: Extract Obligations
  - Extracted Obligations
3. Click Finish.

Next, check to see if you need to update your Import action.

1. Go to Setup [Screen Results] and go to the Actions tab.
2. Edit the T: Create Obligations action.
3. On the Data Source tab, scroll down to the Upload Sample section and select the Sample Text option.
4. In the Sample Text field, check to see if the following text is present. If not, paste the following:  
`{`  
`  "Percentage Amount": 10,`  
`  "Percentage Basis": "Contract Amount",`  
`  "Consequence": "Ten Percent (10%) of the total contract value will be paid upfront within 5 days of contract execution.",`  
`  "Trigger Type": "Time-based",`  
`  "Consequence Standardized": "10%",`  
`  "Fixed Amount": null,`  
`  "Due In Days": 5,`  
`  "Trigger": "Execution Date",`  
`  "Obligation Type": "Financial",`  
`  "Summary": "Yes",`  
`  "Responsible Party": "Client",`  
`  "Summary Standardized": "Yes",`  
`  "Due Date": null`  
`}`
5. Go to the Table tab.
6. Select Obligations from the Table drop-down list, then click the Fields tab.
7. Verify that the following fields are mapped to each other. If not, map the following fields now:
  1. Map Consequence to Consequence.
  2. Map Consequence Standardized to Consequence Standard.
  3. Map Due Date to Due Date.
  4. Map Due in Days to Due in Days.
  5. Map Fixed Amount to Amount - Fixed.
  6. Map Obligation Type to Topic.
  7. Map Percentage Amount to Amount - Percentage.
  8. Map Percentage Basis to Percentage Basis.
  9. Map Responsible Party to Responsible Party. *Do not map this to Responsible Party ID*.
  10. Map Summary to Answer.
  11. Map Summary Standardized to Summary Standardized.
  12. Map Trigger to Trigger.
  13. Map Trigger Type to Trigger Type.
8. Check that the following fields are mapped to each other. If not, do so now; add the following Source Table Fields by clicking Add Field, and then map them to the respective Target Table Fields:
  1. Map Agiloft Contract ID to Contract ID.
  2. Map Screen Agiloft ID to Screen Run ID.
  3. Map Metadata Type ID to Subtopic: ID.
  4. Map Agiloft Attachment ID to Attachment ID.
  5. Map ID to Screen Result ID.
9. Click Finish in the Actions wizard.
10. Click Finish.

You can optionally add Obligations to your top navigation bar. To do so, follow the general steps at [https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714797](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714797).

### Using Obligation Management

To use obligation management:

1. Open the Contract record with a status of Signed and navigate to the Obligations tab.
2. On the Tasks and Obligations tab, select a document and click Extract Obligations to automatically run a screen. If prompted, select an obligation screen and click Screen Document. This is determined by the Screen Run action configuration.
3. The table then displays obligation metadata under the Obligation Data section, such as the Topic, Review Status, and Pinpoint Citation, which reflect the text of the obligation. This information is permanently stored in the Obligations table, in the Extracted Obligations field.
4. To create action items from extracted obligations, you can click Create Tasks from the Obligation Management section.

If you don’t see all the elements described here, or if you want to learn more about how this works, see [Screen Run Actions](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/120553719) or [Obligation Management](https://agiloft-public.atlassian.net/wiki/spaces/SD/pages/237240328).