Updates to Klipfolio user permissions

On July 30th, 2015 Klipfolio will be updating user permissions to support a new feature that will allow you to publish private links to dashboards that can be easily shared with anyone in your enterprise. The following table outlines the changes to permissions associated with this new feature. This article also provides information on the impact of these changes and provides instructions on how to update custom roles and API scripts.

New permission tab.publish: New permission that provides the ability to publish dashboards. By default, this permission is granted to the Admin role. This permission can also be granted to custom roles.
Update to existing permission account.eventlog is being replaced by account.usage. This new permission consolidates access to Event Logs, Refresh History and Published Dashboards. By default, this permission is granted to Admins.
Changes to Account management The Event Log dashboard in your Account is replaced by a new dashboard called Usage which will contain Event Logs, Refresh History and a new section for Published dashboards.

New usage dashboard:

Impact on custom roles

If you have custom roles defined for your account or Client accounts that use the account.eventlog permission, they will have the account.usage permission. As a result, these roles will be able to view Data Refresh activity.

What you need to do

    1. If you have Custom Roles, determine if a change is needed to grant access to publishing dashboards and/or to view usage. The screenshot below shows permissions granted for dashboards.

    1. If you have a custom role that was granted the account.settings permission, but not the account.eventlog permission, that role will no longer be able to see data refresh history information.

What you need to do

You may want to add the new account.usage permission to a custom role if they need access to refresh history.

Impact on Klipfolio API scripts

API scripts referencing the account.eventlog permission (for example, to assign that permission to a custom role) need to be updated to refer to the new account.usage permission.

What you need to do

Update API scripts to point to the account.usage permission instead of the account.eventlog permisson.

Old:

curl -u my@email.com:mypassword https://app.klipfolio.com/api/1.0/roles -X POST -d "{'name': 'My New Role', 'description': 'This is a new role', 'permissions': ['klip.build', 'klip.edit', 'account.eventlog']}" -H "Content-Type: application/json"

New:

 

This example uses Basic Authentication to enable secure authentication.

curl -u my@email.com:mypassword https://app.klipfolio.com/api/1.0/roles -X POST -d "{'name': 'My New Role', 'description': 'This is a new role', 'permissions': ['klip.build', 'klip.edit', 'account.usage']}" -H "Content-Type: application/json"

 

This example uses an API Key to enable secure authentication.

curl -u my@email.com:mypassword https://app.klipfolio.com/api/1.0/roles -X POST -d "{'name': 'My New Role', 'description': 'This is a new role', 'permissions': ['klip.build', 'klip.edit', 'account.usage']}" -H "Content-Type: application/json"