What this helps you do
Setup gets your community ready to send: the profile and branding, the timezone and interface language, the community-controlled Blasts account, the email sending address, and the preferences page where residents choose what they receive. A new community sets all of this up through onboarding, and the Hub activates with its first credit purchase from BlastCredits.
When to use it
Do this once when you first start, and revisit it when the management company changes, the board turns over, or you add a community.
How to do it
- Sign in at /hub/signin/ with an email code, a passkey, or Sign in with Blasts, then open Settings.
- Enter the community or management company name and website so the logo and colors can be captured automatically.
- Set your timezone and country so an 8 a.m. shutoff notice actually goes out at 8 a.m. where the community is.
- Choose your interface language. Residents choose their own language on their preferences page.
- Confirm the community-controlled Blasts account: a mailbox on the community's or the management company's own domain (not a manager's personal address), which is the root of ownership and recovery. Publish the DNS TXT record Settings shows you to verify the domain, and leave it published.
- Check Email sending: the Hub provisions a sending address for you. The weekly digest for residents who are still on email goes out on Wednesday at 10 a.m. local for a new community; change the day and hour there. Every new Hub starts with 50 email credits.
- Copy the resident preferences link into the move-in packet and the welcome email; that is where each resident chooses which topics they hear about, and where someone still on email can pick a weekly digest instead of every message.
- Decide on auto-accept. Off, each resident who enters your code is a request you accept on Residents; on, they are connected the moment they join. A manager's Blasts go out without an administrator's approval for a new community; turn approval on in Settings if you want that review. The two settings are independent.
Example
A management company sets up one Hub per community. For each one it enters the community name and website, sets the timezone, verifies the domain on the company's own mailbox, turns on auto-accept, leaves approval off, and puts the preferences link in the move-in packet so residents pick their building and their topics before the first Blast goes out.
Good to know
- The Blasts account belongs to the community or the management company, not to one manager, so it keeps working when staff move on or the board turns over.
- Add a passkey on Home so step-up confirmations for All Residents sends use Face ID, Touch ID or your device PIN.
- One Hub per community keeps audiences, history and credits separate, which is what a board expects when a management contract ends.
- You can change the interface language anytime; only the Hub chrome changes, never what residents wrote or chose.
- Setting the Hub up changes nothing in your property-management system, your access system or your reservation process. Keep running leases, work orders, payments, reservations and access where you run them now.