Rambox: group your apps and keep their sign-ins clear

Working for two clients may mean two inboxes, two calendars and several chats. The difficulty is not just the number of windows: it is knowing which account opens when you select one. Rambox is a desktop tool for using web apps in one place. Each service becomes an app in its sidebar, and related apps belong to a workspace.

The workspace guide uses work, personal life and client projects as examples. In Rambox 3, workspaces sit at the same level and every app belongs to one. A workspace groups apps; a Profile is a named sign-in session determining which apps share login information. Understanding both avoids assuming that a separate group automatically means a separate account.

Suppose Client A and Client B each use a Google account. The following suggested setup groups each client's inbox and calendar. Multiple workspaces, custom profiles and shared sign-ins require Pro or a trial. Basic includes one workspace and automatically gives each app its own session.

If upgrading from Rambox 2, first read the migration guide. Once the account is moved, the old version cannot sign in with it, and old windows on other computers are signed out. Enterprise users should check their organization's migration arrangements first.

1. Create the groups. Choose Add workspace in the sidebar, name it Client A and select Add. Once it appears, enter it to add the relevant services. Create another workspace for Client B.
2. Set the sign-in relationship. Right-click a workspace and open its settings. Select “+” beside Profile to open the Profiles panel. Select Create, enter Client A and confirm. The new profile appears as a card and in Profile choices. Create Client B the same way, then select and save the corresponding profile in each workspace. The profile guide explains that new apps inherit the workspace's profile by default, while different profiles keep sign-ins apart.
3. Add apps and sign in. In Client A, choose Add app and add Gmail and Google Calendar from the catalog, then sign in with Client A's account. The same profile lets these apps share Google sign-in; Client B uses a different profile. The app guide covers the catalog, adding apps and account copies. Check each service's account indicator afterward to confirm the setup.
4. Set notification hours. In workspace settings, enter a Work hours range such as 09:00–18:00 and save. The official guide says apps keep running outside that range while sounds, notifications and the workspace badge go quiet. The same range applies every day using the computer's clock; overnight ranges and individual weekdays are unsupported.

Changing an existing app's profile prompts a reload and may require another sign-in. Planning account ownership before adding apps is generally easier to check than changing them one by one afterward.

Give visible groups and sign-in relationships separate jobs

The Client A workspace tells users which group of work they are handling. The Client A profile tells them which sign-in information the apps use. They can work together without being forced to match: an individual app can use a different profile. That separation supports complex arrangements, but newcomers need to understand inheritance. The useful lesson is to display current ownership clearly instead of expecting a colored label to explain everything.

Quiet the interruptions without closing the work

Work hours control notifications rather than shutting down apps. Users can still choose to check an email in the evening. If they are waiting for an important message, Bypass restrictions in that app's banner temporarily restores alerts, and Restore restrictions makes it quiet again. This separates receiving work from interrupting someone now. A daily range is easy to understand, while shift and cross-time-zone work still need attention to the schedules it cannot represent.