All Collections
Authentication Guides
ATS
Configuring Permissions for Oracle Taleo Enterprise Edition
Configuring Permissions for Oracle Taleo Enterprise Edition

How to configure permissions to authenticate Oracle Taleo Enterprise

Michelle Krameisen avatar
Written by Michelle Krameisen
Updated over a week ago

This guide will outline how to configure your Oracle Taleo account to connect to Merge (or any other API-based integration). Taleo configures their permissions on user level; when creating a user type, it is recommended to duplicate an existing user type that has been validated in the zone already to work properly.

General Linking Instructions

The two items needed will be:

  1. A User (it can be a Service User just for this integration or an Admin from your Organization) with access to Web Services and general ATS Permissions around Candidates, Applications, Interview Stages, Jobs, etc.

    1. Please view this section if you'd like to create a service user or verify permisions

  2. Access to Web Services, and access to the WSDL

    1. Please view this section on how to gather the WSDL. It may involve you reaching out to your Oracle Taleo Reps!

The First Screen will be around inputting your Web Services / Server URL (WSDL)

The Second Screen will be around inputting the Username and Password of either an Admin from your Organization or a Service User

How to Step up Permissions in Taleo

Step 1: Create and approve a new User

  • Create a Taleo User Account activated with Web Service permissions. If you don't have Web Service permissions enabled in your Taleo instance, skip to Enabling Taleo Web Service Framework

Step 2: Define User Type, User Group, and Coverage Area

  • User accounts are defined by system administrators in SmartOrg.

    • (Navigation: Configuration > [SmartOrg] Administration > [Users] User Accounts.) When creating a user account, system administrators define several elements:

      • User Type (Recruiting)

      • User Group (Recruiting Center)

      • Coverage Area (Requisitions and Search)

      • General Preferences (can be modified by users in Taleo Recruiting, in the My Setup feature, to fit personal preferences)

Step 3: Configure access to endpoint fields

  • We’ll need the user to have access to certain endpoints in order to get things up and running:

    Note: This list is a work in progress and does not encompass all the permissions required for all Merge common models supported in the Taleo integration (i.e Applications is not on this list). We'll continue to update this list as we discover the required permissions for each object.

Taleo Export Request

Field Path

Offer

projectedClass: Offer

Application,Number

AcceptedDate

RefusedDate

ExtendDate

ActualStartDate

Status,Number

Status,Description

UserAfterApprovalSuccess,UserNo

Job Interview Stage

projectedClass: ApplicationState

Number

Description

Attachments

projectedClass: Candidate

Number

AttachedFiles,Number

AttachedFiles,FileName

AttachedFiles,AttachmentType,Code

AttachedFiles,FileContent

Requisition

projectedClass: Requisition

Number

ContestNumber

JobInformation,Title

JobInformation,CreationDate

JobInformation,LastModifiedDate

JobInformation,DescriptionExternalHTML

JobInformation,PrimaryLocation,Number

JobInformation,OtherLocations,Location,Number

State,Number

State,Description

Requision,Department,Number

Requisition,HiringManager

Office

projectedClass: WorkLocation

Candidate

projectedClass: Candidate

Candidate,FirstName

Candidate,LastName

Candidate,CreationDate

Candidate,LastModifiedDate

Candidate,InclusiveLastModifiedDate

Candidate,Anonymous

Candidate,NotifyByEmail

Candidate,City

Candidate,HomePhone

Candidate,MobilePhone

Candidate,WorkPhone

Candidate,Number

Candidate,ReferralType

Candidate,CandidateReferrer,Number

Candidate,EmailAddress

Candidate,WebSite

Candidate,Applications,Number

Candidate,Applications,Requisition,ContestNumber

Candidate,Applications,Requisition,Number

Candidate,Applications,ReferralType

Candidate,Applications,ApplicationState,Description

Candidate,Applications,DisqualifierResultDate

Candidate,Applications,LetterSendRegretLetter

Candidate,Applications,DisqualifierResult,Number

Candidate,Applications,DisqualifierResult,Description

Sources

projectedClass: RecruitmentSource

Description

LastModifiedDate

User

projectedClass: User

User,UserNo

User,FirstName

User,LastName

User,CorporateEmail

User,PersonalEmail

User,CorrespondenceEmail

User,UserAccount,AccountCreationDate

Enabling Taleo Web Service Framework

You will need a User Account with "Web Service" permissions to be able to access and use the TaleoAPI. If you do not have this type of account, please contact your System Administrator to request one:

Step 1: Have the Taleo Production Team Enable the Web Service Framework

By default, the web service framework is disabled. The Taleo Production Team will activate it for you upon a proof of purchase. Contact your Customer Representative for further details about pricing and activation.

Step 2: Generate or Obtain the Web Services WSDL Files

To access the Taleo API, you need the Web Service Description Language (WSDL) files corresponding to the Web Services. A WSDL file defines a Web service that is available to you. Your development platform uses this WSDL to generate an API to access the Web service it defines. Each Web service available through the Taleo product is defined by a dedicated WSDL file. You can either obtain the WSDL files from your Customer Representative or you can generate them yourself if you have access to the WSDL download page in the Taleo product user interface.

Did this answer your question?