← Back to X_TRADER® Help Library
TT User Setup Documentation
- Getting Started
- User Administration Basics
-
User Administration: Administrative Users
- Creating and Editing Administrative Users
- Creating a Super Administrator
- Creating a Broker Administrator - X_TRADER ASP
- Allowing Buy-side Administrators to Manage Product Limits (X_TRADER ASP)
- Creating a Group Administrator (non-X_TRADER ASP only)
- Creating a Gateway Login Administrator (non-X_TRADER ASP only)
- Creating a Password Administrator (non-X_TRADER ASP only)
- Creating a View Only User
- Creating a Collect Log Files Only User
- Configuring the Outgoing Email Settings
-
User Administration: X TRADER® Or X RISK® Users
- Creating and Editing X_TRADER or X_RISK Users
- Applying Basic User Properties
- Customizing Billing Data for a User - X_TRADER ASP only
- Configuring User Risk Settings for a User
- Setting Application Permissions
- SettingTrade Permissions
- Creating and Managing X_TRADER Customer Defaults
- Customer Defaults and Algo Defaults MiFID II
- Allowingor Blocking Product Groups for Specific Markets
- Applying X_RISK Permissions
- Creating a New Gateway Login through the Users Window
- Generating a Gateway Login for all Gateways
- Assigning Gateway Logins to a User Through the Users Window
- Setting Account Permissions
-
User Administration: FIX Adapter
- TT FIX Adapter and TT User Setup Overview
- Setting Up a TT FIX Adapter Server (non-X_TRADER ASP)
- SettingUp a FIX Adapter Client User
- Setting Up an AccountDefault
- FIX Adapter Account Defaults MiFID II
- Assigning TT FIX Adapter Client(s) to a FIX Adapter Server
- Allowing or Blocking Product Groups for a FIX Adapter User
- User Maintenance
- Gateway Login Administration Basics
-
Creating Gateway Logins
- Creating a New Gateway Login
- Assigning the MemberGroupTrader ID
- Disabling Start-of-Day Records
- Assigning Gateways to Gateway Logins
- Mapping a TTORD to an Exchange Trader
- Adding Gateways to Existing TTORDs
- Assigning Accounts
- Configuring Risk
- AssigningUsers to a Gateway Login
- Editing a User's Gateway Login Attributes
- Assigning Gateways to Multiple Gateway Logins
- Account Group Administration
- Account Administration
- Order Passing Group Administration (X_TRADER ASP)
- Gateway Login Risk Administration
-
Account And Account Group Risk Administration
- Adding Account-Level Risk Checking
- Adding Account Group-Level Risk Checking
- Creating Product Limits for Accounts and Account Groups
- Enabling Duplicate Order Check for Accounts and Account Groups
- Creating Contract Level Overrides
- Contract Limits Overview
- Creating Margin Limits for Accounts and Account Groups
- Applying Account-BasedRisk to Wholesale Trades
- Configuring Wholesale Order Overrides
- Copying Product Limits to Additional Accounts or Account Groups
- Copying Account-Based Product Limits to Additional Gateways
- Copying MGT-based Product Limits to Account-Based Product Limits
- User Level Risk Checking
- User Group Administration
- Publishing To Guardian
-
Server Administration
- Disabling Trading for a Trading Environment
- Collecting Log Files
- Using Version Control Rules
- Resetting the Guardian Exchange Tree (non-X_TRADER ASP only)
- Editing the Currency Exchange Rates
- Adding and Deleting Currencies
- Editing Product Margins
- Viewing and Clearing Product Margin Conflicts
- Viewing and Publishing Licenses
- Migrating Users to a New Gateway
- Understanding Server Messages
- System Settings
- Enabling Two-factor Authentication
- Reports
-
Tutorials
- How to Setup a New User Who Will Trade Using a TTORD Gateway Login
- How to Map an Additional Gateway Login to an Existing TTORD User
- How to Set Up an Administrator Who Uses Both X_RISK and TT User Setup
- How to Set Up a Third-party Risk Administrator
- How to Create a New User by Copying an Existing User
- How to Assign Existing Product Limits to Other Gateway Login IDs Simultaneously
- How to Change Multiple Product Limit Values Simultaneously
- How to Set Up Customer Defaults
- How to Update Customer Defaults Across Multiple Users Simultaneously
- How to Change the Message Users Receive When Their Logins Fail
- How to Use Wildcard Characters in Filters
- How to Set Up a Tiered Administrator
- How to Set Up a Drop Copy TT FIX Adapter Server and Corresponding FIX Adapter Clients
- How to Set Up an Order Routing TT FIX Adapter Server and Corresponding FIX Adapter Clients
- How to Set up a User for Autospreader SE or Synthetic SE
- Creating TT SIM Credit Limits and Product Limits
- Appendix
Editing a User’s Gateway Login Attributes
You are viewing TT User Setup Version 7.17 and higher. For earlier versions, click here
The User's Gateway Login Attributes window displays all the users, the gateway logins to which they are assigned, and various attributes applied to each specific login.
Use this window to edit attributes across one or more users simultaneously.
To edit a user’s Gateway Login Attributes...
- From the User Admin menu, select User's Gateway Login Attributes.
The User's Gateway Login Attributes window appears.
- Select a user and click Edit.
The Edit User's Gateway Login Attributes window appears.
- Change or add login attribute values as needed. Refer to the following table for a description of each attribute.
| Login Attribute | Description |
|---|---|
| Available to User | Indicates whether a user has access to a given gateway login after performing a universal login. |
| Available to FIX Client | Indicates whether a FIX Client has access to a given gateway login after performing a universal login. |
| Automatically login | Specifies that a user will automatically be logged into a gateway after logging into X_TRADER. |
| Mandatory login | Indicates whether the user must log onto this Gateway when logging into TT applications. Check this option to prevent users from bypassing risk limits by not logging into a specific Gateway. |
| Default Account | Refers to the account and associated numeric CTI value for all orders sent through an order session. For more information on CTI/Origin values, refer to the TT CME Gateway System Administration Manual or any other applicable TT Gateway System Administration Manual. |
| Clearing Member | Designates a member firm of a clearing house through which trades are settled. |
| Preferred IP | Specifies the IP address of the gateway through which you want the user's first login attempt to be made. If unavailable, TT User Setup automatically selects an alternate IP address of the same gateway type. |
| Operator ID | Specifies the Operator ID that is used to identify the trader to the exchange (e.g., Tag 50 for CME). To configure an Operator ID for the Gateway Login, enter or select an Operator ID from the drop down menu in this field. Operator IDs can also be configured on the following User Admin windows:Users | New or Edit User |Gateway LoginsGateway Logins | Assign to Users Note: An Operator ID is required if the Available to User or Available to FIX Client field is enabled for an ICE or Eurex Gateway Login. For ICE, clients running TT User Setup 7.17.60 or earlier will still be prompted to enter an Operator ID. If this is an issue, upgrade to 7.17.61 or later, which removes this requirement for ICE Gateway logins. |
| Executing Firm | Sets the User or firm that submitted an order. To support MiFID II compliance, this field is used for setting a registered ID or Short Code. |
| Exchange 1 -- 5 | Used for configuring exchange-specific order routing functionality (e.g., CME Self Match Prevention). The Exchange fields on this screen can also be configured to replace the use of FFT fields in X_TRADER. |
| User Level Overrides | |
| Prevent more than X orders per second (overrides the User-Level setting) | The maximum rate of orders per second allowed per TT Gateway. This setting overrides the rate set for all TT Gateways assigned to a user. |
| Market Orders | Allows or prevents market orders for a user’s Gateway Login, or defers to the user’s setting for market orders. This setting only applies to native market orders being submitted (Cancel/Delete/Hold are unaffected). Select one of the following options:
|
Configuring a Self-Match Prevention ID
CME Gateway 7.17.30 or higher and CME Gateway 7.18.15.6 or higher support CME Globex Self Match Prevention functionality. SMP is optional and allows an executing firm to prevent the matching of orders for accounts with common ownership if both the buy and sell orders contain the same Self-Match Prevention Identifier (SMP ID) and Executing Firm ID. The SMP ID is configured in the Exchange 1 field on the Edit Gateway Login Attributes screen when connecting to either CME Gateway. However, for users connecting to CME Gateway 7.18.15.6 or higher, the Self Match Prevention is configured using the Exchange 1 and Exchange 3 fields on the Edit Gateway Login Attributes window or New/Edit User Gateway Logins window in TT User Setup on a per user basis:- Exchange 1: Enables/Disables SMP for the user. Enter the user's exchange-registered SMP ID in this field, which is required for enabling the exchange's SMP functionality for a user. To disable SMP for a user, remove the SMP ID from Exchange 1 and leave the field blank.
- Exchange 3: Determines how the exchange should handle potentially self-matching orders. Enter one of the following values:
- O — If a user enters a self-matching order with Exchange 3 = O , the exchange will cancel the user's resting order and accept the newly entered order.
- N — If a user enters a self-matching order with Exchange 3 = N, the exchange will cancel the new (aggressive) order . The resting order remains at the exchange.
- <blank> — If a user enters a self-matching order with Exchange 3 = <blank> (empty), the exchange will cancel the user's resting order and accept the newly entered order (i.e., exchange behaves as if set to "O").
Configuring an ATS Operator ID
CME Gateway 7.17.30 or higher and CFE Gateway 7.17.60 or higher supports an ATS (automated trading system) Operator ID to identify users submitting automated trades to the exchange. The ATS Operator ID is a user-defined value that needs to be registered at the Exchange as Tag 50 (trader identifier) for automated trades. In TT User Setup 7.17.20 or higher, ATS Operator IDs are configured per TT Gateway Login for a user using the Exchange 2 field on the Edit Gateway Login Attributes screen.Providing an Alternative Gateway to Multiple Users
Scenario: The following procedure describes a situation in which multiple users connected to the same gateway (e.g. CME) lose access, and you must quickly make an alternative gateway (e.g. CME-A) available to each user simultaneously.
Note: This procedure assumes that each applicable user has been assigned to both the CME and CME-A gateways. For a detailed description of assigning users, refer to Assigning Users to a Gateway Login.To provide an alternative gateway to multiple users...
- From the User Admin menu, select User's Gateway Login Attributes.
The User's Gateway Login Attributes window appears.
- Filter the Gateway column by entering CME into the Gateway filter field.
- Holding down the Ctrl key, click the applicable user rows for which you want to make the associated login unavailable.
Note: Alternatively, you could enter =CME as the Gateway filter, and then press the Ctrl and a keys to select all the CME Gateways.
- Click Edit.
On the Edit multiple user Gateway Login records prompt, click OK .
The Edit Multiple User Gateway Login Attributes window appears.
- Uncheck the Available to User option to disable the feature.
- Click Save.
The Available To User column on the User's Gateway Login Attributes window shows the value unchecked.
- On the User's Gateway Login Attributes window, filter the Gateway column by =CME-A.
- Holding down the Ctrl key, click the applicable user rows for which you want to make the associated login available.
- Click Edit.
On the Edit multiple user Gateway Login records prompt, click OK.
The Edit Multiple User Gateway Login Attributes window appears.
- Check the Available to user option to enable the feature.
- Click Save.
The CME-A gateway is made available to the applicable user's associated gateway login.
Note: A single user cannot have more than one MGT login set to Available To User for identical gateways. In the example above, user RADAMS can only have one CME-A row marked Available To User even if he has two different MGTs for CME-A.
You have successfully provided multiple users access to an alternative gateway.