# Activation level

General errand creation is **configuration-driven** rather than activation-level–driven. The same integration can create errands for different objects (e.g. [objects.apartment](/apis/objects), [accounting.invoice](/apis/accounting)) depending on the customer's [errands.generalerrandtype](/apis/errands) and [errands.generalerrandsubtype](/apis/errands) setup.


Your integration's activation level determines which organizations or real estates you can access; within that scope, you use the API to read available types/sub-types and create errands according to the configuration.

Choose one of the following activation levels for the general errand creation case.

## 1. Per organization

Activation level: [sales.organization](/apis/sales)

- One credential per typical customer (one organization).
- Within that scope, read [errands.generalerrandtype](/apis/errands) and [errands.generalerrandsubtype](/apis/errands) and create errands according to the configuration.


## 2. Per real estate

Activation level: [objects.realestate](/apis/objects)

- Separate credentials per real estate.
- Each activation has access only to objects under that real estate. Within that scope, read [errands.generalerrandtype](/apis/errands) and [errands.generalerrandsubtype](/apis/errands) and create errands according to the configuration.