Access and control
Use this if you are signing off on more than one system, or if someone else did the setup and you want to see what was granted. For the steps themselves, go to the guide for your system.
Who you are granting access to
AgentFront is operated by Parallel International Pty Ltd, an Australian company. That is the name Microsoft's consent screen shows as the verified publisher.
Both of our domains are in use: the product and this documentation are at agentfront.com.au, and our support address is on agentfront.au.
How access works
Only what the assistant uses. Every permission maps to something the assistant does, and each guide sets out which, permission by permission.
Read-only where the work allows it. realestate.com.au is read-only. Email is written to, and that guide lists every write.
Access follows each person's own sign-in. On both Microsoft and Google, your administrator approval permits AgentFront to ask. Access to a mailbox exists once that person has signed in themselves.
Nothing is granted with a password. No email or realestate.com.au credential is given to AgentFront. Those flows run on the provider's own pages.
Email: Microsoft 365 and Google Workspace
An agency uses one or the other. Full detail: Microsoft 365 · Google Workspace.
| Microsoft 365 | Google Workspace | |
|---|---|---|
| Mechanism | Microsoft Graph, delegated OAuth permissions | Google OAuth, allowed in the Admin console |
| Administrator grants | Admin consent for the organisation | App access control set to Trusted |
| Per-user step | Each staff member signs in with Microsoft | Each staff member links their own Gmail |
| Mail access | Read, draft, send, mark read, categorise, move | Read, label, mark read, move, send |
| Calendar access | Read and write, the user's own calendars | Read and write, the user's own primary calendar |
| Deletes mail? | No | No |
What neither one touches. No SharePoint, OneDrive, Teams, Files or Sites. No Google Drive, Docs, Contacts/People or Tasks. No directory enumeration on either platform, so AgentFront cannot list your users, groups or organisational units.
Sending. Replies are prepared for a member of the agency's team to review and send from the AgentFront queue.
realestate.com.au
Full detail: realestate.com.au.
Mechanism. AgentFront is a registered REA integration partner and reads REA's API using its own partner credentials. The agency supplies nothing: no password, no key, no identifier.
Read-only. AgentFront reads your listings and cannot change them. It cannot create, edit, withdraw or relist a property, respond to a lead, or change a campaign.
Data used. Listing Export. Campaign Reporting and Leads are optional, and Listing Publication is not requested.
Who can authorise what
| System | Who authorises | Where | Needs an AgentFront account? |
|---|---|---|---|
| Microsoft 365 | An administrator who can grant admin consent | Microsoft's consent page | No |
| Google Workspace | Super administrator | Google Admin console | No |
| realestate.com.au | REA Ignite administrator | REA Ignite | No, but an AgentFront agency admin runs verification |
After access is revoked
| You do this | Effect |
|---|---|
| Remove AgentFront in Entra ID | Mail and calendar access stops for the whole organisation |
| Revoke one user's tokens in Entra ID | That person only |
| Block or remove the app in Google Admin | Gmail and Calendar access stops |
| A user revokes AgentFront in their own Google Account | That person only |
| Remove the integration in REA Ignite | Listing syncing stops, usually within about five minutes |
In every case, records AgentFront already created stay where they are. Drafts and sent mail remain in the mailbox, and calendar entries remain.
Access is always withdrawn in your own system (Entra ID, the Google Admin console or REA Ignite), which is where it was granted. The connection cards inside AgentFront are read-only status displays.