General settings are configured in the itris Management Utility (IMU), in the Settings area > General Settings.
Click below to jump to required section.
In addition to Rebate Periods, your Fixed Fee placements (all Permanent and any Contract or Temp placements set with a one-off fee) can have an extended period set that is the Grace Period. This is a way of superseding the rebate period with a longer protection period. Applicants within their grace period can be excluded from searches, preventing them from appearing in your search results. You could even set this exclusion as part of your default search template. Additionally, you will also receive warnings during the submission process if you are working with an applicant within a grace period.
If a placement ends before the grace period is concluded, the grace period for the placement will no longer apply.
In both your Company and Contact hubs you will note you have areas for Lapsed records. Lapsed record are those that have given at least one job in the past, but have not given a job for some time. That amount of time is set here in the IMU.
In the Community Hub by default, Twitter will display the itris feed, giving you the chance to see our latest content. The feed can be set to your company's Twitter account here.
Daxtra CV Parsing
Daxtra CV Parsing speeds up the process of adding an applicant record, by parsing data from the applicant's CV into the new record form, saving you time manually adding the data. However, should you wish to not use this functionality and you would instead prefer your users to manually enter the information, you can turn it off here.
Additionally, you may disable this is you are using Daxtra Deep.
Daxtra Keyword Parsing
Daxtra Keyword Parsing also speeds up the process of adding a new applicant, by matching text in the applicant's CV to daxtra and itris keywords. If there are matches to all three itris will automatically assign that keyword to the record (you can choose to remove any or assign more keywords). Additionally, it will highlight any keywords that exist in the CV and as daxtra keywords, but not as itris keywords. However, if you prefer your users manually enter keywords, you can turn off this functionality here.
If you don't require your users to enter their password each time they log in to itris, you can tick to allow them to save their password in the itris Launcher (log in).
In this area, you can set the default communication types to use when creating new records or new communication entries. The options available in the drop-down for each are set in the IMU Data section, please see the related article for more information.
Regardless of which options are set below for web address, if itris detects the web address is LinkedIn, it will overwrite the default option.
itris will allow those users with permissions to manage all stages of agreeing terms with your client from the Terms area of any company record.
Terms of business are commonplace in any business relationship, and the recruitment industry is no exception. Generally, every time business is conducted between two parties, terms of business will be agreed to, and in most cases, this will be the supplier’s standard terms and conditions. However, in some cases, the terms may be negotiated on a per-customer basis.
Here you can add details around your terms, multiple term documents and set standard Rebate stages, by days, weeks or months, or set to No Stages.
You can also set the default Fee. This can be a fixed fee, a Scale or Flat fee.
A fixed fee will be a set percentage
A Scale allows you to account for changes in the fee dependent on the salary.
A Flat fee is a value (e.g. in £) as opposed to a percentage, whereby the salary has no impact on the fee.
When applying terms to a company record, it will automatically populate using the settings added, with the exception of the terms document. The Terms document will be available as a centralised resource for emails.
Rebates added to a company record will, in turn, be inherited onto fixed fee placements.
You, of course don’t have to apply these defaults to the record if you have a different agreement with them.
When performing text searches, SQL Server naturally omits certain characters to streamline full-text searching.
This includes numbers, single characters, symbols, and basically anything in the Unicode dictionary. So for example, when searching CVs for 'R', ‘C#’ or ‘C++’, SQL Server will remove these and treat them as if they do not exist.
Special words are therefore used to force SQL Server to include these when performing a full-text search and this is done by creating a catalogue in the database, essentially telling SQL Server that it is actually a word.