Mark

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This entry is about our IPS Community Suite 4.2 release
 
Top Members
For 4.2 we made some improvements to the Top Members section of the Leaderboard. A new overview page tab shows a selection of the top members across different criteria.

Top Members Overview Page showing members with Most Reputation and Most Content
The filter menu allows you to view more members in any chosen category, and a new AdminCP setting controls which categories should be available.

Top Members Categories
In the AdminCP you can configure which categories are shown on the overview page, the filter menu, and how many results show for each.

Top Members AdminCP Settings
 
Popular Contributors Widget
Another small change is the Popular Contributors widget now contains a link to the appropriate section of the Leaderboard.

Popular Contributors Widget

This is an entry about our IPS Community Suite 4.2 release.
You are probably already familiar with our content embedding feature in IPS Community Suite. When a link to content in the community is pasted into the editor (e.g. a topic, or a post, or a gallery image, etc.) it is automatically expanded into a preview of the content, usually with an accompanying image, allowing users to click through to that content if they are interested.

An embedded Gallery image in IPS Community Suite 4.1
While it has proved a useful feature to members, each embed used essentially the same structure - a small thumbnail on the left, a title, and a few lines of text. This works fine for topics, but isn't ideal for other kinds of rich content that might be posted.
In IPS Community Suite 4.2, we greatly improved upon our embedding handling, giving every type of content within every application its own customized embed style, allowing that content to be displayed however works best. This means larger high-res previews of Gallery images, a button to download a file right from the embed for Downloads files, showing a map for Calendar events, and so on. We worked to keep a consistent overall style between apps, but allow each to display its own relevant information.
For users, things will work exactly as they do now - they simply paste a link to content, and it will continue to expand automatically. The changes are also backwards compatible. Any existing embeds in your community will automatically show the new styling you see below - no rebuilding necessary.
So with that in mind, let's take a look what the new embeds look like! I won't show every single embed here because there's a huge number, but I'll try and give you a feel for how we approached the embed styles for each app.

Gallery Image

Comment on a Gallery Image

Gallery Album

Forum Topic

Downloads File

Review on a Downloads File

Calendar Event

Comment on a Calendar Event

Commerce Product

Record from a Pages database
I hope that gives you a good overview of what to expect when your users try out the new embeds for themselves. As always, please share your feedback in the comments below!
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification
 

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release
IPS Community Suite has supported drag and drop uploading to the attachments area at the bottom of the editor since 4.0. In 4.2 we're pleased to add the ability to drag and drop right into the editor, so you can drop your attachment exactly where you want it to show without having to add it afterwards.

Drag and drop into editor
If your browser and OS supports it you can also copy and paste, either from the desktop or from other content on the web:

Copy and Paste
Naturally this works for ordinary files as well as images:

Drag and drop a file
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device
 

This entry is about our IPS Community Suite 4.2 release.
One of our more technically-oriented features for 4.2, we have added more detailed logs of user logins, and the devices and IP addresses used. This brings several new features:
 
Notification of a new device sign in
If enabled, users can receive an email notification when a new device is used to log into their account:
 

Email sent when a login from a new device is detected
When a user signs in for the first time, a special key is set to recognise the browser on subsequent logins. This mean the notification email does not trigger on a new IP address, which would be annoying when travelling or if using a network where the IP address changes regularly. Instead, the notification is only triggered if someone signs into your account from a new physical device or web browser.
 
UserCP Device Management
If enabled, a new page will show in the user's settings page showing all the devices which have been used to log into their within the last 90 days (which is recent enough that could still be logged in if "Remember Me" was checked).

Recently Used Devices
Users can see the device, browser, physical location (obtained by a GeoIP lookup) and if applicable, how the login was processed (for example, if the sign in was with Facebook or Twitter, this will show). If they chose "Remember Me" when logging in, they can undo that (handy if you realise you accidentally left yourself signed in on a public computer).
If they see anything they don't recognise, a page to walk them through the necessary steps to re-secure their account is available.

Secure Account Information
 
New Two-Factor Authentication Setting
"Logging into the front-end" is one of the options of when to prompt for Two Factor Authentication. In 4.2, this has been separated into two distinct settings:
Logging into the front-end from a new device Logging into the front-end from a known device If you enable the former, but not the latter, and the user has previously logged in devices, the system will automatically show an explanation to users alongside the other available recovery option. This can be useful especially if you do not want to offer other recovery options.
 
AdminCP Device Management
In the AdminCP, administrators can see all the device and IPs a member has used. They can also disable automatic login for any device.
 

Edit member page shows most recently used device and IP address
 
 
Viewing a device's details
The system can also detect if another user is using the same device and will show this in the list of devices.
  
Users sharing the same device