@mattab opened this Issue on October 5th 2015 Member

At Piwik our mission is to help individuals and organisations keep full control of their data. Piwik is becoming more and more popular with medium businesses, big companies, corporations, governments.

In this issue, we would like to gather all the requirements to meet so that Piwik can become the best Enterprise Analytics platform.

Please leave a comment with your suggestion or ideally: a link to an existing github issue.

@mattab commented on October 5th 2015 Member

Piwik is an Enterprise platform and already used in many very large companies and governments. We've already made amazing progress in the last two years...

Our work is not finished though and there are still important features to build to make Piwik awesome for Enterprise users:

  • [x] Introducing Long Term Support #8546 (decided at our 2015 community meetup)
  • [x] Implement "Content Security Policy" (CSP) #1542
  • [ ] Show all personal email reports, custom alerts of all sites, not only current selected site #7076
  • [x] Super Users should be able to list all segments #6766
  • [ ] Admin role should be able to create segments visible to all users with access to this site #6844
  • [x] Improve User Management and assigning permissions to users #6187
  • [ ] Customizable columns in All Websites Dashboard #5150
@tsteur commented on October 6th 2015 Member
  • User groups / roles / ACL. Let a superuser/admin define what a user is allowed to do in Piwik, move multiple users into one group, assign user permissions like view or admin to a group of websites, ... Management for 1000 users with 1000 different websites should be easy. When there's a new employee it should be easy to give that user the right permissions for the right websites (the websites that department is allowed to see and manage) in seconds with one or two clicks.
  • Pretty much all tracking and archiving related settings from global.ini.php, also some settings in the UI should be customizable for each site and for a group of sites.
  • Various single sign on connectors, eg Jira, Salesforce, I forgot the name of some big, enterprise ones
  • Deployment of Piwik to a multi server architecture should be as easy as possible, ideally "out of the box". This also means using Redis for caches, etc.
  • Sharing dashboards
  • Site and "group of sites" specific Dashboards (eg all sites in group "Marketing" would have the same dashboards)
  • Role specific dashboards (eg a user role SEO would always see the SEO dashboards on all sites )
  • More advanced email reports, at least better, professional looking ones

I'm sure there's much more. Without these I'd not consider it enterprise ready, max small business ready :)

@MagicFab commented on October 6th 2015
@gaumondp commented on October 7th 2015

I don't need it myself and I hate to write it but :

  • Multiple DB support is an important enterprise go/no-go feature for many.
@tsteur commented on October 12th 2015 Member
  • Block users for X minutes or an hour after Y unsuccessful logins,
  • 2FA in core :+1:
  • token_auth should no longer be able to use as login and to authenticate, instead proper API authentication, eg oAuth etc.
  • salted, hashed passwords in DB that do not depend on username + password

In general platform should be more secure if one wants to use it in Enterprise

@tsteur commented on November 23rd 2015 Member

salted, hashed passwords in DB that do not depend on username + password
token_auth should no longer be able to use as login and to authenticate, instead proper API authentication, eg oAuth etc.

Also we should not store token_auth in database and especially not in plain text

@tsteur commented on December 7th 2015 Member
  • Improve Piwik's sharing capabilities: Let a user share reports #9351
  • Improve print version of Piwik #9347
@RMastop commented on January 23rd 2016 Contributor

Send email to notify a new user after creating their account. In this email we can write them about the password reset function, so no credentials need to be send. (or if some other authentication is used let them know about this).

@tsteur commented on January 23rd 2016 Member

:+1: maybe we should create a new issue for this as well in case we don't have one yet as I find it almost mandatory and always wondered why we haven't been sending mails already for new accounts

@RMastop commented on February 9th 2016 Contributor

Fully separate tracking from reporting. For security and performance reasons.

@tsteur commented on February 10th 2016 Member

Fully separate tracking from reporting. For security and performance reasons.

I also want to have this for technical reasons. It will be much easier to maintain and to contribute when having these things separated. Each project will be smaller and more clear. Also they will be usable independently. Meaning someone can use tracking feature, but build different custom reporting.

@hpvd commented on February 10th 2016

most wanted "unvisible technical" feature:
"keep raw data"

to be able to

see also https://github.com/piwik/piwik/issues/8955#issuecomment-178479720

@hpvd commented on February 10th 2016

most wanted "field of features" to be enhanced
"everything with ecommerce" (simply search for it within issues)

reasons:

  • large group of users
  • group of users who has to like piwik "owner ship of data" by default (because of laws in several countries)
  • group of users having money to spent and are willing to do so for good solutions
    (imortant for making piwik future prrof see comments in https://github.com/piwik/piwik/issues/9169)
@tsteur commented on February 14th 2016 Member

Site specific dashboards

Powered by GitHub Issue Mirror