# Access

Refer to the API Reference for full attribute and endpoint details.

## Reading settings and configuration

| Entity | Access | Purpose |
|  --- | --- | --- |
| [errands.generalerrandtype](/apis/errands) | read | Allowed/required fields, delegation, notifications, allowed connection types. |
| [errands.generalerrandsubtype](/apis/errands) | read | Can override rules from the type. |
| [errands.customerrandfieldtype](/apis/errands) | read | Customer-defined fields for errand submission. |
| [errands.customerrandfieldinclusion](/apis/errands) | read | Which custom fields apply to a given general errand type. |


## Constructing the errand

| Entity | Access | Purpose |
|  --- | --- | --- |
| [errands.generalerrand](/apis/errands) | read + create | Main errand (title, description, link to object such as [objects.apartment](/apis/objects)). |
| [errands.generalerrandfile](/apis/errands) | all | Files attached to the errand (e.g. photos of a fault). |
| [errands.customerrandfieldvalue](/apis/errands) | all | Values for the custom-fields configured on the errand-type/errand-sub-type. |


You will also need read access to the entity types that errands can be connected to (e.g. [objects.apartment](/apis/objects), [accounting.invoice](/apis/accounting))