Email and calendar

Personas

A persona is a sending identity — an address you send from. A workspace can hold several, which is the normal case for anyone running more than one brand or keeping studio mail apart from personal mail.

Mail arrives into one inbox regardless of which persona received it, and replies go out from the persona the thread belongs to.

How mail finds its client

Incoming mail is matched to a client by the address it came from and the contacts you have recorded. A matched message shows up on that client’s activity log without you filing it anywhere.

Where a match is wrong or missing, logging a message to a record deliberately makes a permanent copy as an activity log entry. That matters because message bodies themselves are a prunable cache.

Message bodies are a cache

Bodies are the bulk of a typical workspace, so they are stored as a cache you can age out — forever, or twelve, six, three or one month. Choosing a shorter window is the single biggest lever on how large your database gets.

Attachments are never stored in the database at all. They are fetched from the mail server when you open them.

Anything you deliberately logged is exempt. It has its own copy and is not pruned.

Calendar

The calendar reads across everything in the workspace — tasks, meetings, project milestones — rather than being a separate thing you maintain.

Two-way sync is available with Google Calendar or Microsoft 365, per persona. Applied scheduling moves push out to the calendars of personas that sync.

Files can be attached from Drive or OneDrive, and as everywhere else in BooshHUB what is stored is a link rather than a copy.

One deliberate limitation

Your external calendar does not feed the auto-scheduler. It is drawn so you can see it, but it is not treated as busy time. The reasoning is in Planning your week with Optimise — in short, an all-day birthday marker should not blank a working day.