Describing Concur Request Administration Tools and Roles

In this unit, you will learn about the different administration tools available in Concur Request as well as what permissions must be assigned for users to utilize those tools.

After completing this unit, you will be able to:

• Explain the different administration tools available in Concur Request.
• Describe the permissions required to use each of the administration tools.

The previous unit was a high-level look at the configuration tools used in Concur Request and future units will go much deeper into those tools. Beyond the configuration tools, there are a number of other administration tools that you will use on a regular basis. Each tool requires a specific permission to be assigned to the user's profile through the Permission Administrator tool.

Request Processor

This tool is the Concur Request version of the Expense Processor and Invoice Processor. It is used for administrators who need to approve requests during the approval process and acts as a method for users to see all requests in one place.

This tool is group aware, so access can be restricted by how the tool is assigned.

Required Permissions: (only one of these permissions can be assigned to a user)

• Request Administrator: Users with this permission can view, edit (depending on the configuration), and approve requests.

• Request Auditor: This permission provides read-only access to the Request Processor tool. This permission can be assigned to TMCs, customer internal travel agents, or any other user that needs read-only access to requests.

• TMC Agent: This permission is assigned to a representative of a TMC or a customers own internal travel agents. In some regions, it is appropriate for the TMC Agent to access the request after submission but prior to manager approval. This allows the TMC Agent to add or edit segment amounts, ensuring accuracy for the request approver.

Note

Unlike Concur Expense and Concur Invoice, there is no Processor Manager functionality in Concur Request.

Request Proxy

Just like in Concur Expense and Concur Invoice, the proxy tool allows a user to access another user's requests. A proxy can create, modify, and submit requests on behalf of another user. However, users with this role cannot approve requests on behalf of another user.

The proxy tool is most commonly used to support users and troubleshoot issues they might be having.

This tool is group aware, so access can be restricted by how the tool is assigned.

Required Permissions: Request Proxy Logon

Event Request

Some customers may have situations where many users travel to the same event on a regular basis, such as a conference or training. If the company falls into this category, you may want to use the Event Request functionality within Concur Request.

This feature allows users with the Request Event Manager permission to create an Event Request and add the names of the participants to it as attendees. Once submitted, each attendee will receive an instance of the request where they can add their details. This allows for the costs of each request, as well as the costs for the entire event to be tracked.

Required Permission: Request Event Manager

User Administration

This tool is used to create and modify user profiles within the system. It is one of the main administrator tools and is used by administrators for Concur Request, Concur Expense, Concur Invoice, and Concur Travel.

User profiles can also be created and modified with file imports, APIs, and some third-party integrations.

User profiles cannot be deleted.

This tool is group aware, so access can be restricted by how the tool is assigned.

Required Permissions: (only one of these permissions can be assigned to a user)

• Employee Administrator: This is the main permission used to grant access to this tool. It allows for the creation and modification of user profiles.
• Employee Administrator (read-only): This permission provides read-only access to user profiles. It is often assigned to auditors and other users who need to see user profiles, but not change them.
• Employee Maintenance: This permission gives the user the ability to modify existing users but not create new users.

Permission Administrator

This tool allows users to assign and revoke permissions to other users.

Many permissions can also be assigned by a file import, APIs, or third part integrations.

This tool is group aware, so access can be restricted by how the tool is assigned.

Required Permissions: Role Administrator.

You can review the system documentation for Permissions Administration by following this link: User Administration User Guide. The section on permissions starts on page 7.

You have completed all of the lessons in this unit, you can now continue to the conclusion.

Links to the guides for each of the administration tools were provided in those sections. In addition to the guides, you find the Request Deployment Toolkit helpful as well.

This toolkit is designed to provide you with additional resources that will help you configure and implement Concur Request, including a package containing specifications for all file imports and extracts.