> For the complete documentation index, see [llms.txt](https://happybara.gitbook.io/nightowl/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/nightowl/reference/admin-settings.md).

# Admin Settings

### Workspace admins have access to admin settings by default, but standard users can be granted permission to act as app admins. <a href="#app-admins" id="app-admins"></a>

#### Workspace and app admins can manage admin settings and features in Nightowl that standard users cannot. &#x20;

Workspace admins and existing app admins can add new app admins from the **Admin Settings** modal.

{% hint style="info" %}
Granting a user app admin permissions does **not** make the user a workspace admin.
{% endhint %}

#### To access the Admin Settings modal, click the :closed\_lock\_with\_key:`Admin Settings` button in the [App Settings](/nightowl/getting-started/app-settings.md) modal.

{% hint style="info" %}
Users that are not app or workspace admins can request app admin permissions by clicking the :raised\_hand:`Request admin permissions` button in the [**App Settings**](/nightowl/getting-started/app-settings.md) modal.
{% endhint %}

### To grant a user app admin access, add their name to the list at the top of the Admin Settings modal.

> Adding or removing app admins will notify affected users about the permission change.

### Workspace and app admins can require approval for access to the standard features of Nightowl. <a href="#app-access" id="app-access"></a>

#### To enable access control, check the following box in the Admin Settings modal.

![](/files/-MJchu9sFLs-kEAS_ie-)

* Once this setting is enabled, a field will be exposed where users can be selected to enable their access to the **standard features** of **Nightowl**.

  > Any **existing** nightowl users will be added to the field by default upon enabling the setting.
* **Adding** users to the list will invite them to use **Nightowl**.

  > Users will only be added to the billing count upon successfully installing the app after being invited.
* **Removing** users from this list will revoke their access to **Nightowl.**

  > Users will be notified of this change and will be removed from the billing count.

#### When access control is enabled, new installs by users not granted access in the list will not impact the billing count.

{% hint style="warning" %}
Unapproved users will be **unable** to use **Nightowl** without seeking approval from an app or workspace admin.

* These users will be prompted to seek approval upon install and afterward if attempting to use the app prior to approval.
  {% endhint %}

{% hint style="info" %}

#### If approval is required for a user action, the user is able to select which admins should receive an approval request message.

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

### Workspace and app admins can disable one or more Nightowl features. <a href="#feature-toggle" id="feature-toggle"></a>

#### To disable a feature, uncheck the corresponding box.

![](/files/-MUlYPQsdItXnSW03Hee)

{% hint style="info" %}
Unchecking a box disables that feature and all users will lose access to it in the **Nightowl** App Home.
{% endhint %}

{% hint style="warning" %}
If a user has **existing** [**scheduled**](/nightowl/reference/scheduled-messages.md) or [**recurring messages**](/nightowl/reference/recurring-messages.md) when the relevant feature is disabled, those messages will remain in flight.

The user will need temporary access to the relevant feature to delete the messages.
{% 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/nightowl/reference/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.
