Workspace integrations
Live todayGoogle Workspace for therapy centers, tied to the employee record
Provision, suspend, reactivate, and offboard employee accounts from TargetFlo's directory. Org units follow role and location. Microsoft 365 / Entra ID is next on the roadmap.
- New RBT · RaleighProvisioned
- BCBA · CharlotteOrg unit: Clinical/CLT
- Front office · DurhamSuspended — leave
- BT · RaleighOffboarded 08/29
What is the TargetFlo Workspace integration?
The TargetFlo Workspace integration connects the employee directory to your identity platform so that hiring, leave, and termination drive the account lifecycle automatically. Google Workspace is live: TargetFlo provisions accounts, assigns org units by role and location, suspends on leave, and offboards with license release. Microsoft 365 / Entra ID brings the same lifecycle to Microsoft-first organizations and is on the roadmap. Every action is written to the same audit trail described on the Security page.
Employee lifecycle
Hired → provisioned → role & org unit → suspended → offboarded
Five states, one record. The directory, the audit trail, and Workspace never disagree about who has access.
- 01
Hired
The employee record is created in the TargetFlo directory with role, location, and start date. Onboarding tasks and required courses are assigned.
- 02
Provisioned
A Google Workspace account is created from the record — name, primary email, and recovery details — without opening the Admin console.
- 03
Role & org unit
The account is placed in the org unit that matches role and location, so Drive sharing, Calendar, and group policies apply on day one.
- 04
Suspended on leave
Extended leave or an investigation suspends the account in one click. Mail is preserved; sign-in is blocked; the record shows why.
- 05
Offboarded
Termination triggers suspension, optional data transfer, and license release. The directory, the audit trail, and Workspace agree on the date.
Google Workspace
Live todayOnboard an RBT without opening the Admin console
Multi-location ABA providers hire constantly. Each new RBT or BCBA used to mean a ticket, a manual account, and a guess at the right org unit. TargetFlo creates the account from the approved employee record and places it correctly the first time.
- Provision accounts with organization-defined email formats
- Assign org units by role (RBT, BCBA, front office, leadership) and location
- Suspend on leave and reactivate on return, with the reason recorded
- Offboard with suspension and license release tied to the termination date
- New RBT · RaleighProvisioned
- BCBA · CharlotteOrg unit: Clinical/CLT
- Front office · DurhamSuspended — leave
- BT · RaleighOffboarded 08/29
Capabilities
What the Google Workspace integration does
Provision from the record
Create the Workspace account when the employee record is approved. Email format and org unit follow organization rules.
Suspend & reactivate
Leave, investigation, or a late background check: suspend in one action, reactivate when cleared, with the reason logged.
Org unit assignment
Map roles (RBT, BCBA, front office, leadership) and locations to org units so policy and sharing are correct automatically.
Email lifecycle
Primary address, aliases, and group memberships follow onboarding and offboarding instead of living in a ticket queue.
Offboard cleanly
Suspend, transfer ownership where configured, and release the license — recorded against the employee record.
Every action audited
Who provisioned, suspended, or offboarded, and when. The audit trail is the same one that covers PHI access.
Microsoft 365 / Entra ID
Coming soonThe same lifecycle for Microsoft-first organizations
Centers standardized on Microsoft 365 need the same thing: accounts that appear when someone is hired and disappear when they leave, with group and license assignment driven by role. TargetFlo is building the Entra ID integration on the same lifecycle model as Google Workspace.
- Provision Entra ID users from the employee record
- Assign groups and licenses by role and location
- Suspend on leave; disable and release licenses on offboarding
- Same audit trail and same directory as the Google integration
- Hired → Entra ID user created
- Role → security group + license
- Leave → sign-in blocked
- Termination → disabled, license released
Join the waitlist and we will contact you before rollout to validate the mapping against your tenant.
Least privilege
What TargetFlo asks your Workspace admin for
Account lifecycle needs specific scopes. Reading employee mail or files is not one of them.
| Scope | Requirement | Used for |
|---|---|---|
| Create, suspend, reactivate, delete users | Required | Account lifecycle from the employee record |
| Read and assign organizational units | Required | Role- and location-based org unit placement |
| Manage group membership | Optional | Add to location or role distribution groups on hire |
| Read license assignments | Optional | Release licenses on offboarding and report seat usage |
| Read mailbox or Drive contents | Not requested | TargetFlo does not read employee email or files |
Credentials are stored per organization, scoped to the connected tenant, and can be revoked from either side at any time. Revoking the connection stops lifecycle automation; it does not delete or modify any Workspace account.
FAQ
Workspace integration FAQs
Provision your next hire from the employee record
Book a demo. We connect a test Workspace tenant, map one location's org units, and walk an employee through hired → provisioned → offboarded.