Topic Permissions

Topic permissions define who can view, comment on, edit, or delete a topic. Proper configuration ensures control, traceability, and structured collaboration.

1.     Default Permissions

New topics are public by default, meaning all project users can view them.

Default rules:

·        Topic Creator - Total (view, edit, delete)

·        Assigned to – Read + Edit

·        Other users – Read (view and comment)

📌 Making a topic private during creation

To create a private topic, click the padlock icon in the creation panel.

This sets permissions to None for all users except:

·        The Topic Creator

·        The Assigned to user.

2.     Customizing Permissions

After creation, permissions can be configured in the topic settings.

Permissions can be assigned for:

·        Individual users

·        Companies

·        Teams

Conflict Rule:

If a user receives permissions from multiple sources, the highest permission level is applied.

3.     Public vs. Private Topics

·        Public Topics

o   Visible to all project users.

o   Access cannot be removed unless the topic is made private

·        Private Topics

·        Only explicitly assigned users, companies, or teams can access the topic

·        Note: If the Design Private Topics level in Project Permissions is set to Read or Total, users with that role will be override permissions set by the creator.

4.     Permission Levels

●       X: Remove users to remove all permissions

●       Read: View and comment only

●       Read + Edit: View and edit, without delete permission

●       Total: Full control (view, edit, delete)

5.     Key Notes

·        The topic creator always has Total permission

·        The Assigned to user always has at least Read + Edit

o   This permission can only be increased, not reduced