Overview
The user-detail-request and user-detail-response integration points are used when a buying organization wishes use an external system such as an Active Directory or their ERP system as the master source of user information. During the login process a user-detail-request is sent from Unimarket to the external system. This contains the details of the person attempting to login. The external system then responds with the user-detail-response which provides Unimarket with the valid user details. Access to Unimarket will then be granted/denied based on the details provided from the external system.
| Note: If this integration is enabled the external system is the master for all user information. Each time the user-detail-response message provides Unimarket with user details these will replace anything previously held for that user inside Unimarket. |
This integration allows an organization to centrally manage their user information within an Active Directory (or similar) and have this information updated into Unimarket. It removes the need to manage users inside Unimarket.
Setting up User Details Integration
If you want to use a central repository to manage user details such as an Active Directory then you will need to store some specific information about the Unimarket user so it can be passed to Unimarket within the user-detail-response. Below is a list of the values that need to be stored.
Unimarket User Roles
| Role | Integration Syntax | Definition |
|
Approval Administrator |
COMMUNITY_APPROVALS |
View and manage community approval information and configurations. |
|
Bid Request |
COMMUNITY_RFX_CREATE |
Initiate bidding events (RFQ, RFP, RFI) through the sourcing module. |
|
Bid Request Collaboration |
COMMUNITY_RFX_COLLABORATION_CREATE |
Gives users with the Bid Requests role the ability to select collaborators when creating a bid request. |
|
Browser |
COMMUNITY_BROWSER |
Shop the marketplace and create incomplete requisitions to reassign to Buyers within their org unit. The Browser role can not be used with the Buyer Role. |
|
Buyer |
COMMUNITY_BUYER |
Shop the marketplace, create requisitions and complete reassigned requisitions from users with the Browser role. |
|
Community Administrator |
COMMUNITY_ADMIN |
Full community administration rights. |
|
Community Features |
COMMUNITY_FEATURES |
Manage administrator functions that relate to the community features, such as general community preferences, ordering and checkout preferences and invoice matching preferences. |
|
Community Management |
COMMUNITY_MANAGEMENT |
Manage administrator functions that relate to the community setup and master data. |
|
Community Profile |
COMMUNITY_PROFILE |
Manage administrator functions that relate to the community profile, such as community name, branding, welcome text, links, community email addresses and more. |
|
Community Supplier Administrator |
COMMUNITY_SUPPLIER_ADMIN |
Manage supplier information, categories, invitations and connections. |
|
Contracts Administrator |
CONTRACTS_ADMIN |
Allows users to make changes and edit a contract as if they were the owner of the contract without being a member of the contract. Allows users to able to access the Documents and Transactions tabs without being a member. |
|
Create Blanket Order |
COMMUNITY_BLANKET_ORDER_CREATE |
Create Blanket Orders for suppliers. |
|
Create Contracts |
COMMUNITY_CONTRACTS_CREATE |
Ability to Create contracts and link or unlink transactions (reqs and orders) to a contract. |
|
Create Buyer Invoices |
COMMUNITY_INVOICE_BUYER_CREATE |
If community PO Flip is enabled, a user with the Create Buyer Invoices role can use the 'Invoice Order' feature to create invoices for any of their own orders already in Unimarket. If Retrofit Invoices are enabled a user with this role will also be able to create invoices for orders that are not yet in Unimarket for buyer approval. |
|
Create Invoices |
COMMUNITY_INVOICE_CREATE |
If community PO Flip is enabled, a user with the Create Invoices role can use the 'Invoice Order' feature to create invoices for orders already in Unimarket. If Retrofit Invoices are enabled a user with this role will also be able to create invoices for orders that are not yet in Unimarket for buyer approval. Users can also force match invoices. |
|
Escalate Approval |
COMMUNITY_APPROVAL_ESCALATE |
Escalate approvals for viewable requisitions.(Community Administration role also gives this ability) |
|
Expenses |
COMMUNITY_EXPENSES |
Create expense claims. |
|
On Behalf Of |
COMMUNITY_ON_BEHALF_OF_BUYER |
Create requisitions on behalf of any other user in the community. |
|
On Behalf Of Expenses |
COMMUNITY_EXPENSES_OBO |
Create expense claims on behalf of other users. |
|
On Behalf of Receiving |
COMMUNITY_ON_BEHALF_OF_RECEIVING |
Receive orders on behalf of other users. User will see full community open receiving. Ideal for Central Receiving staff. |
|
Over Receiving |
COMMUNITY_OVER_RECEIVING |
Allows users to receive more than the ordered quantity. |
|
RFQ |
COMMUNITY_RFQ_CREATE |
Initiate simple RFQs with suppliers. |
|
Supplier Request Admin |
COMMUNITY_SUPPLIER_REQUEST_ADMIN |
Manage new supplier requests from end users. The requests can be turned into invitations if the supplier is not currently in the marketplace. |
|
User Administrator |
COMMUNITY_USER_ADMIN |
Manage community users including user details and roles. The User Administrator role cannot allocate a user the Community Administrator role. |
|
User Support |
COMMUNITY_USER_SUPPORT |
Allows User to Switch into other users to assist with support. Not able to make changes while switched into other users. |
|
View Contracts |
COMMUNITY_CONTRACTS_VIEW |
View any existing contract leadsheets entered for your community. User must be a member of a contract to view the contract documents. |
|
View Tax Profiles |
COMMUNITY_TAX_PROFILE_VIEW |
View Tax Profiles (W9/W8BEN forms) submitted by suppliers. |
|
View Transactions |
COMMUNITY_TRANSACTION_VIEW |
View all transactions for the entire community. Users with this role can view any purchase throughout the entire community. Without this role, users may only see transactions they are involved in. |
Technical Information
For technical documentation and examples relating to the full list of Unimarket webservice interfaces see: