1.6 User Administration in Admin Interface

[rossjones]

[Optional] As an Instance Admin I want to add (invite), edit, and remove users so 
that they have access (or do not have access) to the platform

[Required] As an Instance Admin I want to make a user a sysadmin in the user interface 
so that  they have full access (and I don’t to have direct access to the machine
 to do this ...)

[rossjones]

At the moment the onus is on the user to manually register on the site, and the granting of sysadmin privileges is done on the command line by an administrator.

I'd suggest both of these should be required. Users who manage organizations can invite users by email, but a more thorough implementation that gave more control in an admin section would be a much better (for instance owners and sysadmins alike).

[jqnatividad]

In relation to #12, ODI may want to consider adding some user metrics not only to the Admin page, but the user page in general.

Currently, the user dashboard has the News Feed, My Datasets, My Organizations and My Groups. Perhaps, there could also be My Stats?

This is not only useful feedback and tracking information for the CKAN operator in terms of enforcing SLA commitments and utilization, it can also be used to dynamically generate interesting utilization metadata that can be displayed on the UI.

Already, CKAN has page view tracking functionality that can be extended to support this functionality.

Would be nice too if there's a way to differentiate admins, bots and users.

[wardi]

CKAN currently lets you invite users to organizations but not invite regular users. I agree we should fix this, as suggested: ckan/ideas#85

Promoting a user to sysadmin would also be nice to have, as mentioned in ckan/ideas#47 . We're not planning on including that in the first ckan-multisite release. It would be a core ckan feature or extension regardless