Skip to main content
Ghost Mode

A conversation
for the moment.

Propose a temporary session in a direct message. Show participants the consent and expiry terms, with message-history cleanup governed by the session policy.

CoplaceTeam workspaceSample workspace
Ghost ModeThe first-week plan
Participants review the terms and give their own consent.

Product tour with sample contentCompare the waiting and approved examples. When everyone must agree, the conversation opens after the final participant accepts.

Clear terms for a temporary conversation.

Participants see the session terms before a temporary conversation begins. Consent requirements, expiry, and leaving behavior determine when its temporary message history is cleaned up.

  • Consent terms shown to participants

    Participants see the temporary-session proposal and its terms. Each person gives their own consent; agreement is not assumed on someone else’s behalf.

  • Option to wait for everyone’s agreement

    When the session requires everyone’s consent, it waits until the final participant accepts. Waiting and active states are distinct.

  • Message cleanup after expiry or leaving

    The session’s expiry and leaving policy govern cleanup. Expiry or leaving clears temporary history according to the active policy.

  • Temporary message history kept out of search

    Temporary message history is kept out of search results. Write decisions that need a lasting record in the appropriate place outside the session.

See when the session has started.

The first example waits for the last participant’s agreement. Here, everyone has accepted and the conversation is visible. The control demonstrates those states; it does not give consent for real people.

CoplaceTeam workspaceSample workspace
Ghost ModeThe first-week plan

The first-week guide is drafted. Shall we add the team channels too?

First-week guide.pdf240 KB

I’m preparing the first-day schedule. The team introduction is on the calendar too.

Use Show the waiting state to compare the view before and after consent.

Agree on the terms before starting.

When everyone’s agreement is required, the session waits for the last participant to accept. Compare the waiting and approved examples.

  1. Propose a session

    Show temporary-session terms to participants in the direct message.

  2. Wait for approvals

    When everyone’s agreement is required, the session waits for the final participant to accept. The terms remain visible while the session is waiting.

  3. Manage expiry

    See remaining time and clear temporary message history when the expiry or leave policy applies.

Participants can see that the session is temporary and understand its cleanup terms. Record lasting work decisions separately.

Choose a temporary session deliberately.

A temporary direct conversation

Propose a temporary session in a direct message. Show participants the expiry and consent terms and follow the acceptance state.

Work that needs a lasting record

Task scope, due dates, and project decisions need to be revisited. Keep them in a channel, task, or Canvas outside the temporary session.

Understand what temporary history covers.

Ghost Mode covers temporary message-history cleanup under the session policy. It does not mean every physical copy of a shared file is deleted. Use a lasting record for work decisions that need to be kept.

Frequently asked questions.

A few details about using this feature and what it covers.

Start with clear session terms.

Open Ghost Mode in a direct message, read the consent and expiry terms, and propose the temporary conversation.