# Roles and Attribution

After the creation of a Task, task parameters can be set with a simple `task set key=value` command.
Some of key=value pairs come pre-configured, but can still be edited in task by end CLI user.

## Attribution
Depending on the AIKP used, this key comes either with NO value by default (for user-defined input data like DEMs or TIFFs) or, for AIKPs that use specific satellite acquisitions, it will preconfigure default attribution based on source of satellite imagery, e.g. Sentinel, WorldView-3, TSX, etc.
At any point during AIKP workflow (but before recipe creation), end CLI user can manually override this automatic assignment of attribution (or add attribution if there is no automatic assignment) with a simple
``` bash
task set attribution="users choice of text"
```
This task parametar will be a part of the created geoJSON metadata and proper attirubution for the dataset will be visible in the bottom right of the UI screen when the dataset is added to the Map View.

## Roles
By default, to each task, assigned roles are [`"public_read", "draft_read"]`, which allow everyone with access to the WebUI to see the published output of that Task.
However, it is possible to create specific groups of users and set the roles key in task parameters to that group in order to limit the visibility of the published output only to that group.
This can be done on a task level with 
```bash
task set roles="user_group_of_choice"
```
and on environment level inside of `default.yaml` in upload configuration section.

Example:
```yaml
default_upload:
  # visibility of published documents in UI per role group
  task_defaults:
    roles: ["/public_read", "/consortium_read"]
```

Setting up of new user groups and assigining roles to those groups is now managed by OPT/NET, so contact for more informations.