---
title: "Policy Center: Filling out the Policy Overview"
url: "https://atlan.com/demos/filling-out-policy-overview/"
description: "Accelerate policy creation with Atlan AI, automatically generating purposes and definitions, saving significant time for data teams."
format: "Video"
video: "https://videos.ctfassets.net/nwa1c00rtgxb/21fqAIFJMos2hLMWuAHAtT/b875832f0c90651fede38c632b0c6965/Filling_out_the_Policy_Overview.mp4"
content_purpose: ["Product Overview"]
target_persona: ["Data Steward"]
journey_stage: ["S2 - Discovery", "C1 - Onboarding", "C3 - Adoption"]
use_case_context: ["Training"]
product: ["Data Marketplace - Data Governance"]
content_type: "video transcript"
transcript_source: "contentful"
---

# Policy Center: Filling out the Policy Overview

Transcript of the video at https://atlan.com/demos/filling-out-policy-overview/

<!-- Body: machine transcript stored on the Contentful entry (field contentBody), timestamps kept, product names corrected. Not yet edited by a person. -->

Filling out the Policy Overview

[00:00] Now that the policy has been created, it's time to fill out the details so it can be ready for approval and put into production. The first item to fill out is the purpose. The purpose should be just that, the actual purpose of the policy that is being created. Clicking on the right policy purpose allows you to manually document this.

However, this is where Atlan AI can be a game changer as writing policy purposes can be a time consuming task by clicking on Ask Atlan ai, the section updates To show the AI purpose generation Here you are able to first enter in your industry whether or not the policy is global, local, or regional. If the type of policy is a standard compliance, a regulation, or something else, you can enter in the name of the compliance or regulation the policy is for, and finally give the description of the policy.

Alan AI takes all this information and creates the purpose for you. In this case, we'll enter the industry [01:00] of finance, enter in the compliance of PCI, and since this policy is around data retention, we put in this policy is to adhere to the data retention needs of PCI compliance. Clicking generate purpose kicks off Atlan ai. And in just a few short moments, we see the results. We can stop AI from continuing to write. If we deem the information provided already as enough, we are now able to review the purpose created by Atlan AI making updates where needed, saving us a ton of time in ensuring that the purpose aligns with our need.

Clicking save updates the purpose. Next on the overview page, exceptions allow us to document any individuals or entities that do not have to adhere to the policy itself.

Not all policies will have exceptions, but this allows you to add those when needed.

Clicking on add policy exception brings the new exception creation tab. At the top, we add the exception name, which we recommend adding in the users or [02:00] entities in the exception name, to allow for easy understanding and accessibility of whom is exempt from this policy.

Next is entering the reason for the exception, outlining why the exception exists and what situation addresses. Finally, if specific users or groups are part of the exception, they can be added by clicking on the user's field, bringing up the user selection, where you can select individual users to add or clicking on the groups tab, add any of the groups for selection.

Clicking add exception creates the exception and adds it to the policy. Policies can also be linked to terms from the glossary, allowing for additional context on the policy to be added, such as the definition of private consumer information or what a customer is. It's also a great way to link more generic policies to a single compliance that may be documented inside of your glossary.

Clicking on the plus button brings up the glossary popup where we can use the hierarchy to find the term we're looking for, or search at the top for a specific [03:00] term when one is identified to be added.

Clicking on the check box to the right of the term, select it and simply clicking away from it will link the term to the policy. The policy details are to the right. We can update the type of policy in owners by clicking on the edit button. Below these, is the period of validity. This is a required field that we must add in order to submit our policy for approval. This allows us to designate for how long the policy when approved will be valid during this valid period. The policy will continue linking automatically to assets within its scope, along with a evaluating those assets and producing any incidents based on the rules.

If the policy is not reapproved before expiry, the policy will deprecate delinking the assets from it, along with closing all of the open incidents. This date should be chosen based upon your normal review cadence for all policies. So working with the team that will be reviewing the policy before approval is recommended to determine the date.

Clicking on the plus [04:00] button brings the calendar selector where you can select the date. For our policy, we select a year from today's date Below this is the review period. This defaults to 30 days, and once a policy's valid period is within that timeframe, a banner will show at the top of the policy itself that it is within the review period, giving indication that the policy needs to be submitted for re-approval prior to it expiring.

We will leave this at 30 days and below we can see both when the policy was last modified and also by whom it was created. We have filled out all the required information on the overview page. However, the submit for approval button is not currently active. Hovering over it brings a pop-up listing the items that must be completed before submitting for approval.

Here we see that we still need to actually define the policy itself, the scope, and any rules to apply to the policy and the approval workflow that will be used for this policy. Clicking on the policy tab [05:00] updates the page. It shows the purpose that we previously created, but also shows the policy definition below. Clicking on write policy opens the editor, which similar to readme's, allows for markups and embedding of other documents such as Word documents.

But again, we're going to use the power of Atlan AI to help reduce the amount of work we need to do. Clicking on Ask Atlan, AI triggers it to write a draft of the defined policy for us. And once completed, we're able to update it and make edits to meet our needs, saving a ton of time and allowing us to make changes where needed.

Clicking save applies the definition, completing this requirement. Next is to add the scope and rules for the policy.
