A common request for Aptuitiv Studio has been to integrate user permissions. We had those capabilities in version 2 and have recently completed it for version 3. If you're on the Plus or higher version of Aptuitiv Studio then you now have user permissions.
You can now set an administrative user to have limited access to the administration. You can set which apps they can work in and for some of the apps you can even set which actions they can perform. Those actions are usually things like add, edit or delete. Some of the apps, such as Pages, allow you to have more control beyond those basic actions on what the user can do. Even if you give a user access to a certain app you don't have to give them access to the entire app. For example, you can give a user access to the Blog app but limit them to only being able to work with Posts. They won't see the other parts of the Blog app (Categories, Layouts, Settings and Attributes) or have access to those areas.
When you add a user it is now a 2 step process. Step 1 is to enter the general user information. Step 2 is to simply state whether or not a user has full access to the administration. If you are limiting the user you would select "No" at this step. Once you save the user you will be taken to the user details view where you can set the actual permissions.
Adding a user - step 1
Adding a user - step 2
Instead of editing a user directly you will be taken to a user details view first. From there you can edit the user details, edit the user permissions and view login statistics for the user.
User details view
Editing user permissions
The Pages app is a little unique when it comes to user permissions. There are a lot of different things that you can do when editing a page so we've taken the permissions beyond just limiting what a user can do in the Pages app. You can also limit the information that a user can edit on a page.
For example, you can set a user so that they can't change the page address but can change everything else. Or you could set that they can only edit the content for the page and not everything else (page title, name, address, meta data, published status, search settings, etc.) This really comes in handy when you want to allow a user to work with page content but not change some of the advanced properties for a page.
Right now the user permissions don't take into consideration multiple instances for an app. This means that if you have multiple Blog instances and you give a user access to the Blog they will have access to all instances of the Blog app. We are planning on rolling out a new version of user permissions that work with multiple instances of an app in the near future.
Leave the first comment