cancel
Showing results for 
Search instead for 
Did you mean: 

Restricting user to modify/delete only its own objects

SOLVED
Occasional Contributor

Restricting user to modify/delete only its own objects

Hello, 

 

We wanted to know what would be the best approach to allow a new user, starting with Mega, to be able to read and create objects (Functional activities, applications, diagrams, ect), but only be able to modify and delete objects created by him/her in a single Environment and single Repository ? (typical case: Trainee, allow him/her to try out the tool but no permanent damage)

 

I have tried several approaches by customizing a Data Writin AccessAccess and Meta Model Access under UI access (CRUD permissions) but cannot achieve what was mentionned above. (Eg: Can create but cannot modify what he/she has just created)

 

Many Thanks !

 

1 REPLY
Highlighted
MEGA

Re: Restricting user to modify/delete only its own objects

Hello

 

I assume you have implemented management of writing access area.
With this feature, a permission level (writing access area) is mapped to a group of users (not personal) in a static way (stamp on object).

You could of course create one writing access area per user but this it not the idea of the feature.

 

You can consider to implement data access rules to code dynamically permissions according to various criteria including creator, owner.
Note that is more complex and can slow down performances.

Jerome