> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/group-access-policies/source-based-policies.md).

# Source-based Policies

Here's an explanation for each Source-base policy.

A Source-based Policy includes all resource-based type permissions, which user will need to assign to a selected data source that has been connected to decube. Before you can select permissions, you will need to **first select a data source** that has **been already added to decube**.

## Asset Selection for Access Controls

Administrators can grant access by two methods:

* **Grant access to everything:** This grants access to the same permissions to all assets within the data source, including future assets that are added to the source.
* **Grant access to specific assets:**
  * This grants access to the specific asset and its children (if available).
  * Selecting a parent asset grants future child assets as well eg. Granting access to a schema will grant access to all newly added tables within the schema.

### Select specific assets to grant permissions

Click on the `Select options` dropdown to search for the assets to grant permissions to.

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-1aa6d7ed72dcf450c9b606d49df4ad703ff661bb%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

Once asset selection has been completed, the user can then continue proceed to the permissions screen.

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-52a6367e5af8af9f48de26777169759899478a5b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Select Permissions for Granting Assets

Administrators can then select from a list of permissions that will apply to the selected assets in the form. The list of permissions that can be granted to the user with the permitted actions are listed in the section [Permissions for Source-based policies](#permissions-for-source-based-policies).

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-5bd3b0f047131cf0e3072f477e76e739ff81349c%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Permissions for Source-based policies

### Catalog and Governance

#### Asset Details

{% hint style="info" %}
View access for Asset Details is granted by default for all selected assets. Adding Edit option below grants additional permission to edit the asset.
{% endhint %}

* Edit: User able to create and submit change requests for an asset, such as description, classifications, and custom attributes.

#### Run the profiler for Profile & Field Statistics

* Allow run profiler: User able to run profiler to generate Table Overview and Field Statistics results.

#### Preview

* Run preview: User able to run preview to [obtain sample data](https://docs.decube.io/catalog/preview-sample-data.md).

#### Change requests

* Approve or reject change requests: User can review change requests and be selected as an approver for change requests.

### Data Quality Classic and V2

These permissions apply to monitors and cases in both Data Quality Classic and Data Quality V2. Alert rules in Data Quality V2 are not tied to a source, so you manage access to them in [Module-based policies](https://docs.decube.io/group-access-policies/module-based-policies.md#data-quality-v2).

#### Cases and incidents

{% hint style="info" %}
View access for Asset Details is granted by default for all selected assets. Adding Edit option below grants additional permission to edit the asset.
{% endhint %}

* Read-only: User is able to see cases and incidents, but unable to edit selection in Incident Details such as status.
* Edit: User is able to update selection in Incident Details such as close or mute incidents.

#### Configure monitors and alerts

* Read-only: User able to view the list of monitoring settings in the Config, but unable to create new or modify existing monitors
* Add, modify and delete monitors: User able to create and edit monitoring settings for all types of monitors.

#### Monitors associated with multiple assets

Freshness, Volume and Field Health monitors, and their cases, each belong to the single asset they run on. A Custom SQL monitor can be associated with several assets, so access works differently:

* **Monitors:** User needs access to the entire source to view or edit the monitor.
* **Cases:** User needs access to at least one of the assets the monitor is associated with to view or edit the case.

### Data Recon

By Default, access to Data Recon is disabled for a user unless they possess a policy of `Enable Data Recon`. Enabling Data Recon for a source enables users to see the list of completed recons that has been completed with that data source.

#### Data Recon Configuration

* Create: User can add a new recon configuration.
* Edit: User can edit schedule for recon configuration.
* Delete: User can delete any existing recon.

#### Export Data Recon Details

* Allow export: Allow user to export unmatched rows from Recon details.

### Reports

* Allow export reports: allowing users to access the reports module and generate reports.
