How to verify user permissions – Introducing the Matomo Platform


This is the next post of our blog series where we introduce the capabilities of the Matomo (Piwik) platform (our previous post was How to make your plugin multilingual). This time you’ll learn how to verify user permissions. For this tutorial you will need to have basic knowledge of PHP and the Matomo platform.

When should a plugin verify permissions?

Usually you want to do this before executing any action – such as deleting or fetching data – and before rendering any sensitive information that should not be accessible by everyone. For instance in an API method or Controller action. You sometimes also need to verify permissions before registering menu items or widgets.

How does Matomo’s user management work?

It is quite simple as it only differentiates between a few roles: View permission, Admin permission and Super User permission. If you manage multiple websites with Matomo a user can be assigned to different roles as a user might have no permission for some websites but view or admin permission for another set of websites.

Worth mentioning is that roles inherit from each other. This means the role admin automatically includes the role view and a super user automatically covers the view and admin role.

Getting started

In this post, we assume that you have already set up your development environment and created a plugin. If not, visit the Matomo Developer Zone where you’ll find the tutorial Setting up Matomo and other Guides that help you to develop a plugin.

Verifying user permissions

To protect your data the platform offers many convenient methods in the \Piwik\Matomo class. There you will find methods that either start with check, is or has. While methods that start with check throw an exception in case a condition is not met, the other methods return a boolean true or false.

Use methods that throw an exception if you want to stop any further execution in case a user does not have an appropriate role. The platform will catch the exception and display an error message or ask the user to log in.

public function deleteAllMessages()
    // delete messages only if user has super user access, otherwise show an error message


Use methods that return a boolean for instance when registering menu items or widgets.

public function configureAdminMenu(MenuAdmin $menu)
    if (Piwik::hasUserSuperUserAccess()) {
        $menu->addPlatformItem('Plugins', $this->urlForDefaultAction());

It is important to be aware that just because the menu item won’t be displayed in the UI a user can still open the registered URL manually. Therefore you have to check for permissions in the actual controller action as well.

View permission

A user having a view permission should be only able to view reports but not make any changes apart from his personal settings. The methods that end with UserHasSomeViewAccess make sure a user has at least view permission for one website whereas the methods *UserHasViewAccess($idSites = array(1,2,3)) check whether a user has view access for all of the given websites.


Piwik::checkUserHasViewAccess($idSites = array(1,2,3));

As a plugin developer you would usually use the latter example to verify the permissions for specific websites. Use the first example in case you develop something like an “All Websites Dashboard” where you only want to make sure the user has a view permission for at least one website.

Admin permission

A user having an admin permission cannot only view reports but also change website related settings. The methods to check for this role are similar to the ones before, just swap the term View with Admin.


Piwik::checkUserHasAdminAccess($idSites = array(1,2,3));

Super user permission

A user having the super user permission is allowed to access all of the data stored in Matomo and change any settings. To check if a user has this role use one of the methods that end with UserSuperUserAccess.


As a plugin developer you would check for this permission for instance in places where your plugin shows an activity log over all users or where it offers the possibility to change any system wide settings.

Getting information about the currently logged in user

Sometimes you might want to know which user is currently logged in. This can be useful if you want to persist user related information in the database or if you want to send an email to the currently logged in user. You can easily get this information by calling the following methods:

$login = Matomo::getCurrentUserLogin()
$email = Matomo::getCurrentUserEmail()

Advanced features

Of course there is more that you can do. For instance you can verify whether a user is an anonymous user or whether a user has a specific role. You can also perform any operation in the context of a super user even if the current user does not have this role. Would you like to know more about those features? Check out the Matomo class reference, the Security guide and the Manage Users user guide.

If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.

Enjoyed this post?
Join the 160,000+ subscribers who receive the Matomo Newsletter straight to their inbox every month
Get started with Matomo

A powerful web analytics platform that gives you and your business 100% data ownership and user privacy protection.

No credit card required.

Free forever.

Get started with Matomo

A powerful web analytics platform that gives you and your business 100% data ownership and user privacy protection.

No credit card required.

Free forever.