Scenario 2 - Understanding rights at design time and runtime
This scenario illustrates the rights different people need in order to view, use, modify, and delete a form and the views on that form, both at runtime and design-time. Remember that you need rights on the parent category if you want to view the objects in the category tree. For this scenario, parent category rights and inheritance are not shown.
Mike created a form with two views. Eric must run the form but also needs to change one of the views on the form (he needs design time rights). Jill only needs to run the form.
The following roles and rights are required:
| User | Rights | Permissions | Runtime | Design time |
|---|---|---|---|---|
| Mike |
View rights on Form |
Allow Allow Allow |
Can see the form | Can see, change, use, and delete the form |
| View rights on View 1 Modify rights on View 1 Delete rights on View 1 |
Allow Allow Allow |
Can see the view | Can see, change, use, and delete the view | |
| View rights on View 2 Modify rights on View 2 Delete rights on View 2 |
Allow Allow Allow |
Can see the view | Can see, change, use, and delete the view | |
| Eric |
View rights on Form Modify rights on Form Execute rights on Form |
Allow Deny Allow |
Can see the form | Can see and use the form but cannot change, rename, or move the form |
|
View rights on View 1 |
Allow Allow |
Can see the view |
Can see, change, and use the view |
|
| View rights on View 2 Modify rights on View 2 |
Deny Deny |
Can see the view |
Cannot see and use the view | |
| Jill | Execute rights on Form | Allow | Can see the form and views | Cannot see or use the forms or views |