Improved access capabilities: separate delete from write/run

Hi ​@Markus Pettersen!

Thank you for suggesting this product idea. This is a very understandable concern. 

In a scenario where you’d be able to: 

• have a dedicated call access capability where meaningful (e.g. functions, transformations, agents, etc.), separating calling/running from creating/updating/deleting (write)
• always scope access to instances, through a concept like data sets or similar, meaning you would be able to scope read/write/call access for a group of users to a specific set of instances

Do you still believe you’d require separate create/update and delete capabilites? 

A dedicated call where applicable would mitigate a lot of our concerns (it should be scoped to dataset/space etc.)

If the write access was scoped and not global then having write and delete coupled would not be as much of a concern. The global scope is a bigger issue. Having them separate would still be nice, but not a necessity.

Thanks ​@Markus Pettersen. We’re working on multiple initiatives that are relevant here. In general, what you’re describing sounds very aligned with what we’re planning. We can provide an update once our plans and timelines are more clear.