Wavebox makes working across different SaaS apps easy, which sounds simple enough, right? Erm no, in fact, there's a ton of magic required under the hood to ensure your apps, websites and links all work seamlessly together.
In Wavebox, much of this magic involves 'Cookie Containers' (formerly Cookie Profiles) and 'Groups' and in this post you'll learn more about these features, and how best to use them when setting up your Wavebox browser workspace.
What is a Cookie Containers?
Cookie containers are used to either isolate or share cookies between apps. Choosing the right container mostly depends on what you want to do...
Sharing Cookie Containers
When you add your first app to Wavebox (normally your email login app) the default cookie container is chosen for you. This is to ensure that all your apps share the same cookie jar, so when you click on a link in one app it opens up in the correct app, without you having to sign-in again. It's worth noting that even though you may sign-in to these apps with different logins, they can still share the same cookie container in Wavebox and work seamlessly together.
Isolating Cookie Containers
If you try to add a second app of a particular type to Wavebox you will be prompted to create a new cookie container for it, therefore isolating it from other apps. This prevents accounts of the same type getting muddled e.g. to avoiding seeing the files of one Google Drive in another Google Drive 😱. Once created, this new cookie container can be used for other apps you want it to work with (as described above under 'Sharing Cookie Containers').
You also may have a situation where you just don't want an app to share cookies with any other app. For example, you may want to isolate your 'home' apps from your 'work' apps. In this case, you'd choose a new cookie container when adding your home apps.
What's the Default Cookie Container all about?
If you add any extensions they will work across all cookie containers, but under-the-hood they store their own extension cookies in your default container cookie jar. This means that if you login to your extension, then they will share the same logins as your default container. You can change your default container at any time, so that you can login to your extension. Just go to 'Settings > Cookie Containers > Choose a Group or App > Click on more icon (three dots top right) > Select 'Make Default Cookie Container'.
Essential facts about cookie containers:
- You don't need to create a new cookie container every time you add an app. This is only needed when you add a second app of a particular type, or you want to purposely isolate it.
- Apps in a group can have different cookie containers.
- We advise that you use groups to organise your apps, rather than cookie containers.
which leads us on to....
What are Groups?
Groups are for organizing your apps.
Groups live down the side of your workspace as large rounded square icons. They can contain one or more apps. Apps in a group appear as smaller circle icons located in the top toolbar (on the left or right) or in the sidebar underneath the main group icon. Example groups could be:
- Group apps for a particular workflow.
- Group apps for a project.
- Group apps for an individual client.
- Group apps of a particular type e.g. 'home' apps or 'work'.
- Group apps of the same type e.g. Slacks, Trellos, Gmails (note - when you're adding apps of the same type they will need their own cookie container)
There are a couple of settings which cover all apps in a group, such as the sleep setting. The group unread badge also displays the total number of unreads for all apps in that group.
Bringing Groups and Containers together.
When you add a new app to a group, the add app screen will suggest using the group cookie container. This is so that links between apps in that group will flow seamlessly, without you having to keep signing-in.
However, groups can include apps with different cookie containers - just bear in mind that links will not work correctly between them. But this may be your desired behaviour e.g. organising all your Gmail's together in one group - they need to be kept separate but you don't need to work across them.
Some fast facts about groups:
- You can move your groups and apps around the sidebar and top toolbar by dragging them (Version: 10.101) Try it!
- You can change the container of an app at any time using the right-click menu followed by 'Settings > App Settings > Cookie Container' (if you do change the container of an app or group, you may need to sign-in to your apps again).
- You can right-click on any group icon in the sidebar and select 'Move app to' to change its location.
So what are Workspaces for then?
You can add existing apps or weblinks to workspaces by clicking on the '+' icon (top-right corner of the workspaces box). Workspaces offer a way of bookmarking apps and links that you may use on a regular basis. For example, you may have a particular Google document you're working on at the moment, and you want to group it with a project worksheet or Trello board. Pop a link to them in a workspaces for easy navigation, then delete when you're done (this doesn't delete the app or link from elsewhere in Wavebox).
Also, if you create a Connect Team, a shared workspace will automatically be created for your team. This updates in real-time and is shared across everyone in that team. You can create as many teams as you like, and therefore as many shared workspaces. Shared workspaces are perfect for onboarding new people to Wavebox.
But it's up to you how you use Wavebox!
The best thing to do is have a play, and maybe rethink how you work on the web. For example, there's no need to jump out to your default browser (e.g. Chrome) or desktop app when you can link across to apps within Wavebox and work seamlessly between them without having to sign in and out. (Remember, links will work across apps in different groups if they share the same cookie container!)