SharePoint Reviews

Some solutions have been implemented in the company that I work for. Most of them are based on workflows and team collaboration.

It has made us faster and more efficient. Users just like working in this environment, as an MS Office desktop.

• Team collaboration
• Unique permissions
• MS Office web access 
• Quantity and variety of partners with solution development ability on the platform.

Allow more functionalities for the on-premise version. Do not force the move of content to a non-private cloud.

More than five years.

Documentation management is the most valuable feature for me. As a technical writer, the ability to add, edit, manage and move documents is a daily task and SharePoint allows me to do that effectively.

The search function is imperative in this product and used frequently to locate and update information for our global and diverse teams.

SharePoint has allowed our organization to effectively share important information across lines of business globally. I am able to deliver effective information to all of our internal orgs immediately and can receive feedback for updates in real time.

I’ve personally experienced some difficulties in creating new pages, as this tool isn’t a web designer’s dream. Providing a list of existing pages that are named the same or similar to the new pages one might create would be helpful. Being able to toggle into those pages without exiting your original page would also be beneficial. I’ve also noticed limitations with copying and pasting fonts and images.

I have used it for seven months.

I did not encounter any stability issues.

I did not encounter any scalability issues.

Our company has used other solutions to meet various needs. We are still in the process of converting into using SharePoint for our knowledge base, etc.

Before choosing this product, I also evaluated Confluence and ZenDesk.

Create a structure for organizational pages from the beginning and document that for anyone who wants to create new pages/structures within it. One confusing thing I see often are existing pages that are “named” the same as ones that I need to create, and the existing page doesn’t have any of the information I’m trying to share.

We use it for collaboration and document management in the process of developing proposal responses.

SharePoint has made it easier to collaborate across the company during the process of developing proposals.

• The collaboration is incredibly helpful. 
• The ability to have version control and co-editing is vital to our workflows.

SharePoint sometimes cannot handle the amount of co-editing that we do. Of course, this could be the user, not the tool.

Three to five years.

• Team sites
• Reporting services
• Power pivot
• Excel services
• Search services.

• E-forms
• Workflows
• BPMN

I have used SharePoint for 10 years.

We did not have stability issues.

We did not have scalability issues.

Technical support rates a 3.5/5.

We did not have a previous solution.

Setup was complex. As an IT techie, it is setting up a farm that includes five servers.

It is a good solution for the enterprise level.

Feedback workflows ensure we don't miss someone when documents need reviewing and approval workflows make sure the right people are approving it, especially when there are new or temporary staff involved. They don't have to ask who is next in line. They just pick the appropriate workflow and it's all sorted.

We automated task workflows for document review and gathering feedback.

No additional features are needed at the moment, except bringing some of the alerting functionality from the on-premise to the online version.

I have used this for four years.

We did not have any stability problems.

We did not have any scalability problems.

We were using SharePoint 2007. We changed due to the product lifecycle.

Setup was complex. We needed to design governance and implementation architecture before deployment.

Get help. Pricing and licensing is tricky.

We didn’t look at any alternatives.

Consider SharePoint Online unless you have customisations. If you have customisations, try and get rid of them. They cause problems when upgrading.

• Visual web parts
• Document libraries
• FBA
• Document templates

It simplifies development of portal and document management. Also, by using Office 365, we got good integration with office tools.

When we develop portals, we need to develop a lot of web parts that eventually go to a number of pages. These pages must be created manually. There should be some easy way to develop pages automatically via programing.

I am working on SharePoint since 2011. I have worked (with my team) on Microsoft SharePoint 2010 and 2013. We have developed enterprise web portals of government entities and large private organizations.

We have not had any stability issues.

Actually, the scaling is very simple. One of my customers needs their portal in three languages (English, Arabic and Urdu). SharePoint doesn’t have the Urdu language package, hence we had to work hard for it.

Most of time we got support from forum and that is good enough.

We did not use a previous solution.

Setup was simple.

I recommend using Office 365.

We did not look at other solutions.

if you have a .NET team, the SharePoint is right solution for you.

Valuable features in this product are:

• Easy customization with MS .NET and related tools
• Stability
• Performance in a medium size environment (100-200 users)
• Full support by MS

We implemented custom approval workflows (for approving Opex items) using Windows Workflow Foundation which simplified and helped in speeding up the process of approving HW and SW licenses.

Performance: The web page was sometimes not as fast as we'd like to see.

Application of custom CSS/visual styles was cumbersome and usually required a complete re-write of out-of-the box SharePoint site pages.

I have used this product for three years.

Stability was usually good.

I have not encountered any scalability issues.

It's standard MS-quality support. We got the help level we expected as an MS Gold partner.

Previously, we used custom ASP.NET application. We wanted to use SharePoint because it is easy to deploy in a new environment and has out-of-the box functionalities like AD authentication, file versioning, wiki pages, .NET extensible, etc.

The installation of SharePoint server was easy and had no issues.

I cannot make any specific recommendations.

SharePoint didn't have a direct competition at the time of our evaluation, mainly due to its deep integration with .NET Framework technologies like Windows Workflow Foundation. Thus, it was our only choice to try.

Consider what level of SharePoint Web customization you are looking for. If you would be okay with some basic color changes, adding your logo and other small visual changes, it would be easy for you to build what you want. However, if you are looking to build a custom look and feel website and consider using SharePoint, you will end up building a completely new product using some SharePoint components that may lead into technology/customization limitations.

Meeting workspaces, version history, bulk tagging.

It has helped us collapse all our versions into a single file. It has also improved our meetings.

Setting up permissions can be overwhelming. If this can be improved it would be great. Also Sharepoint search out-of-the-box needs improvement.

Five years. Started out with Sharepoint 2007.

Most issues are from the change management part.

The solution appeared unstable at deployment but it's been more stable since then.

We implemented through a vendor team.