Versions Compared

Old Version 3

changes.mady.by.user Blagica

Saved on

compared with

New Version Current

changes.mady.by.user Blagica

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Read

Write

Execute

Business Models and Monitors (i.e. storedModelsStoredModels)

  • Visualize

  • Edit [ Put / Patch ]

  • Create snapshots*

Snapshots (i.e. deployableModelsDeployableModels)

  • Visualize

  • Edit [ Put / Patch ]

  • Adding Add Monitors

  • Execute monitors.

  • Deploy [POST DeployedModels]

  • Create jobs (scoring or metric) and re-run jobs

Deployed Models

  • Visualize

  • Edit [ Put / Patch ]

  • Un-Deploy

N/A

Model Test Results

  • Visualize

  • Edit [ Put / Patch ]

N/A

ModelMLCModel MLCs

  • Visualize

  • Edit [ Put / Patch ]

N/A

Jobs

  • Visualize

  • Edit [ Put / Patch ]

  • Re-run jobs

N/A

Runtimes

  • Visualize

  • Edit [ Put / Patch ]

  • Deploy to the runtime

  • Schedule jobs on the runtime

  • Reset engine

Notifications

  • Visualize

N		/A

  • Edit [ Put / Patch ]

  • Create [ Post ]**

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 entity, 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

...

User

READ Model A

READ Model B

READ Model C

Rules description

Alice

✅

❌

❌

  • Alice belongs to GroupA.

  • Alice is only able to see StoredModels from the only group she belongs to.

  • Model A is the only StoredModel associated to GroupA.

Result:

  • Alice only see Model A after logging in to ModelOp Center.

Bob

✅ (Granted by RWX - row 1)

✅

❌

  • Bob belongs to GroupB.

  • Model A is the only StoredModel associated to GroupA.

  • Model B is the only StoredModel associated to GroupB.

  • Bob is able to see StoredModels from the group he belongs to (GroupB) and also due to the RWX READ permission from RWX Table as the owned by granted to Group B, Bob is able to see StoredModels from Group A as well.

Result:

  • Bob is able to see Model A and Model B after logging-in into ModelOp Center.

Charley

❌

✅ (Granted by RWX - row 2)

✅

  • Charley belongs to GroupC.

  • Model B is the only StoredModel associated to GroupB.

  • Model C is the only StoredModel associated to GroupC.

  • Charley is able to see StoredModels from the group he belongs to (GroupC) and also due to the RWX READ permission from RWX Table as the owned by granted to Group C, Charley is able to see StoredModels from Group B as well.

Result:

  • Charley is able to see Model B and Model C after logging-in into ModelOp Center.

...