For an introduction, see the "Access management" section under the "Administration Elements" located in the Platform chapter
Using the standard directories makes it easier for Support, partners, and people not involved in the project to maintain the application. Avoid creating custom folder structures for recipients, lists, deliveries, and so on.
For an introduction, see How to setup folders and access rights.
Using the standard directories makes it easier for Support, partners, and people not involved in the project to maintain the application.
Avoid creating custom folder structures for recipients, lists, deliveries etc.
For an introduction, see How to setup folders and access rights.
Using the standard directories makes it easier for Support, partners, and people not involved in the project to maintain the application.
Avoid creating custom folder structures for recipients, lists, deliveries etc.
For an introduction, see How to setup folders and access rights.
Using the standard directories makes it easier for Support, partners, and people not involved in the project to maintain the application.
Avoid creating custom folder structures for recipients, lists, deliveries etc.
Nota:
Use the standard folders such as Administration, profiles & Targets, Campaign management
Place technical workflows under the standard directory: Administration / Production / Technical Workflows.Create subdirectories per workflow type.
Nota:
Organize the technical workflows by frequency.
For example: aggregates, imports, exports. Name the workflows in alphabetical order, so that they appear sorted in the order of execution.
For example:
A1 – import recipients, starts at 10:00;
A2 – import tickets, starts at 11:00.
Nota:
Create templates for users to start with
I post su Twitter™ e Facebook non sono coperti dai termini di Creative Commons.