In Rambox, we have "Profiles", a Pro feature that gives you the flexibility to share sessions across multiple apps (so you only have to log in once), use private sessions to sign in to multiple accounts of the same service, or incognito profiles to not store apps' history and cookies information.

You can find the Profile setting in the Apps and Workspace Settings. There are four main Profiles: "Primary" (default profile), "Inherit from Workspace" (only for nested elements), "Private" (isolated session), and "Incognito":

Also, by clicking the plus sign, you can edit and add more profiles of your own:

By clicking on the "globe" icon, you will be able to configure the profile's proxy settings:

• Auto detect: the app will use the proxy configurations set in Rambox's General Settings.
• No Proxy: do not use proxy.
• HTTP, HTTPs, Socks4, Socks5: if you want to use a proxy, these options will show you some configuration fields for you to set.

Bear in mind that these configurations are "Profile-Specific", so any app using a shared profile will share these proxy configurations, too. You can read more about configuring proxies per profile in THIS LINK.

You can create a profile and assign it to a number of apps. Let say that you create a "Work" profile where you get logged to Gmail using your work credentials. Then you can add, let say, a Google Drive app anywhere in Rambox and assign it the "Work" profile too, and this Google Drive app will get logged using those credentials.

Also, you can set a profile scheme for a workspace and all the apps and workspaces within it, or even assign the workspace a private profile if you want that all nested apps have their own isolated profile. In order to use the workspace profile setting, the nested element must have the "Inherit from Workspace" profile set (this is the default profile for nested apps). 

For apps like WhatsApp, Telegram, Discord or Android messages, we recommend the private profile (isolated per app), which is the default when adding them.