Nintex offers a platform that helps companies discover, automate, and optimize business processes.
N/A
Teams Manager for Microsoft Teams
Score 7.7 out of 10
N/A
IT administrators can keep control of their Microsoft 365 environment with Teams Manager. Teams Manager is used to prevent the uncontrolled creation of Teams and Groups and automate governance processes. Key Features: • Governance Dashboard and Reports – provides an overview of the M365 environment (inactive or ownerless teams, teams with guests etc.) • Provisioning of new teams & SharePoint sites – with channels,…
$1,500
per year
Pricing
Nintex Process Platform
Teams Manager for Microsoft Teams
Editions & Modules
No answers on this topic
XL: more than 4,000 users
€ 1.50
per year per user
Small: 1 - 249 users
€ 1500
per year
Medium: 250 - 999 users
€ 3780
per year
Large: 1,000 - 4,000 users
€ 6050
per year
Offerings
Pricing Offerings
Nintex Process Platform
Teams Manager for Microsoft Teams
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Optional
$2,100 one-time fee
Additional Details
—
Information on Enterprise editions and Support packages can be found at the vendor's website.
Unfortunately I have not used other products that are similar to Nintex Process Platforms so it's impossible for me to compare it to any competitors. Not necessarily because of a lack of experience, but because Nintex has thus far continued to not only meet our current needs, …
Nintex is best suited when processes are drawed by the business and then can be furter enhanced by IT professionals. When only used by business units we see that there are some lose ends in processes and some bagic process knowledge is needed. Therefore it is wise that the persons in the business who will use Nintex have some basic knowledge on how to set up business processes
For different projects in a big organization different teams can be formed and thus their internal tasks assignments can be done there. It is easy to manage, assign tasks to people in a particular project. People or team leads in multiple projects can share different channels thus maintaining different projects. Users should be refrained of creating new teams just for fun purpose etc. to avoid to much chaos.
Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs.
Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used.
Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well.
Adding More OCR tools for Document data extraction and dynamic content.
I feel like the Shifts app could be more advanced to sync with Microsoft Outlook. It would be great to receive notifications in Outlook for Shifts and be able to approve/deny requests and schedule changes there while it's synced with the Outlook calendar.
It would be nice if the interface allowed further customization such as assigning colors to the separate channels. Some channels within team sites are rather lengthy and it would be great to group them into color groups.
Another nice feature would be the option to log in as one of your teammates so you can properly set up their Team account before they log in for the first time.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
test runs for key persons to insure the system is set up prior to rolling out I think the platform is good, I think the roll out and the local implantations is where we are failing as a company in using Nintex
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it
As I mentioned before, we switched to Teams from Skype because it was more reliable. We did not experience interruptions in service especially for those departments working remote.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
We have saved our company thousands of dollars by creating our own customer support system rather than using a 3rd party tool.
The ability to generate documents/PDFs in workflows has solved a great number of process issues for us and groups who had previously been using paper documents.
Automating many permissions updates through workflows has been a huge time saver for repetitive processes.
A centralized platform for the Operation Manager to handle and see the progress of different projects
This makes it easy to handle everyone at one place thus reducing time in contacting individuals and taking the feedback on progress
Knowing of any hurdles or bottlenecks in any project by just clicking on any channel and seeing their discussion. Thus guiding them then and there only.
