OX App Suite Professional Email Boosts Productivity

Mailbox Structure and Team-Wide Access Control

A shared mailbox setup determines how quickly a five-person team or a fifty-person department can act on incoming messages without stepping on each other’s replies. OX App Suite handles this through a permission model that separates ownership from delegated access at the folder level, rather than granting all-or-nothing mailbox control, as many legacy hosted email systems do.

How Folder-Level Permissions Work in Practice

Each mailbox folder in OX App Suite, inbox, subfolders, and shared drafts, carries its own access control list, so an administrator can grant one colleague read-only visibility into a support inbox while giving another full send-as rights without exposing archived folders. This differs from flat mailbox sharing, where anyone added to a shared inbox typically inherits the same permissions across all folders within it. The distinction matters most in sales and support teams, where a manager may need oversight without every team member being able to delete historical threads permanently. Reputable providers generally target at least 99.9% uptime for hosted business email, and permission granularity like this only holds value when the mailbox itself is reliably reachable.

Setting this up correctly takes a bit more planning than a generic shared inbox, since someone has to decide, folder by folder, who gets what. In practice, this front-loaded effort pays off within the first month: fewer accidental deletions, fewer “who moved this email” conversations, and cleaner audit trails when a compliance question comes up. Agencies managing multiple client-facing inboxes tend to notice the difference most quickly, since client folders can be walled off from internal ones without creating a second mailbox. Enterprises with formal role hierarchies can mirror those hierarchies directly in the mail client instead of managing a separate permissions spreadsheet.

Where Flat Sharing Still Makes Sense

Not every team needs folder-by-folder control. A two-person consultancy sharing a single “info@” inbox usually wants both people to see everything and reply freely. OX App Suite supports that simpler configuration without forcing anyone through a permissions wizard. The setup collapses to a single shared-access grant, which takes less than a minute per user once the mailbox itself exists.

The trade-off becomes apparent as the team grows beyond a handful of people. What starts as “everyone sees everything” tends to become unmanageable once a business adds a second department, a contractor, or a client-facing role that shouldn’t see internal negotiation threads. Teams that anticipate this growth early tend to set up folder-level permissions from day one, even while small, rather than retrofitting access rules onto years of unsorted mail later. That early structuring is a small time cost that avoids a much larger cleanup project down the line.

Shared Calendars That Keep Teams Aligned

Scheduling breakdowns cost teams real time, double-booked meeting rooms, missed handoffs between time zones, and calendar invites that never sync to a phone. OX App Suite addresses this by using calendar sharing built on open synchronization standards rather than a proprietary format locked to a single client.

CalDAV and CardDAV Behind Team Scheduling

OX App Suite calendars sync using CalDAV for events and CardDAV for contacts, both open protocols also supported by Apple Calendar, Thunderbird, and most modern phone operating systems. Because the sync layer is protocol-based rather than proprietary, a team member can view a shared department calendar in their native phone calendar app without installing a dedicated OX application, and changes made in either location propagate back through the same channel. This differs from platforms that require a specific branded app for full calendar functionality, which becomes a friction point the moment someone prefers their device’s built-in calendar. For distributed teams, standards-based sync also means new hires can be onboarded onto shared calendars using whatever client they already use daily.

The practical benefit shows up in meeting room booking and cross-departmental visibility. A marketing lead can glance at engineering’s shared calendar to find a free slot for a joint planning session without sending three back-and-forth emails asking about availability. Recurring meetings, holiday calendars, and project deadlines can live on a shared read-only calendar that every department subscribes to, so schedule changes propagate automatically rather than requiring a separate announcement email. Teams running hybrid schedules, where some staff work from an office and others remotely, tend to lean on this the most, since time zone conversion happens automatically inside the client rather than manually in someone’s head.

Booking Conflicts and Resource Calendars

Meeting rooms, shared equipment, and pooled vehicles can be modeled as resource calendars in OX App Suite, allowing an organizer to check availability and reserve a resource in the same step as sending a meeting invite. When two people attempt to book the same conference room for overlapping times, the system flags the conflict at the point of booking rather than leaving it for someone to discover on arrival. This is a meaningfully different workflow from teams that manage room bookings through a shared spreadsheet or a sign-up sheet taped to a door, both of which rely entirely on people remembering to update them.

Smaller offices with a single shared meeting room sometimes skip resource calendars entirely and check the room calendar manually, which works fine at that scale. Once an organization has multiple rooms, multiple locations, or shared equipment such as a projector cart or a company vehicle, manual checks break down quickly. Setting up resource calendars takes an administrator a few minutes per resource, and it removes an entire category of “sorry, is this room taken” interruptions from a team’s day, which adds up across dozens of meetings scheduled each week.

Document Collaboration Inside the Inbox

Attaching a file, waiting for edits, and reconciling three different versions by filename is still how many teams handle shared documents. OX App Suite folds basic document editing into the same interface as mail and calendar, reducing the number of times a team needs to open a separate word processor to review a file someone emailed them.

Editing Attachments Without Leaving the Mail Client

OX Documents lets a recipient open a Word-compatible or spreadsheet attachment directly in the webmail interface, make edits, and save the result back to the conversation or shared storage without first downloading the file to a local device. This matters most for quick reviews, correcting a typo in a proposal, adjusting a number in a shared budget sheet, where downloading, editing in a separate application, and re-attaching would otherwise take several extra steps. Because the editing happens inside the same browser tab as the inbox, there’s also no risk of an edited file getting stranded in a downloads folder and never making it back into the shared conversation.

The trade-off is that OX Documents targets everyday editing rather than replacing a full-featured desktop suite. Complex formatting, advanced spreadsheet formulas, or heavy design work still tend to be routed through dedicated software, with OX Documents serving as the fast, in-context option for the other 90% of edits a typical business day involves. Teams that live mostly in quick reviews and lightweight edits get the most out of this; teams producing polished client-facing design documents will still reach for specialized tools for the final pass.

Version History and Concurrent Edit Handling

When more than one person opens the same document in OX Documents, changes merge through the platform’s conflict-handling mechanism rather than producing duplicate copies with “final” and “final_v2” in the filename. Version history keeps earlier states of the document accessible, so a team member can roll back an accidental deletion or compare how a paragraph read before a colleague’s edit. This removes a specific, recurring source of confusion in teams that previously tracked document versions manually through email subject lines.

Smaller documents with light collaboration, a single person drafting, and one other person reviewing rarely need to think about version history at all, since conflicts are unlikely. The feature earns its keep on documents with several simultaneous contributors, such as a shared meeting agenda that three people edit at once before a call starts. In that scenario, being able to see who changed what, and when, saves the awkward “wait, did you delete that section on purpose” conversation that used to happen over chat.

File Storage and Sharing With OX Drive

Email attachments are a poor long-term storage system, inbox size limits, duplicate copies scattered across recipients’ mailboxes, and no single source of truth for the current version of a file. OX Drive gives teams a dedicated storage layer that email and document editing both draw from directly.

Linking Instead of Attaching

Rather than attaching a file copy to every outgoing email, OX App Suite lets a sender insert a link to a file stored in OX Drive, with the recipient opening the live version instead of a static snapshot. This keeps a single authoritative copy of a document in one place, so any update made after the email is sent is automatically reflected for anyone who opens the link later, rather than recipients working from whatever version was attached at send time. It also avoids inbox bloat: a 40MB file linked once instead of attached to a twelve-person email thread saves meaningful mailbox storage across every recipient.

Sharing links can include expiration dates and optional passwords, which matter when a file needs to be sent to an external client or vendor rather than an internal colleague. An administrator can set a link to expire after the proposal deadline, closing access without needing to revoke it manually later. This is a small detail, but it’s the kind of access-control gap that causes real problems when ignored, old shared links to sensitive files left open indefinitely because nobody thought to close them.

Storage Organization for Team and Client Files

OX Drive supports shared team folders alongside individual personal storage so that a project folder can be visible to everyone on a client account. In contrast, a person’s personal drafts stay private by default. Folder structures can mirror how a team already organizes work, by client, by project, by department, rather than forcing a flat structure that becomes unsearchable as file counts grow. Search inside OX Drive covers file names and, for supported formats, document contents, which matters when a shared drive holds hundreds of files rather than a manageable handful.

Agencies juggling several client accounts tend to get outsized value from this structure, since each client’s files stay contained in their own folder tree with permissions matched to who’s actually working that account. A freelancer or very small team, by contrast, might use only a couple of shared folders and never need the deeper hierarchy, which is fine, since the structure scales down as easily as it scales up. The underlying storage pool itself is covered in more detail later in the context of mailbox and drive quotas.

Security Layers That Protect Team Productivity

A single successful phishing email or a compromised mailbox can cost a team more lost time than months of minor inefficiencies combined, including incident response, password resets, client notifications, and lost trust. Security in OX App Suite is built to reduce that risk without adding so much friction that people work around it.

Encryption Handled Through OX Guard

OX Guard adds end-to-end encryption to OX App Suite email using S/MIME and PGP standards, allowing a sender to encrypt a message so that only the intended recipient’s private key can decrypt it, even if the message is intercepted in transit or the mail server itself is compromised. Key management happens within the same webmail interface rather than requiring a separate encryption application. This is typically where end-to-end encryption adoption breaks down on other platforms: people abandon it because the key exchange process feels disconnected from their everyday inbox. OX Guard also supports encrypted file attachments, extending the same protection beyond the message body itself.

This level of encryption matters most for regulated industries, legal, healthcare, and financial services, where a client’s personal or financial information travels by email regularly, and a data exposure carries real compliance consequences. A general business sending routine internal correspondence may reasonably decide that standard transport encryption (TLS between mail servers) is sufficient for day-to-day use, reserving OX Guard for messages that actually contain sensitive content. Renewal reviews commonly surface a stale SPF record that the body remembers adding, and encryption settings deserve the same periodic review. A policy that made sense a year ago may no longer match what the business actually sends today.

Spam and Phishing Filtering Before Messages Arrive

Filtering happens before a message reaches the inbox, scoring incoming mail against known spam patterns, sender reputation, and malicious attachment signatures, and routing anything above a risk threshold into a separate quarantine folder rather than the primary inbox. This keeps the volume of junk a team has to manually sort through low, which matters more than it sounds. Every message a person has to open and evaluate before dismissing it is a small productivity cost repeated dozens of times a day across a team.

Quarantined messages remain reviewable rather than silently deleted, since aggressive spam filtering occasionally catches a legitimate message from a new sender or an unusual domain. A weekly quarantine review, delegated to whoever manages the mailbox, catches these false positives before a real client inquiry gets missed entirely. Two-factor authentication adds a second layer on top of filtering, requiring a time-based code or app confirmation alongside a password before a mailbox can be accessed from an unrecognized device, which meaningfully reduces the damage a single leaked password can do.

Get Set Up With an Authorized OX App Suite Partner

Encryption and spam filtering only protect a team when they’re configured correctly from the start, which is where working with an established reseller makes the setup faster and less error-prone. Hiya Digital, as an Authorized Partner for OX App Suite Email Service, helps businesses configure mailbox security, permissions, and onboarding without the trial-and-error a DIY setup often involves.

View OX App Suite Plans →

Mobile Access and Cross-Device Sync

A team that can only work efficiently from a desk loses hours to travel, commuting, and time away from the office. OX App Suite supports both a dedicated mobile application and native device mail clients, giving teams a choice depending on how deeply they need mobile features versus how simply they want mail to appear on a phone.

Dedicated App Versus Native Mail Client Setup

The OX Mail mobile app mirrors the desktop webmail experience more closely, including folder permissions, OX Drive access, and push notifications tuned specifically for OX App Suite. Connecting a phone’s built-in mail app via standard IMAP and SMTP settings provides basic send-and-receive functionality without the extra features. A field sales rep who regularly needs to check a shared team folder or pull a file from OX Drive between client visits benefits from the dedicated app’s deeper integration with OX Drive. Someone who wants email notifications on their personal phone without installing another app can use the native client route instead, trading some functionality for a setup that takes under two minutes.

Both paths keep messages in sync with the desktop mailbox. Hence, a message read on a phone shows as read when the same person opens the desktop client later, and a calendar event created on mobile appears immediately in the shared team calendar. This two-way consistency is what actually saves time day-to-day; nobody has to double-check whether an email was already handled by checking two separate inboxes that don’t communicate.

Offline Access and Sync Delays

Both the dedicated app and native mail clients cache recent messages locally so that a team member can read and draft replies without an active connection, useful on a flight, in a parking garage, or anywhere a signal drops briefly. Drafts written offline are queued and sent automatically once connectivity returns, rather than requiring the person to remember to resend them manually. Calendar changes made offline sync in the same way, appearing on other devices once the phone reconnects.

Sync isn’t instantaneous in every scenario; a weak connection can delay a new message’s arrival on mobile by a few minutes compared to a strong Wi-Fi connection, and heavy attachments may pause syncing until a better connection is available. This rarely affects day-to-day productivity, but it’s worth knowing before relying on a mobile device for a time-sensitive approval that must happen within seconds, not minutes. Teams handling urgent, time-critical communication sometimes set a policy of confirming receipt by a second channel for anything truly time-sensitive, rather than assuming instant mobile delivery.

Custom Domain Email and Professional Branding

A message from a free webmail address reads differently to a client than one from a company’s own domain, and that difference affects trust before a single word of the email is even read. Custom domain email is a baseline expectation for any business past the earliest freelance stage.

DNS Records That Make a Custom Domain Work

Setting up custom domain email requires an MX record that points incoming mail to the provider’s servers, along with SPF, DKIM, and, ideally, DMARC records published as TXT records to authenticate outgoing mail. SPF (Sender Policy Framework) lists which servers are authorized to send mail on a domain’s behalf, and the standard SPF specification, RFC 7208, caps lookups at ten per check, a limit that trips up domains layering multiple third-party services (a CRM, a marketing platform, a help desk) into one SPF record without consolidating them under includes. DKIM (DomainKeys Identified Mail) works differently: OX App Suite provisions a unique DKIM key per domain rather than sharing a single signing key across all hosted domains on the platform, so a signature failure or key rotation on one client’s domain never affects another’s deliverability.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together, telling receiving mail servers what to do with a message that fails both checks: quarantine it, reject it outright, or monitor and report it. A domain with no DMARC record leaves the decision entirely up to the recipient’s mail server, resulting in inconsistent outcomes. Starting DMARC in monitoring-only mode and gradually tightening it over a few weeks, once reports confirm that all legitimate mail sources pass, helps avoid accidentally blocking a business’s own outgoing mail during setup.

Subdomain and Alias Structures for Departments

Beyond the base domain, OX App Suite supports department-level email addresses and aliases, sales@, support@, billing@, all routing through the same custom domain without requiring separate hosting accounts for each. Aliases can forward to a shared mailbox, a specific individual, or a distribution list that expands to multiple recipients, giving a business flexibility in how incoming mail for a given role gets distributed without customers needing to know which specific person handles it.

Larger organizations sometimes extend this further with subdomains for distinct business units, mail.division.company.com, for instance, each carrying its own SPF and DKIM configuration if the unit’s outgoing mail volume or sending patterns differ enough to warrant separating deliverability reputations. A single-location small business rarely needs subdomain separation and typically manages fine with role-based aliases under one domain. The right structure depends on how independently different parts of the business actually operate, not on company size alone.

Storage Scalability for Growing Teams

Running out of mailbox or drive space at an inconvenient moment, mid-project, mid-client-onboarding, is a preventable disruption that still catches teams off guard regularly. Planning storage ahead of actual need avoids the scramble.

How Mailbox and Drive Storage Pool Across a Team

OX App Suite plans typically allocate storage as a pool shared across a domain’s mailboxes and connected OX Drive space rather than strictly siloing a fixed quota per individual user. However, exact pooling behavior and per-user caps vary by the specific plan tier a business is on. This pooled approach means a team with uneven usage, one person who archives everything, another who barely stores files, draws from shared capacity instead of one person hitting a hard individual ceiling. In contrast, pooled space sits unused elsewhere on the same domain. Administrators can typically view per-mailbox and per-drive consumption from a single dashboard to spot which accounts are consuming disproportionate space.

Storage needs rarely grow linearly; a business might sit flat for a year, then jump significantly after a large client project generates thousands of file versions and email threads in a short window. Reviewing storage consumption quarterly, rather than only reacting once a warning notification appears, gives a team time to plan an upgrade or archive old data before hitting a limit mid-project. Because exact plan allocations and upgrade paths are configuration-specific, confirming current pooled limits directly with a provider before a major project kicks off is worth the five-minute conversation.

When to Archive Versus When to Upgrade

Archiving old mail and files to cold storage or a local backup frees up active pool space without paying for a storage upgrade, and makes sense for a business with several years of historical correspondence it needs to retain for compliance but rarely accesses. This works well when the data in question genuinely doesn’t need to stay instantly searchable inside the live mailbox, old project correspondence from a client relationship that ended two years ago, for example.

Upgrading instead of archiving makes more sense when the team is actively growing, and storage consumption is a symptom of increasing activity rather than accumulated history, more employees, more client accounts, and more ongoing projects generating live files. A team caught between the two options can usually tell which situation applies by checking whether recent storage growth traces to new headcount and active work, or to years of retained mail nobody has opened in months. Mixing both approaches, archiving what’s genuinely inactive while upgrading to match real current usage, is common and often the most cost-effective path.

Migration From Legacy or Free Email Systems

Migration anxiety is one of the biggest reasons businesses delay switching email providers, even when the current system is clearly holding the team back. Understanding what actually happens during a migration removes most of that hesitation.

What a Typical Migration Involves

A migration to OX App Suite generally involves exporting existing mailboxes, often through IMAP transfer for compatible source systems. At the same time, DNS records are updated to point the domain’s mail flow to the new provider. Because DNS changes don’t propagate instantly across every server on the internet, most migrations use a dual-delivery window in which mail can briefly arrive at both the old and new systems, preventing messages from being lost during the transition rather than forcing an abrupt cutover. Calendars and contacts typically migrate separately from mail itself, since they use different underlying formats and sync protocols.

The riskiest part of any migration isn’t the mail transfer itself but rather overlooked dependencies: an old email address hardcoded into a payment processor’s notification settings, a shared calendar invite sent to a client that still points to the old system, or a mail-merge tool authenticated against the old SMTP credentials. Auditing these connected systems before migration day, rather than discovering them after the cutover when something silently stops working, is the single biggest factor in a smooth transition. As an Authorized Partner rather than the underlying infrastructure provider, Hiya Digital coordinates this planning directly with the client rather than leaving DNS timing and dependency checks entirely self-managed.

Pricing Structure and What to Confirm Before Signing

Business email pricing commonly follows an introductory rate for an initial term, followed by a renewal rate that can differ meaningfully from the first invoice, a pattern common across the hosting industry and not unique to any single provider. Because exact renewal pricing, grace periods, and proration rules vary by plan and can change over time, a business should get the specific renewal terms confirmed in writing before signing rather than assuming the introductory price is permanent. Add-ons like extra storage, additional aliases, or premium security features are typically priced separately from the base mailbox cost.

A grace period, the window after a renewal payment is missed before service is actually suspended, also varies by provider and plan, and confirming its exact length in writing avoids an unpleasant surprise if a renewal invoice is missed during a busy period. As a reseller working directly with OX App Suite Email Service, Hiya Digital can walk a prospective client through current approximate pricing ranges and what specifically is included at each tier, rather than a business having to interpret a generic rate card alone.

Team Roles, Permissions, and Administrative Control

Beyond individual mailbox permissions, a growing team needs administrative tools to manage the account as a whole, adding users, resetting access, and enforcing consistent security policy without a single person becoming a bottleneck for every small change.

Role-Based Administration Across a Domain

An administrator account in OX App Suite can provision new mailboxes, reset passwords, enforce two-factor authentication domain-wide, and manage aliases without needing separate access to each mailbox’s settings. Larger teams sometimes delegate a subset of these controls, password resets for one department, for instance, to a secondary administrator without granting full domain-wide control, keeping administrative access itself following the same principle of least privilege that mailbox folder permissions use. This layered control reduces the frequency with which a single IT contact becomes a blocking dependency for routine account changes.

Smaller teams frequently run with just one administrator, usually the business owner or a single IT-responsible employee, and that’s entirely sufficient until the team grows to the point where a single point of failure in account access becomes an actual operational risk. The transition point isn’t a fixed headcount so much as a practical question: what happens if the one administrator is unreachable for a day and someone urgently needs a password reset or a new hire needs mailbox access before a client call?

Shared Calendar Permissions at the Team Level

Shared calendars have their own permission tiers, separate from mailbox folder permissions; a colleague can be granted viewer access to view events without edit rights, editor access to add and modify events, or owner-level control to manage the calendar’s sharing settings entirely. This separation lets a manager expose a department’s schedule broadly for visibility while restricting who can actually move meetings or delete events, which matters once a shared calendar becomes a scheduling source of truth that multiple people depend on.

A small team often defaults everyone to editor access and never runs into a problem, since trust and low volume make conflicts rare. Once people outside the immediate team read a shared calendar, clients check availability, or a large department relies on a master calendar, tightening permissions to viewer-by-default, with a smaller group holding editor rights, prevents accidental changes by someone unfamiliar with how the calendar is organized. Setting this correctly from the start avoids the need to untangle an overly permissive calendar later, once bad habits have already formed.

Frequently Asked Questions

Does OX App Suite work with Outlook, or only its own webmail client?

OX App Suite connects to Outlook through standard IMAP, POP3, and SMTP protocols, and for teams wanting deeper calendar and contact integration, an OXtender for Microsoft Outlook connector is available that syncs shared calendars and folder permissions more natively than basic IMAP alone. Basic IMAP setup keeps mail synced but won’t carry over OX-specific features like folder-level sharing permissions the same way the dedicated connector does. Businesses that standardized on Outlook company-wide, particularly those with existing Outlook macros or add-ins they don’t want to give up, typically use the connector rather than switching their whole team to OX’s native webmail interface. Either path keeps mail, contacts, and calendars synced; the difference is how much OX-specific functionality carries over into the Outlook interface itself versus how much remains accessible only through webmail.

What happens to email during the actual cutover day?

Mail flow during a cutover generally isn’t a single-instant switch; DNS propagation across the internet can take anywhere from a few minutes to about 48 hours, depending on the DNS provider and the record TTL settings configured before the change. A well-planned migration lowers TTL values on DNS records days in advance of the cutover, specifically to shrink this propagation window. During the transition, a dual-delivery configuration can catch mail arriving at both old and new systems so nothing sent during the changeover window gets lost, which is a detail worth confirming directly with whoever is managing the migration.

Can a business keep its existing domain when switching to OX App Suite?

Yes, switching email providers doesn’t require changing domain registrars or the domain name itself. Only the MX, SPF, DKIM, and DMARC DNS records need to be updated to point mail delivery to the new provider. At the same time, the domain’s registration, website hosting, and any other services associated with the domain remain completely unaffected by the email switch. The one exception worth flagging: if the domain’s DNS is currently managed through the same account as the old email provider, a business will need access to whoever controls that DNS zone, or a transfer of DNS management, before the new MX and authentication records can actually be published.

How does OX App Suite handle mailbox backups?

Backup practices are typically handled at the infrastructure level by the underlying OX App Suite Email Service, rather than requiring a business to configure backups manually. However, exact retention windows and backup frequency are provider-configured details a business should confirm directly rather than assume. Regardless of provider-side backups, businesses handling regulated or highly sensitive data commonly maintain an independent export or archive of critical mail and files as a second safeguard, since relying on a single backup layer, even a reliable one, isn’t a resilient long-term strategy for anything genuinely business-critical.

Is OX App Suite suitable for a solo consultant, or is it built mainly for larger teams?

A solo consultant gets real value from custom domain email, calendar scheduling, and OX Drive file storage even without ever touching the team collaboration or folder-permission features built for larger groups. The platform scales down cleanly; a single mailbox with one calendar and no shared folders configured functions the same as a much larger deployment, just without the delegated-access layer that only becomes relevant once a second person joins. The collaboration features described elsewhere in this guide become genuinely useful the moment a consultant brings on a subcontractor or assistant, at which point folder sharing and shared calendars start solving real coordination problems rather than sitting unused.

What should be confirmed with a reseller before signing a contract?

Beyond the introductory price, it’s worth getting specific written confirmation of the exact renewal rate for year two and beyond, the length of any grace period before service suspension on a missed payment, whether storage upgrades are prorated mid-term or only apply at renewal, and what’s included versus billed as an add-on, extra aliases, additional storage blocks, or premium security features like OX Guard. Asking these questions before signing, rather than after the first renewal invoice arrives, avoids the most common source of billing frustration with hosted email services generally.

Does OX App Suite support two-factor authentication, and is it mandatory?

Two-factor authentication is supported and can be enforced domain-wide by an administrator rather than left optional per user, which is the stronger configuration for any business handling client data. Left optional, adoption is inconsistent. Some employees enable it; others skip it, leaving the least-secure account in the organization as the practical security ceiling for the entire domain. Enforcing it domain-wide from the start, ideally during initial account setup rather than retrofitted later, avoids the awkward rollout of suddenly requiring it after the team is already used to password-only logins.

How does file storage in OX Drive compare to just attaching files to emails?

Attaching files means every recipient gets their own static copy at the moment of sending, with no way to update it later without resending, and mailbox storage counted against each recipient individually rather than once. Linking a file stored in OX Drive keeps a single authoritative version that updates for anyone with the link, uses drive storage rather than duplicating it across every recipient’s mailbox, and supports link expiration for files that shouldn’t remain accessible indefinitely. For any file likely to be revised after sending or shared with more than a couple of people, linking through OX Drive avoids the version-control confusion that repeated attachments tend to create over a project’s lifetime.

Can mobile devices access shared team calendars and folders, or just personal mail?

Shared calendars and, depending on the plan configuration, shared OX Drive folders are both accessible on mobile and are not limited to an individual’s personal mailbox content. The dedicated OX Mail app generally surfaces this shared content more directly than connecting a phone’s native mail app via basic IMAP, which may show mail but does not provide the same shared-folder and shared-calendar access without additional configuration. Field-based roles, sales, account management, and on-site service that regularly need to check a shared resource while away from a desk are the clearest use case for the dedicated app over basic native mail sync.

Does switching to OX App Suite mean giving up Google Workspace or Microsoft 365 entirely, or can they coexist?

A full switch replaces the previous platform’s mail, calendar, and collaboration functions with OX App Suite’s equivalents, which is the typical setup for a business consolidating onto one platform. Some organizations run a hybrid period intentionally, migrating email first while continuing to use another platform’s spreadsheet or presentation tools separately, though maintaining two active collaboration ecosystems over the long term usually reintroduces some of the tool-switching inefficiency that a consolidated platform is meant to solve in the first place. Most businesses that start hybrid during a transition period fully consolidate onto a single platform within a few months after the migration settles.

Glossary

MX Record: A DNS record that tells sending mail servers where to deliver incoming mail for a domain.

SPF (Sender Policy Framework): A DNS TXT record listing which mail servers are authorized to send mail on a domain’s behalf.

DKIM (DomainKeys Identified Mail): An email authentication method that attaches a cryptographic signature to outgoing mail, verified against a public key published in DNS.

DMARC (Domain-based Message Authentication, Reporting and Conformance): A policy layered on top of SPF and DKIM that tells receiving servers how to handle mail that fails authentication.

IMAP (Internet Message Access Protocol): A protocol that keeps mail synced across multiple devices by storing messages on the server rather than downloading them permanently to one device.

POP3 (Post Office Protocol 3): An older mail retrieval protocol that typically downloads messages to a single device rather than keeping them synced across several.

SMTP (Simple Mail Transfer Protocol): The protocol used to send outgoing email between mail servers.

CalDAV / CardDAV: Open protocols for syncing calendar events and contacts, respectively, across different applications and devices.

TLS (Transport Layer Security): Encryption applied to a connection in transit, commonly used to secure the link between mail servers as messages are delivered.

OX Guard: An OX App Suite feature adding end-to-end message and attachment encryption using S/MIME and PGP standards.

OX Drive: OX App Suite’s file storage and sharing layer, connected directly to mail and document editing.

Grace Period: The window after a missed renewal payment during which service continues before suspension.