When a record is created or updated in Adapt, the Owning Consultant is passed to the Owner field of the corresponding record in TempBuddy . Similarly, if a record is updated or created in TempBuddy the 'Recruiter' or Owner is passed to the Owning Consultant field of the corresponding record in Adapt.

The following records have ownership synchronisation between the 2 systems:

  • Candidates
  • Clients
  • Contacts
  • Jobs
  • Assignment
  • Timesheets

An ID field exists on the Employee record in Adapt. The value held here should match the value in the External Ref field on the 'Recruiter' record in TempBuddy to ensure the synchronisation happens.

Use the Adapt Manager profile in Adapt and the Administrator Role in TempBuddy, to set these fields:

Syncing Recruiter Ownership on Candidate Creation in Adapt

When any Temporary Candidates are created and made Active in Adapt, the Owning Consultant will be mapped across to the Owner field in the corresponding Candidate record in TempBuddy:

Note: Please see details on Candidate administration between TempBuddy and Adapt here to understand when the Candidate is created in TempBuddy:

Updating Candidate Recruiter Ownership in Adapt on single records

The owning Consultant of a Temporary Candidate is updated in Adapt by running the activity Consultant in the General section of the Activities menu on a Candidate record.
Change the Temp Consultant and click Confirm:

This will trigger the update of the corresponding Candidate record in TempBuddy.

If the corresponding Owner cannot be found in TempBuddy, the field will be left as is.

Updating Candidate Recruiter Ownership in Adapt on multiple records

Using the Batch action Change Owning Consultant from a set of Saved Results, Adapt Manager Profile users can change the Owning Consultant of Temp Candidates.

This will trigger the update of the corresponding Candidate records in TempBuddy

Remember, only Adapt Managers can run this activity in batch.

Updating Candidate Recruiter Ownership in TempBuddy

The Owner of a Candidate record in TempBuddy is updated by editing and saving the Owner field:
Change the Owner and save:

This will trigger the update of the Temp Owning Consultant field in the corresponding Candidate record in Adapt..

Note: Adapt will look at the hierarchy of the Owning Consultant to populate the Team, Office and Region. If changes are made to the Owning Consultant, a journal record will be created in Adapt.

Note: If the Candidate has multiple roles, i.e. Temporary, Permanent and Contract in Adapt, ONLY the Temporary Candidate will be updated.

If the corresponding Owning Consultant cannot be found in Adapt, the field will be left as is.

Syncing Recruiter Ownership on Client Creation in Adapt 

The Client works in the same way as the Candidate. When a Client (and linked Contact) is created in Adapt (and made Active), the owning Temp Consultant will be mapped across to the Owner field in the corresponding record in TempBuddy.

Note: Please see details on Client administration between TempBuddy and Adapt here to understand when the Client is created in TempBuddy:

Updating Client Recruiter Ownership in Adapt

The owning Consultant of a Client is updated in Adapt by running the activity Consultant in the General section of the Activities menu on a Client record.
Change the Temp Consultant and click Confirm:

This will trigger the update of the Owner field in the corresponding Client record in TempBuddy.

If the corresponding Owner cannot be found in TempBuddy, the field will be left as is.

Recruiter Ownership on Contact in Adapt and TempBuddy

If a Contact is created or added in Adapt, the Owning Consultant is held on the Adapt Contact record, but is NOT mapped across or updated on the corresponding Contact record in TempBuddy. This is because ownership is not held at Contact level in TempBuddy, only on the associated Client record.

Updating Client Recruiter Ownership in TempBuddy

The Owner of a Client record in Tempbuddy is updated by editing and saving the Owner field:
Change the Owner and save:

This will trigger the update of the Temp owning Consultant field in the corresponding Client record in Adapt and any linked Contact records.

Note: Adapt will look at the hierarchy of the Owning Consultant to populate the Team, Office and Region. If changes are made to the Owning Consultant, a journal record will be created in Adapt.

If the corresponding Owning Consultant cannot be found in Adapt, the field will be left as is.

Ownership of Additional Contacts added in Tempbuddy

If additional Contacts are created on the TempBuddy Client record, these Contacts will be created in Adapt and the owning Temp Consultant will be set using the Recruiter Owner of the associated Tempbuddy Client:

Note: TempBuddy Contacts do not have a Recruiter Owner. This is only held on the associated Client record.

Updating Contact Recruiter Ownership in Tempbuddy

As Owner is not held on a Contact record in TempBuddy, a Contact Recruiter Owner cannot be updated.

Syncing Recruiter Owner on Job Creation in TempBuddy

When a Job is created in TempBuddy, the Owner will be mapped across to the Temp owning Consultant field in the corresponding record in Adapt.

Note: Please see details on Temporary Job administration between TempBuddy and Adapt here to understand when the Job is created in Adapt:


Note: Adapt will look at the hierarchy of the owning Consultant to populate the Team, Office and Region of the record.

Updating Job Recruiter Ownership in Tempbuddy

The Owner of a Job record in TempBuddy is updated by editing and saving the Owner field:
Change the Owner and save:

This will trigger the update of the Temp owning Consultant field in the corresponding Job record in Adapt.

Note: Adapt will look at the hierarchy of the owning Consultant to populate the Team, Office and Region. If changes are made to the owning Consultant, a journal record will created in Adapt.

If the corresponding owning Consultant cannot be found in Adapt, the field will be left as is.

Syncing Recruiter Owner on Assignment Creation in Tempbuddy

The Recruiter Owner of the Assignment in TempBuddy is inherited from the corresponding Job record. This Owner will be mapped to the Temp owning Consultant field of the corresponding Adapt Assignment record when an Assignment record is created in TempBuddy:

Subsequently, any Timesheets created from Assignments in TempBuddy will inherit the TempBuddy Assignment Recruiter Owner:

Note: Please see details on Temporary Assignment administration between TempBuddy and Adapt here to understand when Assignment records are created in Adapt:


Adapt will look at the hierarchy of the owning Consultant to populate the Team, Office and Region. 

Updating Assignment Recruiter Owner in Tempbuddy

The Owner of an Assignment record in Tempbuddy is updated by editing and saving the Owner field:
Change the Owner and save:

This will trigger the update of the Temp owning Consultant field in the corresponding Assignment record in Adapt 

Note: Adapt will look at the hierarchy of the Owning Consultant to populate the Team, Office and Region. If changes are made to the Owning Consultant, a journal record will be created in Adapt.

If the corresponding Owning Consultant cannot be found in Adapt, the field will be left as is.

Syncing Recruiter Owner on Timesheet Creation in Tempbuddy

The Recruiter Owner of a Timesheet in TempBuddy is inherited from its corresponding Assignment record when created.
This Owner will in turn be held as the Temp owning Consultant of the corresponding Adapt Timesheet record when created.

Note: The corresponding Adapt timesheet will be created when when the following actions are completed successfully in Tempbuddy:

  • Generate New Timesheet
  • Approve Timesheet
  • Generate New Invoice
  • Generate New Payslip

Please see details on Timesheet administration between TempBuddy and Adapt here:


Note: Adapt will look at the hierarchy of the Owning Consultant to populate the Office. 

On Behalf Of fields in Adapt

Records created in Adapt from TempBuddy have the On Behalf Of user set to be the same as the Owner field of the corresponding record in TempBuddy.


Did this answer your question?