En our review to the configuration menu mautic, the open source marketing task automation tool, It is time to create users, assign roles and trigger events through webhooks
Users, roles and events in Mautic
Users are assigned to people so they can access Mautic while roles determine which Mautic functions users can access.
User management is the responsibility of the administrator user.
The administrator can create a user by completing all the required fields, adding a signature if necessary, and assigning a username and password.
Some optional configuration parameters are the time zone and the default language for the new user. Each created user has two states; published (able to connect) or unpublished (unable to connect)
To create a new role we go to the corresponding item in the configuration menu. Then we click on New.
If the 'Full System Access' switch is activated, an administrator account is created that has the highest level of access to all Mautic options.
These accounts must be limited and be assigned to trusted users. You cannot configure permissions because you already have them fully assigned.
The alternative is assigning custom permissions for certain features. This is done by holding the switch for full access to the system and going to the Permissions tab to build the role.
The permission options are as follows:
- View: allows users with this role to see a part of Mautic.
- Edit: User can make changes to a part of Mautic.
- Create: Allows users to create new resources in a specific section of Mautic.
- Delete: The user with this assigned role can delete resources from a Mautic section.
- Publish: Gives the possibility to make the resources available.
- Full: Assign users all the previous permissions.
There are permission levels relative to the resources that the user has created by himself and also related to those created by others:
- Own: this allows users with this role to view / edit / delete / publish their own resources in this part of Mautic, but not those created by others
- Others: In addition to their own resources, the user can edit those created by others.
There are permission levels related to the ability to manage resources:
- Manage: allows users with this role to manage the resources in this area of Mautic (for example, manage custom fields or plugins)
EThere are permission levels related to the fields that can be edited in the Users section:
- Specified fields: allow or deny users with this role to edit the fields specified in the Users section (for example, Name, Username, Email, Title)
- All - This allows users with this role to edit all fields related to the Users section
A webhook is an HTTP callback that allows you to send data from one application to another. In programming, a callback is called to a function "A" that is used as an argument to another function "B". When "B" is called, it executes "A".
mautic establishes a series of activities that we can do through webhook related to the creation, modification and elimination of events.
The procedure to create a webhook is as follows:
- In the configuration menu, click on Webhooks.
- Click on New
- In the form we fill in the name and a brief description of the webhook.
- We paste the POST URL of the application in the corresponding field.
- We select the event that will be fired through the webhook.
- Click on Send Test Payload to test that everything works fine.
- Next, we assign it a category and determine, if more than one event has been selected, in what order they will be executed.
- To finish, click on Apply and Save & Close.
All this may sound a bit dense and incomprehensible, but, when we look at the practical examples, we will see the versatility of this tool,
Be the first to comment