mirror of
https://github.com/zulip/zulip.git
synced 2025-11-06 15:03:34 +00:00
2de2b22d55
Instead of referring to users being added or removed from channels, we now use subscribe or unsubscribed from channels. Splits the article for adding and removing users from a channel into separate articles: /help/subscribe-users-to-a-channel and /help/unsubscribe-users-from-a-channel. The URL redirects for the combined add/remove articles (for both channel and stream terminology) go to the subscribe users to a channel article.
124 lines
3.9 KiB
Markdown
124 lines
3.9 KiB
Markdown
# Guest users
|
|
|
|
You can add users who should have restricted access to your organization as
|
|
**guests**. For example, this may be a good choice for contractors or customers
|
|
invited to a company's Zulip chat.
|
|
|
|
Guest users **can**:
|
|
|
|
- View and send messages in channels they have been subscribed to, including
|
|
viewing message history in the same way as other channel subscribers.
|
|
|
|
Guest users **cannot**:
|
|
|
|
- See private or public channels, unless they have been specifically subscribed
|
|
to the channel.
|
|
- Create new channels or user groups.
|
|
- Add or manage bots.
|
|
- Add custom emoji.
|
|
- Invite users to join the organization.
|
|
|
|
You can also **configure** other permissions for guest users, such as whether they
|
|
can:
|
|
|
|
- [Move](/help/restrict-moving-messages) or
|
|
[edit](/help/restrict-message-editing-and-deletion) messages.
|
|
- Notify a large number of users [with a wildcard
|
|
mention](/help/restrict-wildcard-mentions).
|
|
|
|
Zulip Cloud plans have [special discounted
|
|
pricing](/help/zulip-cloud-billing#temporary-users-and-guests) for guest users.
|
|
|
|
## Configure guest indicator
|
|
|
|
{start_tabs}
|
|
|
|
{tab|desktop-web}
|
|
|
|
{settings_tab|organization-permissions}
|
|
|
|
1. Under **Guests**, toggle **Display “(guest)” after names of guest users**.
|
|
|
|
{!save-changes.md!}
|
|
|
|
{end_tabs}
|
|
|
|
## Configure warning when composing a DM to a guest
|
|
|
|
Zulip can display a warning to let users know when recipients for a direct
|
|
message they are composing are guests in your organization. The warning will be
|
|
shown as a banner in the compose box on the web and desktop apps.
|
|
|
|
{start_tabs}
|
|
|
|
{tab|desktop-web}
|
|
|
|
{settings_tab|organization-permissions}
|
|
|
|
1. Under **Guests**, toggle **Warn when composing a DM to a guest**.
|
|
|
|
{!save-changes.md!}
|
|
|
|
{end_tabs}
|
|
|
|
## Configure whether guests can see all other users
|
|
|
|
{!cloud-plus-only.md!}
|
|
|
|
You can restrict guests' ability to see other users in the organization. If you
|
|
do so, guests will be able to see information about other users only in the
|
|
following cases:
|
|
|
|
- The user belongs to a [direct message](/help/direct-messages) thread with the
|
|
guest.
|
|
- The user is subscribed to one or more [channels](/help/introduction-to-channels) with
|
|
the guest.
|
|
|
|
When a guest cannot see information about a user, the guest's experience will be
|
|
that:
|
|
|
|
- The user does not appear in the right sidebar.
|
|
- The user does not appear in typeahead suggestions, e.g., in the compose box
|
|
and search.
|
|
- Otherwise, such a user will be displayed as an **Unknown user** in the Zulip
|
|
app. For example, messages and reactions from a former subscriber of a channel
|
|
will be shown as from an **Unknown user**.
|
|
- An **Unknown user**'s [user card](/help/user-cards) will not display
|
|
information about that user. However, the guest can still search from all
|
|
messages send by a particular **Unknown user** from that user's card.
|
|
|
|
In practice, guests should rarely encounter content from an **Unknown user**,
|
|
unless users in your organization frequently change their channel subscriptions
|
|
or are [deactivated](/help/deactivate-or-reactivate-a-user).
|
|
|
|
The only information guests can access about unknown users via the [API](/api/)
|
|
is which user IDs exist, and
|
|
[availability](/help/status-and-availability) updates for each user ID.
|
|
|
|
!!! tip ""
|
|
|
|
Self-hosted organizations can disable API access to availability updates
|
|
by [configuring](https://zulip.readthedocs.io/en/stable/production/settings.html)
|
|
`CAN_ACCESS_ALL_USERS_GROUP_LIMITS_PRESENCE = True`. For performance reasons,
|
|
this is recommended only for organizations with up to ~100 users.
|
|
|
|
{start_tabs}
|
|
|
|
{tab|desktop-web}
|
|
|
|
{settings_tab|organization-permissions}
|
|
|
|
1. Under **Guests**, configure **Who can view all other users in the
|
|
organization**.
|
|
|
|
{!save-changes.md!}
|
|
|
|
{end_tabs}
|
|
|
|
## Related articles
|
|
|
|
* [User roles](/help/user-roles)
|
|
* [Invite new users](/help/invite-new-users)
|
|
* [Change a user's role](/help/user-roles#change-a-users-role)
|
|
* [Zulip Cloud billing](/help/zulip-cloud-billing)
|