...
| Read | Write | Execute |
---|---|---|---|
Business Models and Monitors (i.e. storedModelsStoredModels) |
|
|
|
Snapshots (i.e. deployableModelsDeployableModels) |
|
|
|
Deployed Models |
|
| N/A |
Model Test Results |
|
| N/A |
ModelMLCModel MLCs |
|
| N/A |
Jobs |
|
| N/A |
Runtimes |
|
|
|
Notifications |
| /A
| N/A |
*If the snapshot is created through the Jupyter plugin, then the user must have write
permissions, in addition to read
and execute
, to the stored model group. When a snapshot is created through the Jupyter plugin, the plugin updates the stored model with platform
info, hence the need for write
permissions.
**Only for Notification objects, when a new Notification is created, it will inherit the same group as the model it was created for. There might be instances when the user will NOT belong to the group assigned to the Notification, but they will have to have write
permissions for the model’s group on the Notification collection.
Please note that for all other objects, the following rule still applies: on newly created entities, users can only assign groups they actually belong to, and not been given permissions to.
Examples
Context tables.
Onboarded Models | Group |
---|---|
Model A | GroupA |
Model B | GroupB |
Model C | GroupC |
...