Rambox workspaces: keep work and personal accounts separate

A workspace gives related apps a place to live. Account isolation is a separate concern: before adding a second account, decide which apps should share a session and which need an independent one. This setup checklist helps avoid sending a message or sharing a file from the wrong account.

Group apps by the work you are doing

Start with two clearly named workspaces, such as Client work and Personal. Put only the apps needed for each context in that workspace. A long list of almost identical groups makes switching harder; a small set that matches your day is easier to maintain. Keep client-specific tools together when the client boundary matters more than the app category.

Check session separation before signing in

Rambox workspace settings can use a profile scheme or a private profile. Review the current profile setting before adding services that use the same sign-in provider. A separate visual workspace alone is not proof of a separate login session. Add one app first, sign in, then inspect the account shown inside that service before adding the rest.

Name each app instance for its account

Use an account or client label that is recognizable without opening the app. After adding a second instance, open both and inspect the signed-in identity in each service. Check the sender account before sending mail and the destination workspace before sharing a document. Do not use a test that sends a real message to a customer; inspect the account menu or a draft instead.

Review shared devices and notifications

A tidy workspace does not replace device security or each service’s access controls. Lock the computer when away, and avoid displaying sensitive message previews on a shared screen. Review notification settings for each work context so personal alerts do not interrupt a presentation. After changing profile settings, repeat the account check instead of assuming existing sessions moved automatically.

Further reference

Updated:2026-09-17