# Access level

Using AcyMailing Enterprise you can restrict the access of functionalities. (this feature has been implemented since AcyMailing 1.8.0)

Even if you see all kind of groups on this interface, it does not mean all groups are allowed do execute the corresponding action. For example, an action only available via the back-end such as exporting users will only be accessible for users allowed to log-in on your back-end.

If you want to allow a user group to access a Back-end feature, you'll first have to go in the AcyMailing component's options (the "Option" button at the top of the dashboard) then enable the access to the Back-end

![](/files/-MJSQSVQHTqyVA0PDMvG)

Permissions

## Joomla permissions <a href="#joomla-permissions" id="joomla-permissions"></a>

With the "options" button you can access the Joomla ACL manager for the AcyMailing component.

## Advanced access control level <a href="#advanced-access-control-level" id="advanced-access-control-level"></a>

In addition to the Joomla access level management, you can customize almost all the AcyMailing features' access.

### Users <a href="#users" id="users"></a>

![](/files/-MJSQUdcNtthu_8YBELA)

* **View**: Groups allowed to view subscribers (select them when sending a test message for example).
* **Manage**: Groups allowed to access the subscriber listing and create/edit subscribers.
* **Delete**: Groups allowed to delete subscribers.
* **Export**: Groups allowed to export subscribers.
* **Import**: Groups allowed to import subscribers.

### Lists <a href="#lists" id="lists"></a>

* **Manage**: Groups allowed to access the lists management and create/edit lists.
* **Delete**: Groups allowed to delete lists.
* **Filter**: Groups allowed to access the filters/Actions interface.

### Newsletters <a href="#newsletters" id="newsletters"></a>

* **Manage**: Groups allowed to manage Newsletters (view/create/edit)
* **Delete**: Groups allowed to delete Newsletters from the back-end
* **Send**: Groups allowed to send a Newsletter from the back-end and from the front-end (only if they are allowed to manage the corresponding list on the back-end)
* **Schedule**: Groups allowed to schedule or unschedule a Newsletter via the back-end Groups allowed to schedule or unschedule a Newsletter via the front-end (only if they are allowed to manage the corresponding list on the back-end) Groups allowed to schedule a single Newsletter for a single user
* **Spam test**: Groups allowed to access the spam test in the newsletter preview
* **Copy**: Groups allowed to copy a newsletter in the listing
* **Lists**: Groups allowed to choose the lists the newsletter is attached to
* **Attachments**: Groups allowed to attach files to the newsletter
* **Sender information**: Groups allowed to set specific sender information for a newsletter
* **Metadata**: Groups allowed to set the metadata of the newsletter
* **A/B testing** : Groups allowed to perform a spam test
* **Inbox actions** : Groups allowed to set an inbox action

### Smart-Newsletters <a href="#smart-newsletters" id="smart-newsletters"></a>

* **Manage**: Groups allowed to manage Smart-Newsletters (view/create/edit)
* **Delete**: Groups allowed to delete Smart-Newsletters

### Campaign <a href="#campaign" id="campaign"></a>

* **Manage**: Groups allowed to manage campaigns (view/create/edit)
* **Delete**: Groups allowed to delete campaigns
* **View**: Groups allowed to view and insert tags from the front-end or back-end

### Templates <a href="#templates" id="templates"></a>

* **View**: Groups allowed to select a different template than the default one on the front-end or back-end
* **Manage**: Groups allowed to manage templates (create/edit/import)
* **Delete**: Groups allowed to delete templates
* **Copy**: Groups allowed to copy templates

### Queue <a href="#queue" id="queue"></a>

* **Manage**: Groups allowed to access the queue listing
* **Delete**: Groups allowed to mass delete e-mails from the queue (groups allowed to manage the queue will still be able to delete individual e-mails from the queue)
* **Process**: Groups allowed to process the queue

### Statistics <a href="#statistics" id="statistics"></a>

* **Manage**: Groups allowed to access the statistics
* **Delete**: Groups allowed to delete statistics

### Configuration <a href="#configuration" id="configuration"></a>

* **Manage**: Groups allowed to access the AcyMailing configuration page and the custom fields

### Dashboard <a href="#dashboard" id="dashboard"></a>

* **Manage**: Groups allowed to access the Dashboard

## Reset your permissions <a href="#reset-your-permissions" id="reset-your-permissions"></a>

If you migrated your website from J1.5 to J1.6, you will have to execute this query via phpMyAdmin to reset the ACL configuration:

```
DELETE FROM #__acymailing_config WHERE namekey LIKE "acl_%"
```


---

# Agent Instructions: 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:

```
GET https://docs.acymailing.com/old/main-pages/configuration/configuration-tabs/access-level.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.