Users
Have you ever wondered how to manage users that have access to your Appmixer instance? We'll gladly answer your question today.
All users that have access to your Appmixer instance, and thus, can create and manage flows, access all other parts of Appmixer like Insights, Data storage or Connected accounts are managed in the "Users" tab in the Backoffice.
You may note that you have your own user management system inside your own platform. Appmixer, in fact, automatically creates so-called shadow accounts for your end-users who may be otherwise managed in your own user management system. In other words, these two systems can seamlessly work together without one (negatively) influencing the other.
Having said that, our customers use the Appmixer user management system mainly to control who of their workmates has access to the Appmixer instance, and with which rights.
By clicking on the "pen" icon on the right side, a modal shows up giving you the ability to edit the user right.
The "Private" scope will be deactivated in the upcoming weeks.
As you can see, there are multiple scopes that determine the user rights:
User can access the majority of what the Appmixer instance offers, except Backoffice.
Admin can access all parts of Appmixer including the Backoffice.
Notice that besides the user scopes, you can assign "Vendors" to the user. Vendors allow you to control who can install new components into your Appmixer instance – components used in your flows that, as you know, can be fully customised to fit your business needs.
Vendors are represented by the first string of the custom component name. E.g. the default Send Email component available in Appmixer bears the name "appmixer.google.gmail.SendEmail". The Vendor, being the first string, is "appmixer" in this case.
Now imagine you wanted to build custom components representing some triggers and actions in your custom CRM to further use it in your flows. You'd create your vendor names for example "acme" and would have the option to assign this vendor to a user.
Once you do that, the user will have the ability to install custom components under this particular vendor. E.g. he or she would be able to install components using names like acme.customCRM.
Notice that if you're on our free trial, you're automatically assigned the "appmixer" vendor in the Backoffice. Thanks to that, you can start using the default components straight away as well as install your own without any complex configuration.
Let's look at "ACL" or "Access Control List" available in the Backoffice.
Last updated
