Permissions for Talk Templates

1 Initial Problem

Currently, in the Talk Template Administration, administrators can access all templates, and everyone else can't access any templates. Similarly, if a user is allowed to create Talks, they are always offered all templates to do so. It would be useful to be able to control more granually who can access which Talk Template.

2 Conceptual Summary

Talk Templates get a Permissions tab with the Permissions

• View
• Read 
• Edit Settings (includes deriving Talks form this template) 
• Delete 
• Change Permissions 

As default, the global roles Anonymous, Guest, as well as all role templates do not have any of these permissions. The global role Administrator has all permissions, and User only has 'Edit Settings', such that they can create Talks from Templates.

3 User Interface Modifications

3.1 List of Affected Views

• Administration > Organisation > Talk Tamplates > Title > Permission (new Tab) 

3.2 User Interface Details

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

No accessibility implications.

4 Technical Information

No foreseeable technical issues.

5 Privacy

No privacy implications.

6 Security

No security implications.

7 Contact

• Author of the Request: Mix, Eva [emix]
• Maintainer: Schmitz, Tim [tschmitz]
• Implementation of the feature is done by:  Schmitz, Tim [tschmitz]

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

Kunkel, Matthias [mkunkel], 15 JUN 2023: What would be the default permission settings for the several role templates and the global roles? Please give a short overview. Or do all permission have to be set manually for every talk template object?

Kunkel, Matthias [mkunkel], 26 JUN 2023 : We highly appreciate this suggestion and schedule the feature for ILIAS 9. Please describe the default permission settings for the several role templates and the global roles as requested by Matthias.

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

no change required

Approval

Approved at {date} by {user}.