Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

call member role doesn't restrict access #801

Merged
merged 1 commit into from
Oct 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ You can provide a list of call members, this can be done when you create a call
There are two reasons to use call members:

- Call membership allows you to have more flexibility when it comes to permissions. The permission system allows you to grant different permissions to users and members, this way one user can be a member on one call or a member on another.
Membership also allows you to specify a role for user in a call. You can more information about the roles and permissions [here](/api/call_types/permissions/).
Membership also allows you to grant additional roles to users in a call. It's important to note that this doesn't restrict access, but rather expands capabilities.
You can more information about the roles and permissions [here](/api/call_types/permissions/).
- Call members will receive [push notifications](/api/call_types/settings/#push-notifications-settings).

<Tabs groupId="examples">
Expand Down
Loading