Here's a quick reference to help Magento administrators when they're configuring what admin screens should be enabled for various business roles. For the most part, the permission (aka "Resource") required for access to each screen corresponds to the path of the admin screen. But this isn't always the case. There are a number of screens that have been moved around, such as "Customers > Customer Groups" so the name of the permission no longer matches the location of the backend screen. Also, a number of permissions are used for multiple screens. For example, the "Catalog" permission is used for "Catalog" and "Catalog > Inventory".
I've been working with the Magento 2 REST API off and on over the past two years now. One of the hassles with the API is just figuring out what permissions are required to access a particular API endpoint. When setting up access for API users, I have seen some Magento 2 administrators just take the...
Presention by Joshua Warren & David Deppner
Meet Magento New York 2016
Presented by David Deppner
MagentoLive UK, London, June 20, 2016
This presentation offers a business perspective on managing your Magento 2 upgrade project, and when to get started (spoiler alert: start now!). I speak from a merchant point of view to illustrate why you may want to move to Magento...
I recently got started with some work integrating some older systems with Magento 2 using their new REST API. Right at the top of the Getting Started with Magento 2 APIs Introduction there's a list of features, including this one:
The framework supports field filtering of web api responses to conserve mobile bandwidth.
That sounds nice. Let's get some of those responses down to just the fields we need, and speed up the data transfer just a bit!