Similarly to this request, I would like to get the information on all
available workspaces. An example output could look like
this:{"total":10,"workspaces": [{"name": "Example Workspace
1","workspace_id": "12345","date_created": "01.01.1970","activities":
{"active": "25","deactivated": "10","synchronizing": "10"},"modifiedAt":
"02.02.1970"} This way the Target API can be utilized to the maximum if
specific workspaces have to be used in the API calls. Otherwise, it is
really cumbersome to get the...
You mean completely block API requests? Our use case is restricted API
access for normal users (e.g. for reporting purposes on specifically
chosen variables). But it would also be a great idea if specific API
commands could be allowed/blocked for specific users or user groups.
This way the admins could choose to block the get user API command.
Wouldn't it be easier then to change the permissions for normal users so
that they can only see First and Last Name (both in UI and API)? Also, I
haven't seen any E-Mail information in the UI when sharing segments,
workspaces, metrics, etc. I can add someone by specifically writing out
that person's address but usually I only see First and Last Name in the
sharing menu.
I noticed a major privacy problem with API 2.0 while testing out the
possibilities of restricted permissions for normal users:Using the
command https://analytics.adobe.io/api/[mycompany]/users?limit=[XX] a
normal user can get a list of all users in a given organization. This
may pose a privacy issue as a normal user should not be able to see the
usernames, admin status, email, first & last name, phone number, and
title. Those are highly personalized information on any given user.
Usually, I woul...
