> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/publisher/access-policies/creating-an-access-policy.md).

# Creating an Access Policy

## Overview

[Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/access-policies/broken-reference/README.md) administrators can create custom access policies to manage collection access. This guide walks through creating and configuring a new controlled access policy.

## Basic Policy Setup

Start by navigating to [Access Policies](/products/publisher/access-policies.md) through the left sidebar and clicking "Create Policy" in the top right corner. Enter a descriptive name for your policy that reflects its purpose or the group it governs.

## Configuring Access Permissions

### Allow List Configuration

To restrict access to specific users, add their email addresses to the policy. Enter addresses in the text field, separating multiple entries with commas or line breaks.

For example: <researcher1@institution.edu>, <researcher2@institution.edu>

### Access Request System

You may allow users to apply for access to collections with this policy. Enable the access request feature to let users request permission to view controlled [collections](/products/publisher/collections.md).

#### You can handle requests in two ways:

When managing requests through [Publisher](https://github.com/DNAstack/dnastack-product-docs/blob/main/docs/publisher/access-policies/broken-reference/README.md):

1. Provide a reply-to email address for communications
2. Create a custom request form with relevant fields
3. Preview and adjust the form layout as needed
4. Save your form configuration

Alternatively, you can link to an external request system by providing a URL to where data consumers can apply for access

## Terms of Use Integration

To include **Terms of Use** with your policy:

1. Enable the "Terms of Use" feature
2. Enter the URL where your terms document is hosted
3. Specify the terms version number
4. Choose whether to require explicit acceptance

{% hint style="warning" %}
If "Require Acceptance" is enabled when you update either the "Terms of Use" or "Version" number, users must accept the new terms to maintain access.
{% endhint %}

## Finalizing Your Policy

After configuring your settings, save the policy to make it available for use with collections. The new policy will appear in your [Access Policies](/products/publisher/access-policies.md) dashboard, where you can monitor and manage access requests.

{% hint style="info" %}
Remember that you can modify these settings later as your access control needs evolve.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omics.ai/products/publisher/access-policies/creating-an-access-policy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.