Matt

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

I've said before that when I visit a new website, I often look for a link to their community.
It's not uncommon for some brands to have a link to their Twitter account and Facebook page, with a hashtag they'd like you to use when discussing their products.
That is an audience, not a community.
A true community encourages group conversation and empowers people to contribute ideas, promotion, content and support.
A community gives its members a true sense of belonging and more importantly it provides a sense of identity.
A community is an ongoing dialogue between you and your customers. It allows you to nurture and grow relationships far beyond what is possible with a hashtag on Twitter.
Now consider an audience. Let's say you and 500 other people go to a venue to watch a stand-up comic perform. There may be a little interaction between the comic and the audience, but you are there to be quiet and listen. When the show is over, you go home.

Now imagine that instead of going home after the show, you all spend a while talking about the show and the comic. You talk about which bits you enjoyed and which bits made you laugh the most. You compare this comic with other favourites. You share video clips and jokes.
This is a community.
An audience will follow you and consumes what you broadcast, but it is a one-dimensional relationship. Consider the case of Lush Cosmetics, who earlier this year removed their Facebook Group and replaced their community with a Twitter feed and an app "where the latest digital experiments unfold".
I feel this is a missed opportunity to bring customers together to talk about Lush products, share tips, reviews and builder a stronger relationship with Lush.
I've also seen startups trying to build a community on Instagram with a hashtag. They tend to search popular hashtags in their business niche and attempt to befriend individuals who are active with those hashtags intending to broadcast their information. This is all fine, but they are just curating an audience.
A community is more than a list of followers, and it's impossible to control what content is tagged with hashtags. Just ask McDonalds who quickly realised this with their 'McDStories' campaign.

What do you think? Let me know below.

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

Security should never be an afterthought. Don't wait until an attack has compromised your site before you take action.
All too often, site owners consider increasing their security only when it's too late, and their community has already been compromised.
Taking some time now to check and improve the security of your community and server will pay dividends.
In this blog, we run down 8 ways that you can protect your community with Invision Community. We go through the security features you may not know about to best practices all communities should be following.
1. Set up Two Factor Authentication
Invision Community supports Two Factor Authentication (2FA for short), and we highly recommend making use of this feature for your users, but especially for your administrative staff.
2FA is a system that requires both a user's password and a special code (displayed by a phone app) that changes every few seconds. The idea is simple: if a user's password is somehow compromised, a hacker still wouldn't be able to log in to the account without the current code number.
You may already be familiar with 2FA from other services you use. Apple's iCloud, Facebook and Google all offer it, as do thousands of banks and other security-conscious businesses.
Invision Community supports 2FA via the Google Authenticator app (available for iOS and Android) or the Authy service, which can send codes to users via text message or phone call. You can also fall back to security questions instead of codes.
You can configure which members groups can use 2FA, as well as requiring certain groups to use it. 
Recommendation: Require any staff with access to the Admin Control Panel or moderation functions to use 2FA. This will ensure that no damage will occur should their account passwords be discovered. Allow members to use 2FA at their discretion.
2. Configure password requirements
The password strength feature displays a strength meter to users as they type a new password. The meter shows them approximately how secure it is, as well as some tips for choosing a good password.
While you can leave this feature as a simple recommendation for users, it's also possible to require them to choose a password that reaches a certain strength on the meter. 
Recommendation: Require users to choose at least a 'Strong' password.

3. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Giving access to the AdminCP is like handing someone the keys to your house. Before doing so, be sure you trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Recommendation: Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have Administrative access by clicking the Administrators button under staff on the Members tab.
4. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. 
Invision Community allows you to limit administrator access to particular areas of the AdminCP with the Admin Restrictions feature, and even limit what can is done within those areas.
This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
Recommendation: Review the restrictions your admins currently have. 
5. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application, such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for other sites too.
Recommendation: Reset your password regularly and ensure you do not use the same password elsewhere.

6. Stay up to date
It's a fact of software development that from time to time, new security issues are reported and promptly fixed.
But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update promptly.
Invision Community allows you to update to the latest version via the AdminCP. You no longer need to download a thing!
Recommendation: Update to the latest version whenever possible. Remember, with Invision Community's theme and hook systems, upgrades to minor point releases should be very straight forward.
7. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist.
This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment.
Recommendation: Consider IP restriction as an additional security layer when you are not able or willing to use 2FA.
8. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We, therefore, recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled. Especially if you're hosted on a server that also hosts other websites (known as shared hosting), if another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Cloud customers needn't worry about this, we've already ensured our cloud infrastructure is impervious to this kind of attack.
Recommendation: Review your PHP version and settings, or choose one of our cloud plans where we take care of this for you.
So there we go - a brief overview of 8 common-sense ways you can better protect your community and its users.
As software developers, we're constantly working to improve the behind-the-scenes security of our software. As an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!
 

The term "flame-wars" was coined way back in the 1970s when computer scientists talking in the first electronic discussion boards noticed that here was "an escalation of critical comments and an increase in the frequency with which people would respond with short negative messages."
For anyone that has ventured into the comment section of Youtube, read Twitter for more than a few minutes or frequented active forums will know that our behaviour hasn't improved.
Sherry Turkle, Ph.D., a psychologist and professor at MIT, conducted hundreds of interviews over 15 years and found that "we allow ourselves behaviours online we never would in person." These interactions aren't just restricted to strangers on social media as Turkle notes that "we do things online that hurt and damage real relationships".
Why is this?
Tom Sander, executive director of the Saguaro Seminar project on civic engagement at the Harvard Kennedy School, explains that having the ability to be anonymous "can be a real attraction if no one knows you have a drinking problem or depression.
The Internet can be useful in allowing people to anonymously 'come out' about their problems and get support. But it is also an Achilles heel. If people don't know who you are, you are much more likely to say things in a nasty or snarky tone.
In general, we invest less in our reputation in online groups because it is easier to exit them and join other groups. In real space, if you don't get along with your neighbour, you're less likely to say something really nasty, because moving out of town is costly."
A lot of toxicity is from those who just like hearing themselves talk, or feel better when they put others down. Some people think they are clever and witty by using sarcasm and pointing out the flaws in another's argument.

Here's a few ways to manage negativity in your community.
Model your ideal behaviour
The simplest and most effective way to manage negativity in your community is to be the behaviour you seek.
Ensure your replies and friendly and polite. Be fun where appropriate and learn about your regular members. Make sure your team is visible and post regularly so the community feels well run and someone is on hand to deal with issues when they arise.
Your community will follow suit and replicate your behaviour. When your community is positive and helpful, toxicity and negativity find it very hard to get a foothold. Your members will weed it out and correct those members for you.
Have clear guidelines
Socious's Senior Director of Community Management, Katie Bapple advises moderators not to be impulsive when dealing with toxic members.
"Controversial community members should not be dealt with compulsively; have reasonable guidelines and policies in place that draw a clear line, so you know when it's been crossed."
A clear and well-written community guidelines document won't stop trouble from occurring, but it will provide your team with clear boundaries and protocols to follow.
Have a light touch with moderation tools
It's easy to reach for the moderation tools when you see toxic or very harmful posts in a topic. It only takes a few clicks, and you can remove it from view and pretend it didn't happen.
However, much like a child trying to get his parent's attention, the more you try and silence them, the louder and more insistent they will be to get heard. They'll very likely return more inflamed and vitriolic than before.
Unless the content crosses the boundaries you have set for your community; it is often more productive to post a polite reply gently guiding the discussion back on track and thank contributors for their input so far.
If this doesn't de-escalate the situation, then:
Make it private
Open a dialogue with the offender to try and calm the situation. Often this act alone makes the member feel valued and transforms them into a happy and productive member of the community.
Just remind them of the boundaries set out in your community guidelines.
At least you will stop the member from continuing to post in public areas and derailing topics.
Use the appropriate moderation tool
Invision Community is packed with tools to help manage toxicity and negativity. However, reaching right for the ban button may not be the best course of action.
Consider a warning, which the member must acknowledge before posting again. Keep it friendly and polite and to the point. If the behaviour continues, then consider a short term block. Often an enforced 48 hours away from the community is enough to regain some perspective.
Don't assume it'll go away
The truth is people love drama, and most people are drawn towards negativity. We can't help but look when we come across a vehicle accident, and sadly, it's largely the same in a community.
It might be tempting to keep on scrolling and hope that it all sorts itself out. Likely, it won't, and intervention will be required. That might be a polite, friendly reminder to get the topic back on track, or contacting the member in private.
Either way, the best approach is to nip it in the bud with a light touch before it spins out of control, and more forceful action is required.
You can't please everyone
It should be a last resort, but your community may not be a good fit for everyone. If that is the case, then you can consider a permanent ban, or demoting the member into a read-only member group.

Ultimately though negativity and toxicity are pretty rare in an upbeat and productive community. Most quarrels are fixed quickly, and it's rare to find a troll determined to corrupt your community.
Identify your boundaries and educate your community on what is not acceptable and be proactive when issues arise, and you'll keep sentiment positive.
If you run your own community, I'd love to know what tips you can share on dealing with negativity and toxicity. Let me know below.

The term "flame-wars" was coined way back in the 1970s when computer scientists talking in the first electronic discussion boards noticed that here was "an escalation of critical comments and an increase in the frequency with which people would respond with short negative messages."
For anyone that has ventured into the comment section of Youtube, read Twitter for more than a few minutes or frequented active forums will know that our behaviour hasn't improved.
Sherry Turkle, Ph.D., a psychologist and professor at MIT, conducted hundreds of interviews over 15 years and found that "we allow ourselves behaviours online we never would in person." These interactions aren't just restricted to strangers on social media as Turkle notes that "we do things online that hurt and damage real relationships".
Why is this?
Tom Sander, executive director of the Saguaro Seminar project on civic engagement at the Harvard Kennedy School, explains that having the ability to be anonymous "can be a real attraction if no one knows you have a drinking problem or depression.
The Internet can be useful in allowing people to anonymously 'come out' about their problems and get support. But it is also an Achilles heel. If people don't know who you are, you are much more likely to say things in a nasty or snarky tone.
In general, we invest less in our reputation in online groups because it is easier to exit them and join other groups. In real space, if you don't get along with your neighbour, you're less likely to say something really nasty, because moving out of town is costly."
A lot of toxicity is from those who just like hearing themselves talk, or feel better when they put others down. Some people think they are clever and witty by using sarcasm and pointing out the flaws in another's argument.

Here's a few ways to manage negativity in your community.
Model your ideal behaviour
The simplest and most effective way to manage negativity in your community is to be the behaviour you seek.
Ensure your replies and friendly and polite. Be fun where appropriate and learn about your regular members. Make sure your team is visible and post regularly so the community feels well run and someone is on hand to deal with issues when they arise.
Your community will follow suit and replicate your behaviour. When your community is positive and helpful, toxicity and negativity find it very hard to get a foothold. Your members will weed it out and correct those members for you.
Have clear guidelines
Socious's Senior Director of Community Management, Katie Bapple advises moderators not to be impulsive when dealing with toxic members.
"Controversial community members should not be dealt with compulsively; have reasonable guidelines and policies in place that draw a clear line, so you know when it's been crossed."
A clear and well-written community guidelines document won't stop trouble from occurring, but it will provide your team with clear boundaries and protocols to follow.
Have a light touch with moderation tools
It's easy to reach for the moderation tools when you see toxic or very harmful posts in a topic. It only takes a few clicks, and you can remove it from view and pretend it didn't happen.
However, much like a child trying to get his parent's attention, the more you try and silence them, the louder and more insistent they will be to get heard. They'll very likely return more inflamed and vitriolic than before.
Unless the content crosses the boundaries you have set for your community; it is often more productive to post a polite reply gently guiding the discussion back on track and thank contributors for their input so far.
If this doesn't de-escalate the situation, then:
Make it private
Open a dialogue with the offender to try and calm the situation. Often this act alone makes the member feel valued and transforms them into a happy and productive member of the community.
Just remind them of the boundaries set out in your community guidelines.
At least you will stop the member from continuing to post in public areas and derailing topics.
Use the appropriate moderation tool
Invision Community is packed with tools to help manage toxicity and negativity. However, reaching right for the ban button may not be the best course of action.
Consider a warning, which the member must acknowledge before posting again. Keep it friendly and polite and to the point. If the behaviour continues, then consider a short term block. Often an enforced 48 hours away from the community is enough to regain some perspective.
Don't assume it'll go away
The truth is people love drama, and most people are drawn towards negativity. We can't help but look when we come across a vehicle accident, and sadly, it's largely the same in a community.
It might be tempting to keep on scrolling and hope that it all sorts itself out. Likely, it won't, and intervention will be required. That might be a polite, friendly reminder to get the topic back on track, or contacting the member in private.
Either way, the best approach is to nip it in the bud with a light touch before it spins out of control, and more forceful action is required.
You can't please everyone
It should be a last resort, but your community may not be a good fit for everyone. If that is the case, then you can consider a permanent ban, or demoting the member into a read-only member group.

Ultimately though negativity and toxicity are pretty rare in an upbeat and productive community. Most quarrels are fixed quickly, and it's rare to find a troll determined to corrupt your community.
Identify your boundaries and educate your community on what is not acceptable and be proactive when issues arise, and you'll keep sentiment positive.
If you run your own community, I'd love to know what tips you can share on dealing with negativity and toxicity. Let me know below.

The term "flame-wars" was coined way back in the 1970s when computer scientists talking in the first electronic discussion boards noticed that here was "an escalation of critical comments and an increase in the frequency with which people would respond with short negative messages."
For anyone that has ventured into the comment section of Youtube, read Twitter for more than a few minutes or frequented active forums will know that our behaviour hasn't improved.
Sherry Turkle, Ph.D., a psychologist and professor at MIT, conducted hundreds of interviews over 15 years and found that "we allow ourselves behaviours online we never would in person." These interactions aren't just restricted to strangers on social media as Turkle notes that "we do things online that hurt and damage real relationships".
Why is this?
Tom Sander, executive director of the Saguaro Seminar project on civic engagement at the Harvard Kennedy School, explains that having the ability to be anonymous "can be a real attraction if no one knows you have a drinking problem or depression.
The Internet can be useful in allowing people to anonymously 'come out' about their problems and get support. But it is also an Achilles heel. If people don't know who you are, you are much more likely to say things in a nasty or snarky tone.
In general, we invest less in our reputation in online groups because it is easier to exit them and join other groups. In real space, if you don't get along with your neighbour, you're less likely to say something really nasty, because moving out of town is costly."
A lot of toxicity is from those who just like hearing themselves talk, or feel better when they put others down. Some people think they are clever and witty by using sarcasm and pointing out the flaws in another's argument.

Here's a few ways to manage negativity in your community.
Model your ideal behaviour
The simplest and most effective way to manage negativity in your community is to be the behaviour you seek.
Ensure your replies and friendly and polite. Be fun where appropriate and learn about your regular members. Make sure your team is visible and post regularly so the community feels well run and someone is on hand to deal with issues when they arise.
Your community will follow suit and replicate your behaviour. When your community is positive and helpful, toxicity and negativity find it very hard to get a foothold. Your members will weed it out and correct those members for you.
Have clear guidelines
Socious's Senior Director of Community Management, Katie Bapple advises moderators not to be impulsive when dealing with toxic members.
"Controversial community members should not be dealt with compulsively; have reasonable guidelines and policies in place that draw a clear line, so you know when it's been crossed."
A clear and well-written community guidelines document won't stop trouble from occurring, but it will provide your team with clear boundaries and protocols to follow.
Have a light touch with moderation tools
It's easy to reach for the moderation tools when you see toxic or very harmful posts in a topic. It only takes a few clicks, and you can remove it from view and pretend it didn't happen.
However, much like a child trying to get his parent's attention, the more you try and silence them, the louder and more insistent they will be to get heard. They'll very likely return more inflamed and vitriolic than before.
Unless the content crosses the boundaries you have set for your community; it is often more productive to post a polite reply gently guiding the discussion back on track and thank contributors for their input so far.
If this doesn't de-escalate the situation, then:
Make it private
Open a dialogue with the offender to try and calm the situation. Often this act alone makes the member feel valued and transforms them into a happy and productive member of the community.
Just remind them of the boundaries set out in your community guidelines.
At least you will stop the member from continuing to post in public areas and derailing topics.
Use the appropriate moderation tool
Invision Community is packed with tools to help manage toxicity and negativity. However, reaching right for the ban button may not be the best course of action.
Consider a warning, which the member must acknowledge before posting again. Keep it friendly and polite and to the point. If the behaviour continues, then consider a short term block. Often an enforced 48 hours away from the community is enough to regain some perspective.
Don't assume it'll go away
The truth is people love drama, and most people are drawn towards negativity. We can't help but look when we come across a vehicle accident, and sadly, it's largely the same in a community.
It might be tempting to keep on scrolling and hope that it all sorts itself out. Likely, it won't, and intervention will be required. That might be a polite, friendly reminder to get the topic back on track, or contacting the member in private.
Either way, the best approach is to nip it in the bud with a light touch before it spins out of control, and more forceful action is required.
You can't please everyone
It should be a last resort, but your community may not be a good fit for everyone. If that is the case, then you can consider a permanent ban, or demoting the member into a read-only member group.

Ultimately though negativity and toxicity are pretty rare in an upbeat and productive community. Most quarrels are fixed quickly, and it's rare to find a troll determined to corrupt your community.
Identify your boundaries and educate your community on what is not acceptable and be proactive when issues arise, and you'll keep sentiment positive.
If you run your own community, I'd love to know what tips you can share on dealing with negativity and toxicity. Let me know below.

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

The term "flame-wars" was coined way back in the 1970s when computer scientists talking in the first electronic discussion boards noticed that here was "an escalation of critical comments and an increase in the frequency with which people would respond with short negative messages."
For anyone that has ventured into the comment section of Youtube, read Twitter for more than a few minutes or frequented active forums will know that our behaviour hasn't improved.
Sherry Turkle, Ph.D., a psychologist and professor at MIT, conducted hundreds of interviews over 15 years and found that "we allow ourselves behaviours online we never would in person." These interactions aren't just restricted to strangers on social media as Turkle notes that "we do things online that hurt and damage real relationships".
Why is this?
Tom Sander, executive director of the Saguaro Seminar project on civic engagement at the Harvard Kennedy School, explains that having the ability to be anonymous "can be a real attraction if no one knows you have a drinking problem or depression.
The Internet can be useful in allowing people to anonymously 'come out' about their problems and get support. But it is also an Achilles heel. If people don't know who you are, you are much more likely to say things in a nasty or snarky tone.
In general, we invest less in our reputation in online groups because it is easier to exit them and join other groups. In real space, if you don't get along with your neighbour, you're less likely to say something really nasty, because moving out of town is costly."
A lot of toxicity is from those who just like hearing themselves talk, or feel better when they put others down. Some people think they are clever and witty by using sarcasm and pointing out the flaws in another's argument.

Here's a few ways to manage negativity in your community.
Model your ideal behaviour
The simplest and most effective way to manage negativity in your community is to be the behaviour you seek.
Ensure your replies and friendly and polite. Be fun where appropriate and learn about your regular members. Make sure your team is visible and post regularly so the community feels well run and someone is on hand to deal with issues when they arise.
Your community will follow suit and replicate your behaviour. When your community is positive and helpful, toxicity and negativity find it very hard to get a foothold. Your members will weed it out and correct those members for you.
Have clear guidelines
Socious's Senior Director of Community Management, Katie Bapple advises moderators not to be impulsive when dealing with toxic members.
"Controversial community members should not be dealt with compulsively; have reasonable guidelines and policies in place that draw a clear line, so you know when it's been crossed."
A clear and well-written community guidelines document won't stop trouble from occurring, but it will provide your team with clear boundaries and protocols to follow.
Have a light touch with moderation tools
It's easy to reach for the moderation tools when you see toxic or very harmful posts in a topic. It only takes a few clicks, and you can remove it from view and pretend it didn't happen.
However, much like a child trying to get his parent's attention, the more you try and silence them, the louder and more insistent they will be to get heard. They'll very likely return more inflamed and vitriolic than before.
Unless the content crosses the boundaries you have set for your community; it is often more productive to post a polite reply gently guiding the discussion back on track and thank contributors for their input so far.
If this doesn't de-escalate the situation, then:
Make it private
Open a dialogue with the offender to try and calm the situation. Often this act alone makes the member feel valued and transforms them into a happy and productive member of the community.
Just remind them of the boundaries set out in your community guidelines.
At least you will stop the member from continuing to post in public areas and derailing topics.
Use the appropriate moderation tool
Invision Community is packed with tools to help manage toxicity and negativity. However, reaching right for the ban button may not be the best course of action.
Consider a warning, which the member must acknowledge before posting again. Keep it friendly and polite and to the point. If the behaviour continues, then consider a short term block. Often an enforced 48 hours away from the community is enough to regain some perspective.
Don't assume it'll go away
The truth is people love drama, and most people are drawn towards negativity. We can't help but look when we come across a vehicle accident, and sadly, it's largely the same in a community.
It might be tempting to keep on scrolling and hope that it all sorts itself out. Likely, it won't, and intervention will be required. That might be a polite, friendly reminder to get the topic back on track, or contacting the member in private.
Either way, the best approach is to nip it in the bud with a light touch before it spins out of control, and more forceful action is required.
You can't please everyone
It should be a last resort, but your community may not be a good fit for everyone. If that is the case, then you can consider a permanent ban, or demoting the member into a read-only member group.

Ultimately though negativity and toxicity are pretty rare in an upbeat and productive community. Most quarrels are fixed quickly, and it's rare to find a troll determined to corrupt your community.
Identify your boundaries and educate your community on what is not acceptable and be proactive when issues arise, and you'll keep sentiment positive.
If you run your own community, I'd love to know what tips you can share on dealing with negativity and toxicity. Let me know below.

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

Emotion is energy in motion.
Today’s article is the last element in our Sense of Community series, and it’s also the most powerful.  It allows new communities to win over legacy ones; niche communities to triumph over generic platforms; and impassioned communities to outlast everyone.  It’s also the hardest element to cultivate. 
What is it? 
According to a survey by psychologist Dr. Jenny Fremlin, shared emotional connection accounts for the single largest factor of community-building.  In fact, almost half of all respondents in her research identified shared emotional connection as the factor most important to their community. 
How do you cultivate the principle of shared emotional connection?  
New Members
For new members, your goal is to initiate them in your community’s rituals and connect them with other outstanding members who will help reinforce your community’s spirit.   
Induction – Joining your community should be the beginning of a member’s community story, which means leaving a part of himself behind and fostering a new selfhood for your community.  Make induction an important part of onboarding a new member.  Honor his new membership with community gifts.  Require him to fulfill rituals that are unique to your community.  Demand that he open himself to the community, the challenges he faces, and what he hopes to receive.  By doing so, you are asking the new member to invest a part of their emotional selves in the community from the very beginning. 
Greater Contact – The more that people interact, the more likely they are to bond.  Just like in the real world when a new visitor walks into a room and no one talks to him, he’s likely to leave.  But if you can introduce him to other members, invite him to a table with other new members who also recently joined, or connect him with a mentor, then he’s more likely to stay.  You can accomplish the same in your community.  Connect members as much as possible, which spark new friendships. 
Existing Members
For existing members, deepen their sense of shared emotional connection with these strategies.
Community Story – Develop a story for your community, a narrative that is being written by and for members.  It brings all members together in a common sense of history, and even though not all members may have participated the entire time, they identify with the story.  Why was your community founded? Are you tackling a challenge in the world?  Did you undergo a major obstacle? Are you aspiring to improve the world? Where are you going? Write down your past, present, and future and invite members into the living story of your community. 
Community Projects – All too often, community admins launch projects on their own or with an inner circle of staff.  Launch a project that’s open to everyone, where all members can participate, give feedback, and contribute.  Define a beginning and end to the project, which helps members with closure and remembrance (“Did you remember the time when we helped on XYZ project?”) .
Industry Changes – What are disruptions that are happening in your field or industry? Is it affecting anyone you know? How do you feel about it?  Is it positive or negative?  How significant is the change? Use these shared events to get people disclosing their emotions about these disruptions, which helps form an emotional connection with others who are experiencing the same.  The strongest bonds are among people who undergo a crisis together.    
Honor & Humiliation – Finally, the personal growth of members is punctuated by the highs and lows of their membership from rewards that highlight special achievement to penalties that discipline bad behavior.  These moments of recognition and humiliation unlock joy and pain, which emotionally bond the member to your community.  The strongest emotional bonds are experienced by those who traverse the greatest emotional journey – they come to your community as immature or inexperienced, and through rewards and moderation, grow to become a better person through your community. 

Members visit your community for all sorts of reasons.  But out of all reasons, one stands above all others: shared emotional connection. 
There’s no one way to cultivating a shared emotional connection.  Every community will be unique. You and your Invision Community must write your own individual story, cultivate your own special volkgeist, and honor and humiliate members in your own extraordinary way. The energy and emotion of your community will be uniquely yours.  
In the end, you want to foster your own “community of spirit” among members, an exceptional sense of purpose and friendship wrapped in shared emotion that no other community can match.

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

When your customers buy or use your products, they will have many questions. They may have issues using the product, or they may have requests for future versions based on their needs.
Managing and responding to those questions and requests quickly increases conversion, satisfaction and the likelihood or purchasing again.
The statistics back this up.

There is no doubt that unless you have a support community for your brand,  you are not delivering the best experience for your customers and risk losing them to competitors that do.
Building a support community around your product or service will positively drive your business across all departments from product development through sales and into customer support.
Let's break it down and look at the key benefits for each department.
Customer Service
Encouraging your customers to visit your support community is the simplest way to reduce the cost of supporting your product or service. Creating a self-help culture allows other more experienced customers to offer assistance and troubleshoot any problems they have.
73% of customers fall in love with a brand because of friendly customer service representatives.**
Quite often, new customers encounter the same issues that would flood customer support if they were all channelled to your support desk. For example, consider a company that produces an internet-enabled smart device. Less technically savvy customers will likely contact support to troubleshoot initial connectivity issues which can quickly be resolved by peers in the support community.
These questions and answers form a crowdsourced knowledge base that will allow customers to help themselves without any intervention from your team. Furthermore, these questions will feature in external search results, driving more traffic to your site.

Sales
The primary purpose of your community may have initially been to help support your customers, but it quickly becomes a valuable resource to help drive sales.
Your support community will be a relaxed place where customers talk to each other honestly and openly. They will be less inhibited than they would if they were talking to your sales agents.
Customers might be discussing a need for more functionality that you have in another product or service. Your sales team can move these conversations from the community to your CRM to curate new sales leads.
72% of customers will tell 6 people or more if they have a satisfying experience. - Esteban Kolsky
Customers that have had positive interactions with their peers and members of your support team will become advocates for your brand. They will help sell your product over social media and among their friend circles. Given than 90% of customers are influenced by a positive review when buying a product*, having brand advocates is critical to your growth.

Marketing
There are several costly routes to learning about your customers and their wants and needs. You can conduct external surveys, or pay for research groups to look at your products and offer feedback.
56% of customers don't mind sharing their personal information in exchange for better service.**
The most effective method is to look at your community.
Your customers will be posting their thoughts daily. They'll tell you exactly how they use your products, offering you valuable insight into the problems they are solving with your product. This information should be used as the basis of new marketing campaigns.

Project Development
Your support community is a direct line to your customers. You no longer need to use external tools and services to determine which features you should add next. You'll be told directly!
55% of customers are willing to spend more money with a company that guarantees them a satisfying experience.**
You'll find that some feature requests bubble up regularly. These are the ones you will want to move to your product roadmap.
Invision Community allows you to segment your community into private areas for beta testing. Your developers can interact with this group to work directly with your customers to shape new functionality.
Harnessing analytical data will inform development decisions. Invision Community can track keywords in user-generated content. If you have released a new feature, you can track how often it is mentioned in conversations to monitor its uptake.
52% of customers believe that companies need to take action on their feedback.*

Setting up your Invision Community
Now we've looked at the compelling reasons you should create a support community around your products, let's take a look at how to set up your Invision Community.
Support Desk
Invision Community has a fully-featured built in support desk functionality. Commerce has all the features you need, including multiple support desk categories, reply by email, pre-written reply templates and private notes.

 
However, if you already use another support desk such as Zendesk then our API tools mean that Invision Community can integrate with your existing support flow seamlessly.
Keyword Tracking
Invision Community allows you to track how often specific words or phrases. This is useful to monitor which of your products are trending or monitoring uptake on new features.
To set this up, visit the Statistics section of the Admin CP.
Question and Answers
To formalize a support or ideation area within your support community, Invision Community offers a Question and Answer forum type.
Question and Answer forum types allow your members to post questions and enable other members to upvote the questions and replies. Your support team can also flag specific responses as the "best answer" which turns historical questions into a crowdsourced knowledge base.
Showcasing Great Content
Invision Community has several tools to highlight great customer-created content. You can pin topics, and feature specific replies within those topics.
You can also convert posts into new articles within a formal knowledge base or blog to further help your customers find the right answers to their questions.
Extensibility
Invision Community has OAuth and a REST API out of the box. This means it's trivial to extend Invision Community to work within your existing flows. Integrate Invision Community to your SalesForce CRM and Zendesk support systems seamlessly.
Create a federated search to integrate your external knowledge base with client-generated knowledge.
The options are limitless, and we can take care of any custom integrations for you.
If you have any questions, please let me know below, or contact us to see how we can help you harness the power of community for your business.
* https://www.customerthermometer.com/customer-service/customer-service-and-satisfaction-statistics-for-2019/
** https://www.qminder.com/customer-service-statistics/

I've said before that when I visit a new website, I often look for a link to their community.
It's not uncommon for some brands to have a link to their Twitter account and Facebook page, with a hashtag they'd like you to use when discussing their products.
That is an audience, not a community.
A true community encourages group conversation and empowers people to contribute ideas, promotion, content and support.
A community gives its members a true sense of belonging and more importantly it provides a sense of identity.
A community is an ongoing dialogue between you and your customers. It allows you to nurture and grow relationships far beyond what is possible with a hashtag on Twitter.
Now consider an audience. Let's say you and 500 other people go to a venue to watch a stand-up comic perform. There may be a little interaction between the comic and the audience, but you are there to be quiet and listen. When the show is over, you go home.

Now imagine that instead of going home after the show, you all spend a while talking about the show and the comic. You talk about which bits you enjoyed and which bits made you laugh the most. You compare this comic with other favourites. You share video clips and jokes.
This is a community.
An audience will follow you and consumes what you broadcast, but it is a one-dimensional relationship. Consider the case of Lush Cosmetics, who earlier this year removed their Facebook Group and replaced their community with a Twitter feed and an app "where the latest digital experiments unfold".
I feel this is a missed opportunity to bring customers together to talk about Lush products, share tips, reviews and builder a stronger relationship with Lush.
I've also seen startups trying to build a community on Instagram with a hashtag. They tend to search popular hashtags in their business niche and attempt to befriend individuals who are active with those hashtags intending to broadcast their information. This is all fine, but they are just curating an audience.
A community is more than a list of followers, and it's impossible to control what content is tagged with hashtags. Just ask McDonalds who quickly realised this with their 'McDStories' campaign.

What do you think? Let me know below.

I've said before that when I visit a new website, I often look for a link to their community.
It's not uncommon for some brands to have a link to their Twitter account and Facebook page, with a hashtag they'd like you to use when discussing their products.
That is an audience, not a community.
A true community encourages group conversation and empowers people to contribute ideas, promotion, content and support.
A community gives its members a true sense of belonging and more importantly it provides a sense of identity.
A community is an ongoing dialogue between you and your customers. It allows you to nurture and grow relationships far beyond what is possible with a hashtag on Twitter.
Now consider an audience. Let's say you and 500 other people go to a venue to watch a stand-up comic perform. There may be a little interaction between the comic and the audience, but you are there to be quiet and listen. When the show is over, you go home.

Now imagine that instead of going home after the show, you all spend a while talking about the show and the comic. You talk about which bits you enjoyed and which bits made you laugh the most. You compare this comic with other favourites. You share video clips and jokes.
This is a community.
An audience will follow you and consumes what you broadcast, but it is a one-dimensional relationship. Consider the case of Lush Cosmetics, who earlier this year removed their Facebook Group and replaced their community with a Twitter feed and an app "where the latest digital experiments unfold".
I feel this is a missed opportunity to bring customers together to talk about Lush products, share tips, reviews and builder a stronger relationship with Lush.
I've also seen startups trying to build a community on Instagram with a hashtag. They tend to search popular hashtags in their business niche and attempt to befriend individuals who are active with those hashtags intending to broadcast their information. This is all fine, but they are just curating an audience.
A community is more than a list of followers, and it's impossible to control what content is tagged with hashtags. Just ask McDonalds who quickly realised this with their 'McDStories' campaign.

What do you think? Let me know below.

I've said before that when I visit a new website, I often look for a link to their community.
It's not uncommon for some brands to have a link to their Twitter account and Facebook page, with a hashtag they'd like you to use when discussing their products.
That is an audience, not a community.
A true community encourages group conversation and empowers people to contribute ideas, promotion, content and support.
A community gives its members a true sense of belonging and more importantly it provides a sense of identity.
A community is an ongoing dialogue between you and your customers. It allows you to nurture and grow relationships far beyond what is possible with a hashtag on Twitter.
Now consider an audience. Let's say you and 500 other people go to a venue to watch a stand-up comic perform. There may be a little interaction between the comic and the audience, but you are there to be quiet and listen. When the show is over, you go home.

Now imagine that instead of going home after the show, you all spend a while talking about the show and the comic. You talk about which bits you enjoyed and which bits made you laugh the most. You compare this comic with other favourites. You share video clips and jokes.
This is a community.
An audience will follow you and consumes what you broadcast, but it is a one-dimensional relationship. Consider the case of Lush Cosmetics, who earlier this year removed their Facebook Group and replaced their community with a Twitter feed and an app "where the latest digital experiments unfold".
I feel this is a missed opportunity to bring customers together to talk about Lush products, share tips, reviews and builder a stronger relationship with Lush.
I've also seen startups trying to build a community on Instagram with a hashtag. They tend to search popular hashtags in their business niche and attempt to befriend individuals who are active with those hashtags intending to broadcast their information. This is all fine, but they are just curating an audience.
A community is more than a list of followers, and it's impossible to control what content is tagged with hashtags. Just ask McDonalds who quickly realised this with their 'McDStories' campaign.

What do you think? Let me know below.

I've said before that when I visit a new website, I often look for a link to their community.
It's not uncommon for some brands to have a link to their Twitter account and Facebook page, with a hashtag they'd like you to use when discussing their products.
That is an audience, not a community.
A true community encourages group conversation and empowers people to contribute ideas, promotion, content and support.
A community gives its members a true sense of belonging and more importantly it provides a sense of identity.
A community is an ongoing dialogue between you and your customers. It allows you to nurture and grow relationships far beyond what is possible with a hashtag on Twitter.
Now consider an audience. Let's say you and 500 other people go to a venue to watch a stand-up comic perform. There may be a little interaction between the comic and the audience, but you are there to be quiet and listen. When the show is over, you go home.

Now imagine that instead of going home after the show, you all spend a while talking about the show and the comic. You talk about which bits you enjoyed and which bits made you laugh the most. You compare this comic with other favourites. You share video clips and jokes.
This is a community.
An audience will follow you and consumes what you broadcast, but it is a one-dimensional relationship. Consider the case of Lush Cosmetics, who earlier this year removed their Facebook Group and replaced their community with a Twitter feed and an app "where the latest digital experiments unfold".
I feel this is a missed opportunity to bring customers together to talk about Lush products, share tips, reviews and builder a stronger relationship with Lush.
I've also seen startups trying to build a community on Instagram with a hashtag. They tend to search popular hashtags in their business niche and attempt to befriend individuals who are active with those hashtags intending to broadcast their information. This is all fine, but they are just curating an audience.
A community is more than a list of followers, and it's impossible to control what content is tagged with hashtags. Just ask McDonalds who quickly realised this with their 'McDStories' campaign.

What do you think? Let me know below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Collecting, curating and organising ideas and feedback is a critical part of managing a community for a product.
Even though here at Invision Community, we have a relaxed approach to ideation, we do read and review ideas and feature requests that come into us via our support community and via emails and tickets and organise them off-site.


If you wanted to add more rigour to your ideation process, then Invision Community has built-in tools that you can use.
This video covers setting up a "Question & Answer" forum, which forms the basis for your ideation section along with using the built-in translation tools to tweak the interface language.
The complete process takes around five minutes and is the perfect way to collect and organise community ideas.
Once you have it set up, your community members can post their ideas and fellow community members can upvote their favourite suggestions, leave comments on ideas and even upvote and downvote replies inside the idea.
Let me know what you thought, and if you have any further questions below!

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.

Minor releases are almost always just maintenance releases. We gather up a fistful of bug reports and fix them to ensure that every month or so, our clients enjoy more stability and efficiency with Invision Community.
However, more recently we've noticed that we're running low on bug reports, so we've managed to squeeze in a handful of improvements in Invision Community 4.4.5.
Let's take a look and see what's new in Pages.
How should the canonical tag behave?
While this isn't the most exciting name for a feature, it does explain it reasonably well. We had a recent discussion on the forums where it was pointed out that the canonical tag directed search engines to the first page of any record. While this makes perfect sense for an articles or blog system where the content you create is more important than the comments, it makes less sense if the user-generated content (aka the comments) is more important than the content you put up. A good example here is where you put up a video or link for review. You don't want the canonical tag pointing to the first page as it will ignore the reviews themselves.

If you didn't understand much of that, don't worry. The idea behind this feature is to provide Google and friends with a better hint about which content is more important. A happier Google bot slurping your site is a good thing.
How about that Admin CP menu?
When you create a new database in Pages, it is shown in the ACP menu under 'Content'. This is fine, but when you get a lot of databases, it starts looking a little cluttered, and it can be hard to find the correct one.

We've reworked the menu so items have their own section, and can be re-ordered using the ACP menu re-ordering system.
Member fields are now filterable.
Pages allows specific field types to be filterable. This means you can sort by them with the table's advanced search box, and you can drag and drop a filters widget next to the table to refine the rows shown.
Now a member custom field is filterable, which is handy if you use them in your databases.
Other areas of the suite.
Messenger search
A while back, we made a change that removed the ability to search messenger by the sender or recipient name. We also limited the reach of the search system to one year and newer.

Unsurprisingly, this wasn't very popular. We've restored sender, and recipient name searching removed the one year limit and re-engineered the internals of search, so it's more efficient and returns results much faster.
How many members do you have?
You can see quite quickly if you have the member stats widget on the front end, but finding out via the Admin CP is a little more tricky. 

 
Until now! We've added a dashboard widget that not only shows the number of members you have registered, but also a break down of their email opt-in status.
A happier autocomplete.
Apple has this cool feature where if you receive a text message for a two-factor authentication login, it offers to auto-fill the code box for you.
We've had a sweep throughout the suite to ensure two-factor authentication fields allow this autocomplete to happen.
While we were at it, we made sure that other fields are more easily autocompleted.
That wraps up the new features in Invision Community 4.4.5. How many have you spotted after upgrading?
Let us know your favourite below.