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
- 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
- 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
NewUser and Edit User Window Fields
This topic describes the New User and Edit User window settings. The settings are organized into the following categories:
User Settings contains the user's basic information. These settings display for all user types.
Note: Some settings may be unavailable based upon your administrator permissions (e.g., Sell Side Administrator, non-X_TRADER ASP Administrator).
The Universal Login ID used to log into a TT application (e.g., JDOE)
Note: Usernames are limited to 11 characters.
|Display name||An identifier associated with the username that appears in grid displays to help identify the user (e.g., John Doe).|
|Group (Optional)/Company||Group: Identifies the user’s
group name. A group consists of multiple exchange traders and/or TTORDs
trading in a non-X_TRADER ASP environment, and may reflect some aspect
of the traders (e.g., Energy). Group also determines which TT User
Setup administrators can manage which users.
Company: Identifies the user’s buy-side firm when trading in the X_TRADER ASP environment
|Select Group||Used to select the user’s group
Note: This button is disabled in the X_TRADER ASP environment.
|Password / Confirm password||The user's login password (e.g.,
Note: Password fields only appear in the New User window before a user has been saved.
|Generate Password||Allows the system to generate the user’s password
Note: When editing users, the Generate Password button changes to “Password”. Clicking the button opens a new window where you can generate a new password.
|Active||Activates the user's login (Default). Uncheck this field if you would like to deactivate a user’s login so the user cannot log in.|
|Force logoff||Determines whether the user can
shut down X_TRADER and reclaim an X_TRADER license when the user
exceeds their maximum number of logins.
If unchecked, the user cannot kill an X_TRADER connection. (Default)
Example: When enabled, a user who leaves X_TRADER running at work and tries to log in later at home would receive the option to select and kill one of his X_TRADER connections prior to logging into X_TRADER.
|Never lock out due to inactivity||Prevents the user from being locked out after being inactive.|
|Locked Out||Indicates whether the user is currently locked out. Uses can get locked out when they exceed the password locking rules, the number of failed attempts, or the days of inactivity.|
|Password never expires||Determines whether there is a
time limit enabled on the user’s login password.
If checked, the user’s password does not expire. (Default)
In a X_TRADER ASP environment, a broker administrator can enable this setting for traders in the broker company, and not for buy-side users or for the brokers themselves. In X_TRADER ASP, this setting is unchecked by default (passwords are set to expire).
|Two-factor authentication||Enables two-factor authentication for a user login. If enabled,
users can receive a text message or email containing an authentication
code when attempting to login. In addition to a password, users
must provide this code when logging into X_TRADER®, X_RISK®,
and TT User Setup.
Note: This setting can only be enabled for a user when it is enabled first in the System Settings.
|SMS Number||Sets the SMS (text message) number for the user to receive an
authentication code when logging into X_TRADER®, X_RISK®,
and TT User Setup.
An SMS number is required when two-factor authentication is enabled for the user (i.e., the Two-factor authentication checkbox is checked) and the SMS option is enabled for the system.
Note: Numbers outside the U.S. must be entered in "+<countycode><number>" format (e.g., +651234567).
|CME Market Data Access||
Sets a user as grandfathered and/or covered under a netting agreement for billable CME Product Groups:
|Contact fields||Stores the user's Country, Address,
City, State/Province, Zip, Email, Phone Number, and Organization.
Notes: In X_TRADER ASP, Country and Email are required fields. If you set Country to United States, you must set a zip code.
|User Defined Fields|
|User Defined 1 - 6||Stores optional user information, such as MGT, account number, etc.|
Note: This selection is only available when setting up users trading in the X_TRADER ASP environment.
|Billing 1,2 and 3||Stores the user’s billing information
and applies to users trading in the X_TRADER ASP environment.
Note: These fields are broker controlled.
Determines if the user can trade (i.e., add, modify, and delete orders).
If checked, the user is able to trade. (Default)
Note: Ensure this setting is checked for non-tradeable administrator logins (e.g. TTADMXXX100 or TTORDTSXXXMGR) requiring the ability to delete orders, even though they are unable to trade.
|Credit||Determines the overall dollar amount a trader can lose during a given trading session. Enter 0 to reset the credit to Unlimited.|
|Currency||Determines the currency of the credit value.|
|Override credit for TT SIM||
Determines if a different credit limit (i.e., TT SIM Credit) is applied when the user is trading in TT SIM mode.
If unchecked, the value in the Credit field is applied when trading in TT SIM mode. (Default).
If checked, the value in the TT SIM Credit field is applied when trading in TT SIM mode.
|TT SIM Credit||Sets the user’s TT SIM credit limit. Enter 0 to reset the TT SIM credit limit to Unlimited|
|Ignore P&L||Determines whether the user’s P&L is checked before the
order is sent to the market
If unchecked, the user’s P&L is evaluated. (Default)
If checked, the user’s P&L is ignored.
Note: If assigning a credit limit, then Ignore P&L should be unchecked; P&L is calculated on a per product basis.
|Ignore Margin||Determines whether margin is ignored before sending the order
to the market.
Checked ignores margin; unchecked does not
|Use P&L risk algorithm (Use bid/ask midpoint if the LTP is not between the bid/ask)||
Determines the method used to risk check the user.
Checked uses the P&L risk algorithm; the P/L based on setting in X_TRADER defaults to Risk Algorithm,
Unchecked uses the Last Traded Price; the P/L based on setting in X_TRADER remains editable.
|Prevent orders that are more than X ticks from the market price||
Determines how far from the market price a user may enter an order (in ticks). For more information about pre-trade price controls, refer to Setting Pre-Trade Price Controls.
|Apply into the market only||Enforces a maximum price on buy orders and a minimum price on sell orders when the Prevent orders that are more than X ticks away setting is configured.|
|Per TT Gateway, prevent more than X orders per second||Limits the number of orders per second, per TT Gateway. For more information about pre-trade order throughput controls, refer to Setting Order Throughput Controls.|
|Gateway Login Risk Limits||Opens the Gateway Login window.|
|Account Risk Limits||Opens the Account Permissions window.|
|X_TRADER Mode||Determines whether X_TRADER starts up in X_TRADER or X_TRADER Pro. The <Not Specified> option opens the trading application being used locally by the user.|
|User’s most recently recorded X_TRADER version||Displays the user’s most recently recorded X_TRADER version.|
|TT SIM login allowed||Allows user to log in to X_TRADER in TT SIM Mode.|
|X_RISK allowed||Allows a user to log in to X_RISK. If unchecked, a user cannot
log in to X_RISK.
In X_TRADER ASP, this field is disabled and checked (X_RISK is available to all users by default in the X_TRADER ASP environment).
|Live (non-TT SIM ) login allowed||Allows user to log in to X_TRADER in live production mode.|
|Limit the number of concurrent logins (based on IP address)||Restricts the number of times
a single user's login can be in use simultaneously. You must also enforce
the Concurrent Logins rules at the system level for this field to
have affect. Refer to Configuring
Concurrent Login Rules if needed.
Note: This setting is disabled in a X_TRADER ASP environment.
Users that access CME market data and are not validated netting participants will be limited to a single concurrent login in X_TRADER ASP.
|TT API allowed||Allows user to access the TT API. This option is unchecked by default and is only applicable to TTNET customers.|
|XT API allowed||Allows user to access the XT API. This option is checked by default for all new users and can be enabled/disabled by a Group Admin or Super Admin. In a X_TRADER ASP environment, this option is controlled by a Broker Admin or Super Admin.|
|Autotrader Allowed||Allows user to access Autotrader. This option is checked by default for all new users and can be enabled/disabled by a Group Admin or Super Admin. In a X_TRADER ASP environment, this option is controlled by a Broker Admin or Super Admin.|
|Autospreader (desktop) Allowed||Allows user to access Autospreader. This option is checked by default for all new users and can be enabled/disabled by a Group Admin or Super Admin. In a X_TRADER ASP environment, this option is controlled by a Broker Admin or Super Admin.|
|Aggregator Allowed||Allows user to access Aggregator. This option is checked by default for all new users and can be enabled/disabled by a Group Admin or Super Admin. In a X_TRADER ASP environment, this option is controlled by a Broker Admin or Super Admin.|
|X_STUDY/FMDS allowed for the user||Determines whether X_STUDY/FMDS is available to the user.
If checked, X_STUDY/FMDS is available. (Default)This setting is only available when the X_STUDY/FMDS Allowed system setting is enabled.
For a detailed description of FMDS and X_STUDY settings, refer to the Enabling and Configuring X_STUDY and FMDS System Settings topic.
|X_STUDY/FMDS allowed for system||Determines whether the X_STUDY and FMDS can be used in the system.|
|Override system settings with user settings||Overrides the FMDS server system settings with Primary FMDS/Secondary FMDS Server settings for this user.|
|Primary/Secondary FMDS Server IP address||Specifies the IP address for the primary and secondary FMDS server.|
|Primary/Secondary FMDS Server Port||Specifies the port setting for the primary and secondary FMDS server.|
|Primary/Secondary FMDS Server Service||Specifies the service setting for the primary and secondary FMDS server.|
|Primary/Secondary FMDS Server Time Out||Specifies the timeout setting for the primary and secondary FMDS server.|
|ADL Algo deployment||Determines whether the user can deploy strategies to Algo SE
If checked and the user is configured to connect to an Algo SE server, the user can deploy algos. This setting is only valid when the user is configured to connect to an Algo SE server.
|ADL Algo sharing||Determines whether the user can share algorithms with other
users on Algo SE Servers.
If checked and the user is configured to connect to an Algo SE server, the user can share algos with other users. The other users do not need this setting enabled for their usernames in order to have an algo shared with them. However, users with X_TRADER® 7.12 or lower also need to share an order book with the user sharing an algo with them.
Note: If you enable (check) this setting, then ADL Algo deployment must also be enabled. Also, this setting is only valid if the user is configured to connect to an Algo SE server.
|GTC/GTDate orders||Determines whether the user can submit Good til Cancel and Good
til Date orders.
If checked, the user can submit GTC and GTDate orders. (Default)
|Market Orders||Determines whether the user can submit Market orders in X_TRADER.
If checked, the user can submit Market orders. (Default).
When unchecked, the user cannot submit any Market order types, including: Stop Market, Market If Touched, or Market-To-Limit.
|“On Behalf Of” orders||Determines if a Direct Trader can enter orders on-behalf-of
(OBO) TTORD users whose orders the Direct Trader can view.
If unchecked, the Direct Trader cannot enter OBOs. (Default)
If checked, the Direct Trader can enter orders on-behalf-of TTORD users whose orders the Direct Trader can view.
|Wholesale trades||Determines whether the user can
submit wholesale trades in X_TRADER.
If unchecked, the user cannot submit wholesale trades (Default).
If checked the user can submit wholesale trades.
Note: In a X_TRADER ASP environment, wholesale trading cannot be enabled for buy-side users.
|Submitting wholesale orders with undefined accounts||
Determines whether the user can submit wholesale orders using any account or only accounts defined in TT User Setup.
If unchecked, the TT Gateway rejects wholesale trades with accounts that are not defined in TT User Setup (Default).
If checked, the user can submit wholesale trades with any account, including accounts not defined in TT User Setup unless accounts are restricted in TT User Setup Account Permissions.
If checked, the user can quote and send RFQs in X_TRADER (Default).
In a X_TRADER ASP environment, this setting is checked and enabled for broker administrators by default. The broker administrator can enabled/disable RFQ for buy-side users connecting to the broker’s TT Gateways via X_TRADER. However, a broker administrator cannot change the RFQ setting for their own user profile.
Note: See X_TRADER Help for additional information about X_TRADER Quoting functionality.
|Avoid orders that cross||Determines the default behavior for crossed orders.When an order
is submitted, changed, or canceled/replaced, this setting is first
applied to any in-flight orders not yet acknowledged by the TT Gateway.
Then, the setting is applied to the user’s resting orders on the
opposite side of the outbound order. Order quantities and position
in queue are not considered.
If checked, the working Limit or native Iceberg order is rejected (Reject New) or canceled and replaced with the new order (Cancel resting). All other exchange-supported order types and restrictions are not impacted, including:
If unchecked, the Avoid orders that cross setting is not enforced.
If Avoid orders that cross is set, this setting takes precedence over the account-level setting.
|Persist all orders||Determines if Eurex orders are automatically set to persist
(i.e., written to the exchange database and saved during an exchange
outage) or user-controlled (i.e., based on the user’s credentials from
the exchange). By default, this option is unchecked and order routing
behavior is “user controlled”.
Note: See Eurex Gateway in the Help Library if you would like additional information.
|Account changes on fills||
Determines whether the user can update the account number on a fill.
If checked, the user can update the account number. (Default)
Note: If the user’s customer defaults are restricted, then only accounts that are pre-defined in the customer defaults are available.
Note: When applying account-based risk checking, TT does not recommend checking the Account changes on fills allowed option until the user is using X_TRADER 7.17 or later. If a user with a pre-7.17 version of X_TRADER is allowed to change an account on a fill, the account number on the fill will not be updated in all TT products (including the gateways where account-based risk checking is done). This could lead to discrepancies between what is displayed in client applications and how risk is actually being calculated.
Note: When this option is enabled, users with X_TRADER 7.17 or later can modify the account on a fill, and this update will be processed as a part of account-based risk on the gateways. Note that no risk check actually takes place on the modification; therefore changing the account could cause an account to go over its limits. However, any subsequent orders will be risk checked based on the modified fills.
|Submitting orders with undefined accounts (if applicable)||
Determines whether the user can submit orders using any account or only accounts defined in TT User Setup.
If unchecked, the TT Gateway rejects orders with accounts that are not defined in TT User Setup (Default).
If checked, the user can submit orders with any account, including accounts not defined in TT User Setup unless accounts are restricted in TT User Setup Account Permissions.
Note: Beginning with TT User Setup 7.17, you can create TTORDs without accounts; accounts are not required if applicable clients and servers ave been upgraded to 7.17.
|Staged Order Permissions|
|Staged order creation||Determines whether the user can create staged orders.
If unchecked, the user cannot create staged orders. (Default)
|Staged order management||Determines whether the user can claim and work staged orders
created by another user.
If unchecked, the user cannot enter and claim staged orders created by another user. (Default)
|Claiming one’s own staged orders||Determines whether the user can claim and work staged orders
created by themselves.
If checked the user can claim and work staged orders created by themselves. (Default)
|Direct Market Access (DMA) order creation||Determines whether the user can create DMA orders.
If checked, the user can create DMA orders. (Default)
|TT Synthetic Algo Order Types|
|Iceberg orders||Determines whether the user can submit Iceberg orders in X_TRADER.
If checked, the user can submit Iceberg orders. (Default)
See X_TRADER Help for additional information about this order type.
|Time sliced orders||Determines whether the user can submit Time Sliced orders in
If checked, the user can submit Time sliced orders. (Default)
See X_TRADER Help for additional information about this order type.
|Volume sliced orders||Determines whether the user can submit Volume Sliced orders
If checked, the user can submit Volume Sliced orders. (Default)
See X_TRADER Help for additional information about this order type.
|Time duration orders||Determines whether the user can submit Time Duration orders
If checked, the user can submit Time duration orders. (Default)
See X_TRADER Help for additional information about this order type.
|Volume duration orders||Determines whether the user can submit Volume Duration orders
If checked, the user can submit Volume Duration orders. (Default)
See X_TRADER Help for additional information about this order type.
|Machine gun orders||Determines whether the user can submit Machine Gun orders in
If checked, the user can submit Machine Gun orders. (Default)
See X_TRADER Help for additional information about this order type.
|Sniper||Determines whether the user can submit Sniper orders in
If checked, the user can submit Sniper orders. (Default)
See the Autospreader help for additional information about this order type.
|EU Market Settings|
|EU Config 1||Reserved for future use.|
|EU Config 2||Reserved for future use.|
|Customer||Identifies the customer profile name.|
|Sel||Determines whether the customer profile is available in X_TRADER.
If checked, the customer profile is available in X_TRADER.
|Market||Identifies the market (e.g., CME) where the account is allowed to trade. Enter an asterisk (*) for all.|
|Gateway||Determines an order routing gateway to log in to by default. Enter an asterisk (*) to access all available gateways.|
|Product Type||Identifies the product type the account is allowed to trade (i.e., FUTURE, OPTION, STOCK, BOND, ENERGY, INTER-PRODUCT SPREAD, INTER-PRODUCT STRATEGY). Enter an asterisk (*) for all.|
|Product||Identifies the product the account is allowed to trade. Enter an asterisk (*) for all. Separate multiple products with a comma (e.g., ES,NQ).|
|Account #||Identifies the customer account number, associates a trade with a specific customer; may be used by middle or back office as a sub-account.|
|Account||Identifies the default account type as defined by the exchange:
|Give Up||Identifies the member code for whom a separate party completes a transaction; used for trades designated as G2, G2, or G3.|
|FFT2||Free form text field used for annotation purposes; some exchanges require a value in this field.|
|Product Alias||Identifies another name for the product.|
|FFT3||Free form text field used for annotation purposes; some exchanges require a value in this field.|
|First <DEFAULT)>||Specifies whether a <DEFAULT> customer profile entry was the first such default created for that user.|
|Restrict Editing||Identifies whether or not this user is restricted from overriding X_TRADER customer defaults.|
|OBO Username||Identifies the username of the TTORD trader.|
|OBO Account||Identifies the account number of the TTORD trader|
|OBO Member||Identifies the Member ID of the TTORD trader|
|OBO Group||Identifies the Group ID of the TTORD trader|
|OBO Trader||Identifies the Trader ID of the TTORD trader|
|Conn Alias||Identifies a connection so the user can differentiate between two gateways when they have multiple connections to the same gateway.|
|Conn Gateway||Identifies the order gateway when a user has multiple connections to the same gateway|
|Conn Member||Identifies the default Member if the user has multiple logins to the gateway.|
|Conn Group||Identifies the default Group if the user has multiple logins to the gateway.|
|Comm Trader||Identifies the default Trader ID if the user has multiple logins to the gateway.|
|Conn Exch Member||Identifies the exchange-recognized Member ID.|
|Conn Exch Group||Identifies the group ID.|
|Conn Exch Trader||Identifies the exchange-recognized Trader ID.|
|Conn Broker||Identifies the Broker.|
|Product Group Permissions|
Note: Buy-Side users have product group permissions blocked by default. Al other users have product group permissions allowed by default.
|Allow||Provides access to the products in the group(s). You can also
check or uncheck the Allowed check box adjacent to the product
Note: The user must also be configured to connect to one or more applicable gateways (i.e., gateways for the same market as specified in the group).
|Block||Prevents access to the products in the group(s). The blocked
products will not display in the user’s Market Explorer or Instrument
Explorer, and the user will not be able to subscribe to prices.
Note: For additional details, see Allowing or Blocking Product Groups for Specific Markets.
|Market||Specifies the market where the product group is traded.|
|Product Group||Specifies the product group that supports the allow/block feature.|
|Allowed||Specifies whether the user can access the product group.
If checked, the user has access to the products in the product group. This includes the ability to view market data and trade
If unchecked, the user does not have access to the products in the product group.
If the market does not contain specific Product Groups (e.g. EUREX, etc.), then the user will be able to access all products
|Subscriber Agreement Signed||For CME Market Data reporting, this read-only field indicates whether the user has signed an agreement with CME for access to a particular CME product group. Agreements must be signed by 1/1/2015 to maintain access to market data for the applicable CME product group.|
|Administrator Type||Identifies the administrator type:
|Manage Gateway Logins||Provides administrator with the ability to manage one or more
gateway logins. Gateway login administrators cannot edit users,
but can assign gateway logins and gateway login attributes to users
in a user group that the administrator is designated to manage.
Note: You can allow the gateway login administrators to manage only specific groups using the Restricted to the groups below option.
|Manage accounts and broker-specific user settings||This checkbox is checked by default. If unchecked, Group Administrators cannot set a user’s X_TRADER® Mode or change the Can only create, modify, and delete orders with the following accounts setting on the Account Permissions tab for a user. When the checkbox is unchecked, Group Administrators are limited to managing Gateway Logins and user settings that do not impact billing.|
|Create Direct Trader Gateway Logins (If unchecked, can only create and edit TTORDs||Determines whether the administrator can create Direct Trader IDs. If this is not checked, the administrator can only create and edit TTORD IDs.|
|Restricted to the groups below||Determines whether the administrator is restricted to specific groups. To restrict the administrator, select the desired user groups in the Available User Groups column and use the transfer buttons to move the desired groups into the Selected User Groups column.|
|Manage trader-based product limits (cannot manage account-based risk)||In a X_TRADER ASP environment, determines whether a buy-side
administrator with a relationship with a broker company is allowed
to add/edit product limits to existing gateway logins assigned to
the buy-side administrator's users. To allow this, click the check
box to enable. By default, it is unchecked and risk is managed by
the broker company only.
Note : this setting applies to gateway login risk only -- account-based risk is solely managed by the broker company administrator.
|Outgoing Email Settings|
|Enable outgoing email settings (Required for TT User Setup Administrators who email passwords)||Enables the email settings for TT User Setup administrators who need to email user passwords.|
|SMTP server host or IP address||Specifies the email server used for sending email.|
|SMTP port||Specifies the port used for sending email (25 is standard for most ports).|
|SMTP server requires authentication||Enables SMTP server authentication. This is an optional setting that is necessary if your email server requires authentication. When this option is checked, you must provide an SMTP server account name and password,|
|Account name||SMTP server account name used for SMTP server authentication.|
|SMPTP password||SMTP password used for SMTP server authentication.|
|Use SSL||Enables SSL. This is an added security measure required by most servers.|
|From email address||Specifies the string that appears in the From field of the email sent to the recipient.|
|Email subject||Specifies the subject that appears in the password email.|
|Additional message text||Specifies miscellaneous user instructions (Optional).|
|Include username in message||Includes the email recipient’s username in the email.|
|Send Test Email||Allows you to send an email to test the configured settings.|
|Contract Session Prices (CSP) access allowed||Determines whether the user can to publish Contract Sessions
Prices in X_RISK.
If checked, the user can publish CSP; if unchecked, the user cannot (Default).
|Instant Messages (IM) access allowed||Determines whether the user can send instant messages in X_RISK.
If checked, the user can IM; if unchecked, the user cannot (Default).
|Manual Fill (MF) and Start of Day (SOD) publishing allowed||Determines whether the user can publish manual fills in X_RISK.
If checked, the user can publish MFs and SODs (Default); if unchecked, the user cannot.
|Restrict X_RISK administrator to publishing MF/SODs to Accounts within the User Groups listed below||Restricts publishing to accounts in specific groups. When this
setting is checked, the Available User Groups for MF/SOD and Selected User
Groups columns display.
Select the desired user groups in the Available User Groups for MF/SOD column and use the transfer buttons to move the desired groups to the Selected User Groups column.
Use Gateway Logins to assign gateway logins or to view or edit product limits..
|Generate Admin Gateway Logins for all gateways||Enables the Member/Group/Trader
fields which allow you to configure an MGT that can log into all
Example: This is especially useful if setting up a Universal Login for something like the Historical Fill Server. This ensures that HFS always logs into all gateways.
Note: For more information about administrator gateway logins, refer to the Administrator Logins section of the TT User Login and Risk Administration guide.
|New/Edit||Creates a new gateway login. Refer the Creating a New Gateway Login through the Users Window topic for more information.|
|Remove||Removes the selected gateway login(s).|
|Assign Existing Logins||Assigns existing gateway logins to the user. Refer to the Assigning Gateway Logins to a User Through the Users Window topic for more information.|
|Product Limits||Accesses all product limits for the given user. Refer to the Creating Product Limits for Gateway Logins topic.|
|Member||The unique Member ID used to identify an exchange trader or TTORD as part of their MGT.|
|Group||The unique Group ID used to identify an exchange trader or TTORD as part of their MGT.|
|Trader||The unique Trader ID used to identify an exchange trader or TTORD as part of their MGT.|
|Gateway||Specifies the gateway a user is able to log into and trade using
their assigned gateway login (e.g., CME).
Note: If a gateway alias is defined in aconfig, the Gateway column displays <gateway> to represent the alias.
|Exch Member||Specifies the exchange trader’s Member ID mapped to the TTORD.|
|Exch Group||Specifies the exchange trader’s Group ID mapped to the TTORD.|
|Exch Trader||Specifies the exchange trader’s Trader ID mapped to the TTORD.|
|Avail to User*||Indicates whether a user has access to a given gateway login after performing a universal login.|
|Auto Login*||Specifies if a user of a specific gateway login will be automatically logged into the associated gateways.|
|Operator ID*||Specifies the Operator ID that is used to identify the trader or operator to the exchange.|
|Exchange 1 -- 6||Used for configuring exchange-specific order routing functionality. (e.g., CME Self Match Prevention). These fields can also be configured to replace the use of FFT fields in X_TRADER®.|
|Mandatory Login*||Specifies whether a user of a specific gateway login will be automatically logged into a given gateway.|
|Preferred IP||Specifies the IP address of the gateway through which you want the user’s first login attempt to be made.|
A unique identifier assigned to a login (TTORD or Exchange Trader) to be used by a customer profile and when incorporating risk.
|Risk Check||Specifies whether risk checking is enabled.|
|Trading Allowed||Determines whether the gateway login can trade (i.e., add, modify,
and delete orders).
If checked, the user is able to trade. (Default)
Note: Ensure this setting is checked for non-tradable administrator logins (e.g. TTADMXXX100 or TTORDTSXXXMGR) requiring the ability to delete orders, even though they are unable to trade.
|Ignore P&L||Determines if P&L is used in margin, credit, and position calculations.|
|Credit (per MGT)||The sum available at the start of the trading session, against which a single MGT can enter orders, whereby only that trader’s activity can affect the credit limit.|
|Currency||The currency in which trades are calculated (e.g., USD = United States).|
|Alias||An identifier associating|
|Other Users||Lists users that share a particular gateway login.|
|Clearing Member||Designates a member firm of a clearing house through which trades are settled.|
|Default Account||Specifies the default account type as defined by the exchange
(A1-A9, G1, G2, M1-M3, P1-P3, or U1-U3)
|Comments||Displays an error description when a product being saved does not exist in the gateway’s product table.|
|Override Credit for Sim||Indicates whether different credit limit (i.e., TT SIM Credit) are applied when the user is trading in TT SIM mode.|
|TT SIM Credit (per MGT)||Displays the TT SIM credit limit per MGT.|
|Created Date||Displays the date the user was created.|
* These fields are available as columns in the Gateway Logins table. Use the Show/Hide/Arrange columns option to view any hidden columns.
Account Permissions applies to X_TRADER and X_RISK and contains the following
|Can only create, modify, and delete orders with the following accounts (others will be rejected)||Determines whether the account
the user can only use the accounts displayed in the Account Permissions window.
If unchecked, the user is not restricted to specific accounts (Default).
If checked, the user is restricted to the accounts displayed in the Accounts Permissions grid.
|New/Edit||Creates new account permissions.|
Removes the selected account permissions.
|Edit Account Group||Allows the administrator to edit permissions for a selected group of accounts.|
|Assign Existing Account||Opens the Select Account window so that you can select from a list of existing list of accounts.|
|Account||Specifies the account number to which you want to assign permissions.|
|Account Group||Specifies the account group to which the account belongs.|
|Permitted for Order Routing||Indicates whether the account is allowed to route orders.|
|Permitted for ADL order routing||Indicates whether the account can use the account to route algo orders.|
|Created Date||Indicates the date the account was created.|
The FIX Adapter tab applies to FIX Adapter Server and Client users. It contains the following tabs:
FIX Adapter (server role)
The FIX Adapter tab fields vary depending on the selected role (client or server). When you set the FIX Adapter role to FIX Adapter Server, you can create either an Order Routing server type or a Drop Copy server type.
Note: Broker and Buy Side administrators cannot create FIX Adapter servers, however, they can create FIX Adapter clients.
|FIX Adapter role||Select the desired role: None, Client, Order Routing Server, or Drop Copy Server.|
|Order routing server/Drop copy server||Sets the FIX Adapter Server type.|
|FIX Adapter Version||Select the FIX Adapter version: Pre 7.17 or 7.17 or later.|
|Available FIX client users||Lists the available FIX client users.|
|The following FIX clients can connect to this FIX Adapter||Lists the clients that the FIX adapter will connect to the Gateways on behalf of.|
FIX Adapter (client role)
The FIX Adapter tab fields vary depending on the selected role (client or server). When you set the FIX Adapter role to FIX Adapter Client, you can allow or prevent staged orders, enable debugging, and assign the client a FIX Adapter server.
|FIX Adapter Role||Select FIX Adapter Client. For more information about FIX Adapter server and client users, refer to the TT FIX Adapter and TT User Setup Overview topic.|
|Enable debug logging for prices||
Adds debug messages generated by the Price Server to the log files.
Note: Because the log file size may increase significantly and performance may be affected, only enable these fields when troubleshooting the connection between FIX Adapter and either Server.
Note: TT FIX Adapter 7.8 and later ignores the Enable debug logging for orders setting.
|Available FIX Adapters||Displays configured FIX Adapter servers in your environment.|
|The FIX client user can connect to the following FIX Adapters||Identifies FIX Adapter clients.|
|Username||Identifies the name of the FIX Adapter Server.|
|Display Name||Identifies the name of the FIX Adapter Server.|
|Role||Displays the Fix Adapter Server role|
|Company||Identifies the user’s firm.|
The Account Defaults tab has the following buttons and fields:
The data grid has the following fields:
|FIX Adapter Account Defaults|
|New/Edit||Created a new account profile. Refer to “Setting Up an Account” Setting Up an Account Default topic for more information.|
|Copy||Copies the selected account.|
|Copy from user||Copies an existing account profile from another user within your environment.|
|User List||Displays a list of existing users; used in conjunction with Copy from user.|
|Priority||Specifies the priority of the FIX adapter account profile. When an order matches more than one account default (based on key values), TT FIX Adapter server uses the match with the highest priority.||Key|
|Account #||Identifies the account number. Enter an asterisk (*) to match any account number.||Key|
Identifies the market (e.g., CME) where the account is allowed to trade. Enter an asterisk (*) for all.The name of the market. Enter an asterisk (*) to match any market.
|Gateway||Identifies the gateway. Enter an asterisk (*) for any gateway.||Key|
|Product type||Identifies the product type the trader is allowed to trade (i.e., FUTURE, OPTION, STOCK, BOND, ENERGY, INTER-PRODUCT SPREAD, INTER-PRODUCT STRATEGY). Enter an asterisk (*) for all.||Key|
|Account type||Identifies the default account type as defined by the exchange (e.g., A1, M1, P‘).:The type of account associated with the trader.||Value|
|Clearing account||Indicates the clearing member code. Used for Give-up trade accounts only.||Value|
|FFT2/FFT3||The free form fields, often used for annotations by traders or back offices.||Value|
|Created Date||Indicates the date the account profile was created.|