/

Document

IT Allow-listing Request

Effective Date:

Request for approval

Approve Miira in your Microsoft 365 or Google Workspace tenant

Miira asks your IT team to approve the Miira application in your Microsoft 365 (Entra ID) or Google Workspace tenant. Approval lets your staff sign in with their existing work account and connect their mailbox, so Miira can sync and send their email.

This page sets out what Miira is, what access it requests, why, and how we protect your data.

Entra ID admin consent

Google trusted app

miira.app allow-listed

DNS records added

01 · Product

What Miira is

Miira is a property sales platform built by Miira Technologies Pty Ltd (ACN 688 069 712), Australia. Agencies and developers use it to present, market and sell residential and commercial property from one system.

[ 01 ]

Present

Display suite and appointments.

Appointment notes linked to buyer records.

[ 02 ]

Market

Buyer communication.

Campaigns and email playbooks sent to enquirers and buyers.

[ 03 ]

Sell

Pipeline and reporting.

Lead management and sales reporting for agents, managers and developers.

Miira is a property-focused CRM and operating system for presenting, marketing, selling and leasing real estate. Agencies and developers used globally.

The interface is simple for end users, with a full set of features underneath. Miira can run alongside your existing CRM with bi-directional sync, or replace it entirely. Each person has a single record that combines their contact details and enquiries. That record shows the full history of the person’s interactions with your organisation and its marketing material, in order.

Users can build and send emails, eDMs, SMS, custom datarooms and campaigns, either directly in Miira or through marketing automations. Every send and response is logged against the relevant contact.

Miira connects to CRMs, all major property portals, lead sources and third-party apps, including commercial platforms. It does this through webhooks, email parsing, its API or dedicated integrations.

A Miira MCP server is also available, so your organisation can connect Miira securely to AI assistants such as Claude, Microsoft Copilot and ChatGPT.

02 · Sign-in

Why Miira uses Microsoft and Google sign-in

Miira does not hold passwords. Staff sign in through Microsoft 365 or Google Workspace using OAuth 2.0 and OpenID Connect. We made this choice for two reasons.

[ 01 ]

Access stays under your control

Your identity provider decides who gets in. MFA, conditional access and device policies apply to Miira automatically. Disable an account and its Miira access ends with it.

[ 02 ]

Email goes out from your own domain

Buyer and campaign email is sent through the user’s own mailbox, so it comes from your domain, passes your SPF, DKIM and DMARC, and sits in their Sent folder.

The result is fewer credentials in circulation and no separate login for a malicious actor to target.

03 · Setup

What we are asking you to do

Approve Miira in whichever platform your organisation uses, then add the DNS records for Miira’s sending domain. Many tenants block users from consenting to third-party apps, which stops sign-in until an admin approves.

Microsoft 365 (Entra ID)

[ 01 ]

Find Miira in Enterprise applications

In the Entra admin centre, open Enterprise applications and search by Application (client) ID:

03586caa-e170-424a-8aee-3a50874b7c58

[ 02 ]

Grant admin consent

Grant tenant-wide admin consent for the permissions listed in section 04.

[ 03 ]

Assign users (optional)

Assign the app to the users or group who will use Miira.

Google Workspace

[ 01 ]

Open API controls

Admin console › Security › Access and data control › API controls › Manage third-party app access.

[ 02 ]

Add Miira

Add Miira by its OAuth client request.

iOS:

192708642435-1ju7g9gsoef87vue1ecmmfl150vrfc1g.apps.googleusercontent.com

Web:

192708642435-lvr8hb928uvp42jsf3j8f4bncgbantoq.apps.googleusercontent.com

[ 03 ]

Mark as Trusted

Set access to Trusted for the organisational units that will use Miira.

Sending domain

[ 01 ]

We set up a sending domain

Miira sets up a sending domain for your organisation: a subdomain of your own domain, such as mail.yourdomain.com.au.

[ 02 ]

We send you the DNS records

After sign-up, we provide your IT team with the DNS records for that domain.

[ 03 ]

Add the records

Add them at your DNS provider. Campaign email can only send from the subdomain once the records verify.

Email delivery

If your mail gateway filters outbound or inbound mail, allow-list this domain so system notifications reach staff.

miira.app

04 · Permissions

Permissions requested

Miira requests the access needed to sign the user in, sync their email and calendar to buyer records, and send email on their behalf. It does not request access to files or drives.

Purpose

Microsoft Graph

Google

Why

Sign-in

openid, profile, email

openid, profile, email

Confirms identity and work email address

Profile

User.Read

—

Reads the user’s name and email

Read email

Mail.Read (delegated)

gmail.readonly

Syncs correspondence to buyer records and tracks replies

Send email

Mail.Send (delegated)

gmail.send

Sends buyer and campaign email from the user’s mailbox

Calendar

Calendars.ReadWrite

calendar.events

Syncs appointments and availability

Stay signed in

offline_access

Offline access

Keeps sync and sending working without repeated logins

All permissions are delegated, so Miira acts only as the signed-in user. Mailbox data is used only to provide Miira’s features. It is never sold, used for advertising or used to train AI models, and Google data is handled under Google’s Limited Use requirements.

05 · Security

Security controls
  • No passwords stored. Authentication is handled entirely by Microsoft or Google.

  • Encrypted tokens. OAuth tokens are encrypted at rest and in transit (TLS 1.2 or higher).

  • Tenant separation. Each client organisation’s data is logically separated from every other.

  • Role-based access. Agents, managers and administrators see only what their role allows.

  • Instant revocation. Revoking consent in Entra ID or Google Workspace cuts Miira’s access immediately.

  • Australian hosting. Customer Data is stored in Sydney, Australia. Some delivery providers, such as email and SMS, process outside Australia under APP 8 safeguards.

  • Independent assessment. Miira maintains the independent security assessments Google and Microsoft require for mailbox access.

06 · Compliance

Data protection and compliance

Miira is built to meet the privacy and data protection obligations of the markets our clients operate in. Customer Data is stored in Australia and clients retain ownership of their data. Any provider that processes data overseas is listed in Schedule 7 of the Miira Terms of Service.

Framework

Jurisdiction

How Miira addresses it

Privacy Act 1988 and Australian Privacy Principles

Australia

Personal information handled under the APPs; Customer Data stored in Australia; overseas providers bound under APP 8

GDPR

EU and UK

Practices designed to align with GDPR principles; data processing addendum available on request

CCPA / CPRA

California, US

Practices designed to align with CCPA principles; no sale of personal information

ISO/IEC 27001

International

Information security controls modelled on the standard. (Pending Certification).

07 · Contacts

Contacts

[ 01 ]

Technical

Will Truscott

will@miira.app

[ 02 ]

Commercial

Alex Livermore

alex@miira.app

[ 03 ]

Support

Miira Support

support@miira.app

Thank you for helping get your team onto Miira. Any questions, please don’t hesitate to reach out to myself, Will or our broader team.

Alex Livermore · Co-Founder of Miira


Next step

See it on one of your own projects.

We load a demo project from your plans. It’s free, and it starts no term.