> For the complete documentation index, see [llms.txt](https://happybara.gitbook.io/proper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://happybara.gitbook.io/proper/reference/discussions/admin-settings.md).

# Admin Settings

### Like all Proper features, Polls offer granular admin settings and approvals.

{% hint style="info" %}
See [**this page**](/proper/reference/admin-settings.md) for **global** admin settings.
{% endhint %}

#### From the admin setting modal for any feature, use the overflow menu at the top to navigate to another feature.

![](/files/-MWgi2Relqn07dGxlP6w)

#### Any Proper major feature can be enabled or disabled using the checkbox in the second panel of its admin settings modal.

### Approvals

#### App or workspace admin approval can optionally be required for users to:

* Start a new discussion
* Post a reply to an ongoing discussion

{% hint style="info" %}

#### If approval is required for a user action, the user is able to select which admin(s) will receive an approval request message.

* Only one admin needs to approve or deny each request.
* When an admin approves or denies a request, other admins and the requesting user will be notified.

Workspace admins and app admins do not need to seek approval for these actions.
{% endhint %}

### User permissions

#### A list of users can be defined that can use discussions without needing to seek approval.

{% hint style="info" %}
Workspace admins and app admins already have this capability.
{% endhint %}

### Channel permissions

#### A list of up to 25 public channels can be defined where approval is not required to start a discussion.

{% hint style="info" %}
If this setting is enabled, discussions in **other** channels **will require approval** regardless of the approval settings above.
{% 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://happybara.gitbook.io/proper/reference/discussions/admin-settings.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.