You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* allow bulk watchlists CSVs to have extra headers
* CHANGELOG and documentation note for watchlist + update-risk-profile
* clean up doc note
* clean up doc note
If both username and user_id are provided in the CSV row, the user_id value will take precedence. If watchlist_type and watchlist_id columns
58
58
are both provided, the watchlist_id will take precedence.
59
59
60
-
## Add Watchlist-related metadata to User's Profile
60
+
```{eval-rst}
61
+
.. note::
61
62
62
-
Some Watchlists store related metadata to the watchlist member on the User Risk Profile. For example, when adding a user
63
-
to the Departing Watchlist in the Code42 admin console, you can specify a "departure date" for the user. These values
64
-
can be set/updated from the CLI under the [Users command group](./users.md#manage-user-risk-profile-info)
63
+
For watchlists that track additional metadata for a user (e.g. the "departure date" for a user on the Departing watchlist), that data
64
+
can be added/updated via the `code42 users bulk update-risk-profile <../commands/users.html#users-bulk-update-risk-profile>`_ command.
65
+
66
+
You can re-use the same CSV file for both commands, just add the required risk profile columns to the CSV.
67
+
68
+
For example, to bulk add users to multiple watchlists, with appropriate ``start_date``, ``end_date``, and ``notes`` values, create a CSV (in this example named ``watchlists.csv``) with the following::
0 commit comments