Profiles
Keep every profile current.
Bios, links, categories and contact fields consistent across every account rather than whatever each owner last typed — and verification applications prepared, filed and kept current.
Back Office · Social account administration
Apply your IT access rules to social accounts.
Extend your identity and access reviews to the social accounts your business relies on. Compare people and roles, apply your approval rules, then record each authorised change.
Your team sets the policy and approves the work. handles holds no passwords or recovery secrets.
Policy alignment
Apply your rules to social access.
The same owner, approval and review standards can follow a social account change.
Identity context
See the people behind every role.
Compare approved directory and HR context with observed social permissions.
Control evidence
Keep the decision and the change.
An approving owner and a dated account record make the work reviewable.
Every change, accounted for.
Aurora Collective- Change: Contact fieldsAccount: @auroraBefore: a personal addressAfter: a group mailboxBy: handlesWhen: 06 Apr
- Change: Admin removedAccount: Aurora GlobalBefore: Priya Raman · AdminAfter: no accessBy: handlesWhen: 08 Apr
- Change: Advertiser seat removedAccount: Aurora Ads · EMEABefore: Tomas Bergh · AdvertiserAfter: no accessBy: handlesWhen: 08 Apr
- Change: Two-factorAccount: @auroracareersBefore: not enrolledAfter: enrolledBy: Devan MehtaWhen: 09 Apr
- Change: Recovery routeAccount: @auroracollectiveBefore: a personal handsetAfter: a number the company ownsBy: handlesWhen: 13 Apr
- Change: Partner access re-scopedAccount: Aurora GlobalBefore: AdminAfter: the assets in the contractBy: Devan MehtaWhen: 15 Apr
- Change: Verification applicationAccount: @aurora.gulfBefore: not filedAfter: filedBy: handlesWhen: 17 Apr
- Change: Handover recordedAccount: @aurorahome.jpBefore: agency-heldAfter: Kaido KK · JapanBy: handlesWhen: 22 Apr
Identity and access review
Compare social roles with your people records.
Bring approved directory and HR context into the same review as social roles. Agree the lifecycle signals and matching rules with your IT team, then give each exception an owner and an approved route to resolution.
Your IT baseline
Identity & people
Microsoft Entra ID
Google Workspace- Okta Identity
Identity, employment status and team context from sources you approve.
Pulse reconciliation
Compare the records
- Match people to observed platform roles
- Surface leavers, movers and unmatched access
- Review against your approved policy
Social estate
Control the next action
Route approved access changes through each platform’s supported process and keep the decision and outcome on record.
Connection method, available fields and refresh cadence are agreed for each source during setup. A directory change prompts a social access review; it does not itself revoke a platform role.
How a request gets done
Give each access change an owner and a record.
One policy-aligned route from identity signal or platform request to an approved, recorded action.
Request
Bring the signal in.
Directory changes, access reviews and platform tasks enter one queue.
Approve
Approve the change.
Your owner checks the request against IT policy and authorises the action.
Change
Make the update.
An appointed admin acts, or your team uses the prepared work.
Record
Keep the record.
Account, actor, date and next action stay visible.
Platform decisions stay on the queue with a named owner; we do not promise an outcome the platform controls.
What changes
Give each loose end an owner and a next action.
Each account task gets a route, an approver and a recorded next step.
Someone leaves
Without an ownerThe laptop comes back. The admin role does not.
With Back OfficeSocial roles checked against the leavers list and removed from the accounts they still touch.
An agency is replaced
Without an ownerOld seats stay open to avoid disrupting a live campaign.
With Back OfficeOutgoing access closes as the incoming team’s access opens.
A recovery route goes stale
Without an ownerThe reset still points to someone’s personal phone.
With Back OfficeRecovery is moved to a mailbox and number the company owns.
A platform case stalls
Without an ownerThe reference sits unanswered in an inbox.
With Back OfficeA named owner tracks the response through the platform’s own route.
Where we help
Keep account details and access up to date.
The queue covers routine changes across accounts, people and platform cases. Content and campaigns stay with your team.
Joiners and leavers
Give access. Remove it.
Access granted the day someone needs it and revoked the day they don’t, agencies and freelancers included. Pulse shows you who holds what; this is the work of changing it.
Credentials
Put recovery in company hands.
Two-factor enrolled on every account, recovery pointed at a mailbox and a number the company owns rather than whoever set the account up, and a way back in that isn’t one person’s phone — including on the accounts nobody has logged into this year.
Housekeeping
Keep the register true.
Duplicate and legacy accounts consolidated or closed, renewals diarised before they lapse, bio links and redirects kept alive, and the register kept true as all of it changes.
Handovers
Move control without loose ends.
A campaign ends, an agency is replaced, a market takes over its own account. Access, ownership and the record all move together, so nothing is left behind in somebody’s inbox.
The queue
Give each case a next action.
The platform forms, appeals and support threads nobody has time to sit on — filed properly the first time and chased until someone answers, which is usually the whole difference.
Back Office scenarios
What an owned estate should keep on record.
Scattered requests become one owned queue with a visible next action.
Standing operations queue
Every request has an owner and a next action.
The desk connects incoming administration to the dependency, action and accountable person needed to close it.
RequestAccountDependencyNext actionOwner
Leaver accessAurora GlobalDirectory match confirmedRemove inherited roleshandles.ai
Verification application@aurora.gulfAuthorised signatory returnedFile complete packhandles.ai
Agency handoverAurora Home · JapanIncoming owner namedClose old access routeKaido KK
Desk stateNothing is ownerless. Nothing disappears into an inbox.Open work, dependencies and completed changes remain on one record.3 / 3 requests owned
Aurora Collective, Northstar Agency and Kaido KK are fictional. Example records only.
Where it starts
Three sources. One owned queue.
Requests keep arriving after an audit ends. We give each one a place to land.
From your own team
- Joiners and leavers
- Agency handovers
- New market accounts
From the platforms
- Verification requests
- Appeals and support threads
- Forms needing a response
From the diary
- Renewals before they lapse
- Two-factor checks on quiet accounts
- Register and redirect updates
Account administration only. We do not post, write, schedule or run campaigns.
The queue
Prepare the evidence before you file.
A platform case needs the right documents, a named owner and follow-up after submission. Back Office keeps those steps in the same queue.
The pack
Build a pack your team can use again
Before anything can be submitted at scale, somebody has to assemble the file that will be asked for, get it reviewed, and keep it somewhere it can be used again.
- Who the rights owner is, per mark
- The jurisdiction each claim is brought in
- Trademark registration numbers
- The supporting documentation for each right
- A signed authorisation to act
Keep the reviewed documents together so the next appropriate filing starts from a known record.
The chase
Filed, acknowledged, chased, answered
Some platform routes require manual submission. We keep the reference, acknowledgement, next date and response together, with a named owner following up until the platform answers.
What we hold
None of this needs us to hold a password.
We use the access needed for an approved task and keep the decision and change on record. Your team keeps control of identity and recovery.
Read to see it. A named administrator to change it.
The platform surfaces need read permissions and that does not change. Administration is different by definition: where a change is ours to make, we make it as a named administrator you appoint on your own accounts, at the level the task needs. Where it isn’t, we prepare it and your own admins execute.
Your directory sets the people baseline.
Bring approved identity and HR context into the access review. Agree the source, matching rules and lifecycle signals during setup, then compare them with the social roles each connected platform exposes.
handles does not manage passwords.
Identity is your directory’s job, not ours. There is no password, no recovery secret and no credential store on this engagement, and nothing to ask us to delete at the end of it.
Two-factor is a state we check, not a secret we keep.
Every account is checked for enrollment, including the ones nobody has logged into this year. What goes on the record is whether it is on.
A recovery route the company owns.
Recovery pointed at a mailbox and a number the company controls rather than whoever happened to set the account up, so a leaver doesn’t walk out with the reset link.
Asked for by link, not by thread.
A shareable request that asks for the access a job needs and exports as a document, so what was asked for and what was granted are both on the record rather than in somebody’s inbox.
Escalation
Move a wider risk into the right review.
An access request may reveal a former administrator who still appears to have a role. We record the finding and route it for the right review.
Access
An access request that surfaces an admin nobody recognises, or a seat that outlived the contract it was granted under. One request is a task; a pattern is a finding.
Goes toAuditing
Identity
A profile that turns out not to be yours — an account trading on your name that nobody on your side has ever administered.
Goes toRadar
Coverage
A name the estate needs and does not hold, surfaced by a market asking to run an account that does not exist yet.
Goes toAcquire
Rights
An appeal that cannot be argued, because the mark behind it was never registered or never lodged.
Goes toTrademarking
Domains
A bio link pointing at a domain about to lapse, or one already parked by somebody else.
Goes toDomains
If review finds no wider issue, the original task stays in the queue for completion.
How it runs
You’re left with a record, and someone to ask.
The first pass checks profiles, two-factor enrolment, recovery routes and access against the agreed baseline. After that, new requests and platform cases enter a standing queue with a clear record.
- A named owner for the queue, so there is someone to ask rather than a rota nobody wants.
- Every contract carries a named client-management contact and a channel for platform queries, answered in business hours.
- A log of every change: what was altered, on which account, by whom, and when.
- The log records changes you authorise us to make and changes your own administrators make, with the actor named for each one.
- Escalation when a small task turns out to be a real problem — an access request that surfaces an admin who left two years ago belongs in an audit, not an inbox.
- No promise about an outcome a platform decides. Applications are prepared, filed and kept current; whether one is granted is not ours to commit to.
Who holds what
Pulse surfaces the access. Back Office carries out the approved change.
Pulse compares the people and roles exposed by your connected business managers with approved identity context. A leaver still holding an admin role becomes a reviewable finding; Back Office helps carry the approved change through.
Send us the queue — we’ll tell you what we’d take off it.
Bring the open tasks, the accounts involved and an approving owner. We’ll agree the route for each request.