Claap uses role-based access control to manage what a user can see or do in the product. Roles are defined on the level of
topic , and
Visitorsare one-time & unregistered collaborators who can access the content of a claap or a topic but cannot share it with other users and use certain features. Visitors can only access public resources. Visitors are not named nor visible on the claaps and topics.
Guestsare external and occasional collaborators who can collaborate on shared claaps and topics, when invited by email. They have access to the content of the claap or topic, and can use collaborative features. Guests can access particular resources but they are not members of your workspace. Guests are named and visible on the claaps and topics as they are always registered.
Membersare frequent and registered collaborators, who have access to all features in your plan, and can both create and edit claaps & topics in the workspace. Members are named and visible on the claaps and topics as they are registered. They can access all team-shared topics.
Roles on claaps can be received directly by invitation or indirectly through the parent topic. To configure your claap access level, click on the claap’s
Claap supports 2 roles:
Full accessallows users to collaborate in the claap, edit and delete it, and share it with other users.
Can commentallows users to view the claap and leave comments visible to other users on the claap.
💡 Any visitor accessing a public claap can leave a comment and automatically become a guest. Claap doesn’t currently support the
View only mode.
Share claap popin
Roles on topics can be received directly by invitation or indirectly through the team-shared topic. To configure your topic access level, click on the topic’s