General errand creation is configuration-driven rather than activation-level–driven. The same integration can create errands for different objects (e.g. objects.apartment, accounting.invoice) depending on the customer's errands.generalerrandtype and errands.generalerrandsubtype 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.
Activation level: sales.organization
- One credential per typical customer (one organization).
- Within that scope, read errands.generalerrandtype and errands.generalerrandsubtype and create errands according to the configuration.
Activation level: objects.realestate
- Separate credentials per real estate.
- Each activation has access only to objects under that real estate. Within that scope, read errands.generalerrandtype and errands.generalerrandsubtype and create errands according to the configuration.