

team field, and the /api/v3/teams and /api/v3/team endpoints no longer exist.
Every user has a set of site-wide capabilities, plus any number of grants on individual objects.
admin: true) can do everything.manageDatasets: true) hold the editor role on every dataset on the site, so they can read, create, edit and delete any dataset.ab12x.
canCreateDatasets, which lets its members create new datasets. A member who creates a dataset is automatically granted the editor role on it.| Role | Can do |
|---|---|
reader | View the dataset, even if it is private or archived. |
uploader | Also add, replace and remove files and links, and set nextReviewDate. Other metadata is locked. |
editor | Edit all metadata, manage files, and delete the dataset. |
Public datasets are readable by everyone, so reader grants only matter for private and archived datasets.
The whoami endpoint returns your capabilities, your groups, and every grant that applies to you.
{
"id": 382,
"admin": false,
"manageDatasets": false,
"groups": {
"59m9r": {
"id": "59m9r",
"title": "Health Intelligence",
"canCreateDatasets": true,
"permit": {
"dataset": { "20abc": { "id": "20abc", "role": "editor" } },
"webpage": {},
"blogpost": {}
}
}
},
"permit": {
"dataset": { "444xy": { "id": "444xy", "role": "uploader" } },
"webpage": {},
"blogpost": {}
}
// [...]
}
Groups and permissions are managed by site administrators and dataset managers through the web interface. There is currently no public API for creating groups or granting permissions.
If you were previously using the teams API to automate this, please contact support.