Remember the last time you forwarded a teammate an email so they could weigh in? That familiar workaround is exactly what Visitor View replaces.
Share the conversation itself with a client, adviser, or contractor. They can respond where their context matters without entering the rest of your workspace.
View
Invite outside collaborators into the conversation
External partners often live in long forwarding loops. Feedback gets separated from the message it refers to, and the team spends time translating replies back into the thread.
With Visitor View, invite someone by email and keep the discussion together. They open a focused conversation, see the context you shared, and reply directly.
What a visitor gets—and what stays private
Visitors enter the conversation they were invited to. They do not see the team inbox, other threads, internal notes, or unrelated contacts.
Each conversation can include up to eight visitors, and each receives their own access link. The separation is deliberate: the shared context is useful because the boundary is obvious.
I wish this person could see this conversation—now they can.
Teams told us this sentence was the real requirement. Some work with clients for months; others need a specialist for one decision. Visitor View supports both without asking every collaborator to adopt a new workspace.
Admins remain in control
Workspace admins choose who can send invitations and can review every active visitor from one place.
Frequently asked questions
Can visitors see the full message history?
They see the history included when they were invited, plus new messages in that conversation.
Can a visitor add someone else?
No. Only teammates with invitation permission can add or remove participants.
What happens when access is revoked?
The link stops working immediately and the visitor can no longer open the conversation.
Can we see which visitor read a message?
Yes. Read activity appears beside the participant record for that thread.