Visibilities & authorizations of meetings & protocols
- Adjusting the visibility
- Visibility adjustments when transferring tasks & topics
- Visibilities & authorizations in details
Customize visibility
When a meeting is created, it is visible to Basic teams of participants (organizers / participants / distributors) by default. The visibility can be adjusted both during creation and after creation via the shield icon By authorized users. The visibility can only be restricted to the extent that the meeting is / remains visible to all participants.

If a participant with restricted visibility is added to a meeting after it has been created, a corresponding message appears to add the Basic team of the participant to the visibility. In this case, you can either accept the automatically adjusted visibility or select a different team so that the meeting is visible to all participants.

Visibility adjustments when transferring tasks & topics
The visibility of all elements integrated in the protocol is extended to the teams of all participants as soon as the element is transferred to the interactive protocol. A corresponding message appears so that, in case of doubt, you can check whether the visibility extension makes sense. Alternatively, a new element can be created and integrated into the protocol.

If additional participants are subsequently added as meeting participants, the visibility of the elements is not automatically extended to the teams of these people. To make all elements visible for these teams, the visibility in the element can be extended to the corresponding teams. For details, see Visibilities & authorizations of tasks & topics.
Visibilities & authorizations in details
Meetings
| Project administrator | Project coordinator | Creator | Organizer | Participant | Remaining users |
|---|---|---|---|---|---|---|
| | – | – | – | | |
|
|
|
|
|
| |
Show in list | | | | | | |
Show title, type, location & date | | | | | | |
Edit title, type, location & date | |
| | |
|
|
Show participants | | | | | | |
Edit involved | |
| | |
|
|
Show options | |
| | |
|
|
Edit options | |
| | |
|
|
Show protocol (*) | | | | | | |
Edit protocol (*) |
|
|
|
|
|
|
Entries first. / add / remove | |
| | | |
|
Edit entries (**) | |
| | | |
|
Create comments | |
| | | |
|
Delete comments (***) | |
| | | |
|
Create design comments | |
| | | |
|
Edit draft comments | |
| | | |
|
Delete draft comments | |
| | | |
|
Set scheduling | |
| | |
|
|
Inform participants | |
| | |
|
|
Give in approval | |
| | |
|
|
Show approval | | | | | | |
Grant approval | |
| | | |
|
Rework protocol | |
| | |
|
|
Show visibility | | | | | | |
Edit visibility | |
| | |
|
|
|
| | |
|
| |
Delete | |
| | |
|
|
(*) Tasks & topics in the protocol are only displayed to a user if they are visible to that user. For details see Visibilities & authorizations.
(**) Tasks & topics in the protocol may only be edited by a user to a limited extent. For details see Visibilities & authorizations.
(***) Comments can only be deleted if they had no recipients and there are no new comments from other users.
Meetings, visibility, meeting log, team visibility, meeting participants, meeting content, organizer, access, authorization, rights
Updated on: 29/05/2026
