> For the complete documentation index, see [llms.txt](https://help.santesuite.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.santesuite.org/operations/cdr-administration/santedb-icdr-admin-console/policy-administration.md).

# Policy Administration

You can use the iCDR administrative console to list policies and assign policies to objects within the iCDR instance. Creating new policies needs to be done through the UI. For more information visit [Security Policy Management](broken://pages/-LyJMeXTqUGM9ThfTS7k).

## Viewing Policies

You can view all security policies configured on the server using the `policy.list` command, specifying optional filter parameters.

```
> policy.list
SID                                    Name                                   Oid                                       
a14d0096-d62a-11eb-8248-00155d640b09   Create-Policy-Test                     1.3.6.1.4.1.3349.3.1.5.9.2.99.4           
57a36a62-d5c5-11eb-8248-00155d640b09   Access HIV ART Number                  1.3.6.1.4.1.3349.3.1.5.9.2.99.2           
62073cae-8c1e-11eb-be65-00155d640b09   Testy Mctesterson                      1.3.6.1.4.1.66666.3.1.5.9.2.0.14          
598c0e00-82fb-11eb-8dcd-0242ac130007   Read PubSub Subscriptions              1.3.6.1.4.1.33349.3.1.5.9.2.0.14.4        
598c0e00-82fb-11eb-8dcd-0242ac130006   Delete PubSub Subscriptions            1.3.6.1.4.1.33349.3.1.5.9.2.0.14.3        
```

The optional filter parameters for `policy.list` are.

| Parameter | Description                              | Example                            |
| --------- | ---------------------------------------- | ---------------------------------- |
| `-n`      | List policies with specified name        | `policy.list -n test`              |
| `-o`      | List policies with specified OID pattern | `policy.list -o 1.3.6.1.4.1.33349` |

## Assigning Policies

You can assign security policies to devices, roles, and/or applications by using `policy.assign` command,  followed by specifying parameters.

| Parameter               | Description                                     |
| ----------------------- | ----------------------------------------------- |
| `-r` or `--role`        | The role(s) to assign the policy to             |
| `-a` or `--application` | The application(s) to assign the policy to      |
| `-d` or `--device`      | The device(s) to assign the policy to           |
| `-e` or `--rule`        | The action to take (0/deny, 1/elevate, 2/grant) |
| `-p` or `--policy`      | The policy(ies) to apply                        |

{% hint style="info" %}
The object parameter ( role or application or device ) is required. 

The policy parameter is required.

The action parameter (`-e` or `--rule`) specifies the action to take and by default is set to 0 (Deny) if not specified.
{% endhint %}

**Example:**

```
> policy.assign -a Create-Application-Test -e 2 -p 1.3.6.1.4.1.33349.3.1.5.9.2.999
Grant: Override Disclosure TO Create-Application-Test
>
```

```
> policy.assign -a Create-Application-Test -p 1.3.6.1.4.1.33349.3.1.5.9.2.999
Deny: Override Disclosure TO Create-Application-Test
>
```


---

# 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://help.santesuite.org/operations/cdr-administration/santedb-icdr-admin-console/policy-administration.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.