Try our new research platform with insights from 80,000+ expert users
IT proffesional at Ambo university
Real User
Top 10Leaderboard
Used for information sharing and provides good integration capabilities
Pros and Cons
  • "The most valuable feature of the solution is file sharing or information sharing."
  • "The solution should be made more user-friendly for technical and business people."

What is our primary use case?

We use SharePoint for information sharing.

What is most valuable?

The most valuable feature of the solution is file sharing or information sharing.

What needs improvement?

The solution should be made more user-friendly for technical and business people.

For how long have I used the solution?

I have been using SharePoint for six months.

Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.

What do I think about the stability of the solution?

SharePoint is a stable solution.

What do I think about the scalability of the solution?

SharePoint is a scalable solution that supports more than 1,000 users.

How was the initial setup?

The solution’s initial setup is easy.

What other advice do I have?

The solution has good integration capabilities. I would not recommend the solution to other users because it is not easily compatible or operable by everyone. More than 20 engineers and managers are needed for the solution's deployment. SharePoint is a good solution for IT collaboration.

Overall, I rate the solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Olatunji Osinaike - PeerSpot reviewer
IT Admin/Consulrant at Switchmoon
Real User
Top 10
Easy to use and can be used for collaboration, storage, and file sharing
Pros and Cons
  • "The most valuable feature of SharePoint is its ease of use."
  • "When you are trying to migrate from a different platform to SharePoint for file storage, the upload utility should be more flexible, taking more files and then updating you on the upload status of the files you are trying to transfer into SharePoint."

What is our primary use case?

I use SharePoint for collaboration, storage, file sharing, and content management.

What is most valuable?

The most valuable feature of SharePoint is its ease of use. It's quite easy to navigate through the tool.

The most useful feature of SharePoint is the collaboration part. At any point in time, you know who was working on a document, and you can know which version is actually the latest document in case you want to share it with external parties. If we want to make decisions or talk about information on a document, we know which is the latest and most updated.

What needs improvement?

When you are trying to migrate from a different platform to SharePoint for file storage, the upload utility should be more flexible, taking more files and then updating you on the upload status of the files you are trying to transfer into SharePoint. This part is quite clunky and could be improved.

For how long have I used the solution?

I have been using SharePoint for five years.

What do I think about the stability of the solution?

I rate the solution an eight out of ten for stability.

What do I think about the scalability of the solution?

Around 50 users are using the solution in our organization.

I rate the solution’s scalability a seven out of ten.

How are customer service and support?

The solution’s technical support is fine.

How would you rate customer service and support?

Positive

How was the initial setup?

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

What about the implementation team?

The solution's full deployment was done by three people in less than ten days.

What's my experience with pricing, setup cost, and licensing?

The solution's pricing is relatively expensive because it's bundled with other products.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six or seven out of ten.

What other advice do I have?

The solution's integration with Power Automate and many other Microsoft solutions has been very seamless. SharePoint is deployed on the cloud in our organization. The solution requires a bit of maintenance, but it's very minimal. Since most Microsoft solutions are now bundled with AI, the turnaround time for searching and indexing has improved. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
SharePoint
March 2025
Learn what your peers think about SharePoint. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.
MichaelSoliman - PeerSpot reviewer
Owner at Alopex ONE UG
Real User
Top 10
The metadata services, the WCF service integration and the Voxel feature are three most valuable elements of this solution.
Pros and Cons
  • "The metadata services, the WCF service integration and the Voxel feature are three most valuable elements of this solution."
  • "Tech support tops off as excellent."
  • "The initial setup was very complex."

What is our primary use case?

I have been using SharePoint for over twelve years. 

It's a big solution comprising many services similar to an active directory installation with connections to Skype, Exchange services, metadata services and stuff like that, it can do basically everything you need in order to deliver something like a Twitter website or similar solutions. So I do not think that anything rivals SharePoint on the market. Maybe if a lot of effort is placed upon some WebLogic solutions, this may happen. But, this would need a lot of customizing.

How has it helped my organization?

So if you want to have something like a business, or if you want to have something like a product catalog and you are selling something like Amazon, you want to uniquely identify your product like Amazon does it with its ASIM numbers and these to be identified with a name. So the service identifying these unique ASIM in numbers with their names which might be localized in English, German, Dutch or other languages. These are being identified by a managed Metadata service. Amazon does something very similar to Metadata and SharePoint. So, that's the basic technology everyone needs for this web service experience and order to identify the same object with different names.

What is most valuable?

The metadata services, the WCF service integration and the Voxel feature are three most valuable elements of this solution. The Voxel feature, for obvious reasons, because you want to implement business processes and you do not want them to stop if the machine stops so they have to be automatically started. This is What the Voxel feature in SharePoint does. The managed Metadata allows you to define your own notions or terms denoting notions within your companies. And I if I want to disarm them, or disarm power supplies of different types, I need something to denote the names pointing to entities, any program can identify.

Perceptively it does what people used to do with the pens and pencils, on paper. For Millennials, by taking a note of what to do on the paper or stone or whatever they have been using and let anyone else read it and execute with it. So what any back flow or business process you have did legal one for King Nebuchadnezzar 2,700 years ago or for any business where you are taking a phone call, we two are doing right now and writing down something or I have to remind myself to do whatever and sent that over to pop and be while having receipts from department A and have to digitally sign it and send out the paper. It streamlines everything for us.

All of this business processes, people have been performing solely within their minds. Maybe automatized with the structural feature, but it depends on all the metadata that has been stored within the managed metadata, service, user profile data or whatever. So you can not just say, "Oh, I want to send a car" to whom do you want to send it to. Which car do you want to send? So, all of these parameters have to be stored somewhere else. This is what drives the business process and SharePoint solution allowing you to automatize them.

What needs improvement?

I would be liking to see the talk features included in SharePoint because Microsoft effectively discontinued this talk and put something like logic apps but only for Azure, and most German companies do not like Windows Azure because they do not want to put that data into a cloud where everyone can see it. So, there's a lot of distrust with Azure environments and you need something to have on premises as a similar solution. And this talk is something like a big playing ground. For instance, if you want to play monopoly and anyone wants to move the pieces but moving the pieces on street A to street B means you are changing your business process from, I have been starting tax declaration, to I've been finding it but not yet sending it out. So, if you wanted to have something like a business process be denoted as a board game, which is what Monopoly did in 1945, effectively.

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

It is very stable if you know what you are doing and make some precautions. Microsoft lists these precautions, but these precautions are not automatized. It would be nice to have precautions such as: disk size, backup checks, or whatever automized that can be integrated with the SCCM team foundations server.

What do I think about the scalability of the solution?

Well, that's one of the strengths because it not just using soap web services where it sends some XML file to different machines, but it's using WCF, which is a version of a web service, web services being used if you have a different machine where you want to call a function. The type of machines we are using now are invented by Alan Turing, a guy from the hacking Enigma code and Robert Dennard, who invented RAM. These types of machines do not allow you to, all functions on the remote machine. If you want to do that, you have to send a hint which is what web services does.

How is customer service and technical support?

I have been using the commercial technical support and they're always professional. It's not cheap, but they are always professional. So if there's problems to be solved, Microsoft tops off as excellent.

How was the initial setup?

The initial setup was very complex. We had to keep in mind all of the backup solutions. It is kind of like remodeling a kitchen. You must think of all of the parts, the architecture, the electricity, the air flow, etc.

What was our ROI?

I think that SharePoint is the best on the market in terms of stability, quality and capability. I also suggest that if a company has chosen SharePoint, the company must have at least a two day training prior to implementation.

What's my experience with pricing, setup cost, and licensing?

The cost is expensive, but worthwhile.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
OTA Manager, VRA at United States Department of Defense
User
Its configuration management ability is critical for document-based systems
Pros and Cons
  • "Its configuration management ability is critical for document-based systems."
  • "It offers ease of use, which is crucial."
  • "It should have a Google-caliber search ability and a model-based GUI."
  • "During uptime under our network, it is hard to find info when content is hefty."

What is our primary use case?

Most departments use SharePoint for their own organizational homepages and their document repositories

How has it helped my organization?

It is better than static repositories via shared drives, and better than having to use software that is not mainstream (i.e. Microsoft is very mainstream).

What is most valuable?

  • Its configuration management ability is critical for document-based systems.
  • It offers ease of use, which is crucial.

What needs improvement?

  • During uptime under our network, it is hard to find info when content is hefty.
  • It should have a Google-caliber search ability and a model-based GUI.

For how long have I used the solution?

More than five years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
ITIL Process Manager at a healthcare company with 1,001-5,000 employees
Vendor
We use the list functionality to create integrated test scripts. It provides a Web solution for running integrated test scripts across multiple applications.

What is most valuable?

The key features in this product are:

  • Use of list functionality
  • The ability to easily modify the default screen on a new Web site
  • The ability to quickly create and modify subsites
  • The ability to create unique access rights to the subsites

How has it helped my organization?

We use the list functionality within SharePoint to create integrated test scripts. This has allowed us to have a Web solution for running integrated test scripts across multiple applications, along with multiple testing resources in numerous physical locations.

What needs improvement?

The product can be improved in the following aspects:

  • In order to put certain customizations in place requires the downloading and installation of SharePoint Designer 2013. For large organizations where security has the majority of devices locked down, downloading and installing applications is not a simple process. It would be nice if some of the SharePoint Designer functionality could be baked in/part of the edit page functionality.
  • The reporting functionality needs improvement, to combine multiple lists (for the most part) requires a solution outside of SharePoint. It would be great if there was an option to combine lists that have the exact same layout (fields and order of fields) so that the combined lists could be summarized and reported on.


For how long have I used the solution?

I have used SharePoint for a total of 14 years; 11 years with my current employer.

What do I think about the stability of the solution?

Mostly, we have not encountered any stability issues.

What do I think about the scalability of the solution?

I have not encountered any scalability issues.

How is customer service and technical support?

I cannot comment as I simply use Google to find answers for technical issues.

How was the initial setup?

The initial setup process was fairly straightforward.

What other advice do I have?

My advice is to not hesitate; just plunge in and implement SharePoint.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user68340 - PeerSpot reviewer
Director of Development at a tech consulting company with 10,001+ employees
Real User
SharePoint vs Yammer. What’s the difference?

How does Yammer compare to SharePoint? Does it fit into an organization that is using SharePoint 2013?

Ben Skelton

SharePoint 2010’s social features were pretty rudimentary. Organizations that really embraced social had to turn to third-party vendors, such as NewsGator or Yammer. Although powerful, I always felt NewsGator was a little complicated and the user experience wasn’t ideal. SharePoint 2013’s social features are miles ahead of what was available in SharePoint 2010.

Personally, I don’t understand why an organization would adopt both SharePoint 2013 and Yammer. I would leverage the social tools within SharePoint 2013 as they are fully integrated within an organization’s employee portal. The mobile apps for SharePoint (both Windows Phone and iOS) will also help complete the social story. That said, if a client wanted to stay on SharePoint 2010, Yammer might be a good fit.

Chris Radcliffe

While Yammer and SharePoint 2013 share similar social capabilities (discussions, feeds, ratings, individual profiles, etc.), the difference is that Yammer’s social features have been utilized for years and the Yammer team appears to be evolving the social experience more rapidly than the SharePoint team. It is much easier to setup and use Yammer, so fostering collaboration can happen much more quickly. Yammer employees may also tell you that the service was built around people, whereas SharePoint was built around documents.

Yammer spoke about their intended SharePoint integration scenarios at the SharePoint Conference and highlighted concepts such as a Yammer Web Part, embeddable feeds, document and list integration, profile synchronization, and federated search. At this point, I’m only seeing talk about Yammer integrating with SharePoint Online, not the on-premise verion, but that could be coming. I could see organizations using both SharePoint and Yammer when the business case or appetite for social is not yet clear and there would be benefits in piloting Yammer. Agreed though, it would be weird to have a Yammer and SharePoint 2013 mixed social experience.

Ellisa Calder

I have to agree with Ben. SharePoint 2013 has expanded social features allowing you to create community sites, post micro-blogs, use hash tags, and mention colleagues and communities; but it’s still a light social feature set compared to Yammer, NewsGator, and a host of other social products on the market. SharePoint is still the extensible platform that is playing catch-up in the social computing space. That said, I think a lot of organizations will find SharePoint 2013’s out-of-the-box social features sufficient, at least as a first step into this space.

Yammer is completely about conversations in the open. It’s for sharing, collecting company knowledge (especially tacit knowledge), and creating opportunities for connections around work, interests or specializations. Yammer is a social web community experience. We heard over and over again, it exposes the opportunity for serendipitous discovery, and it does this a lot better than SharePoint 2013.

Right now, there isn’t a clear story about an integrated Yammer and SharePoint 2013 experience. For organizations just looking to dip their toes into social, SharePoint 2013 will probably suffice. For organizations looking for rich, social computing capabilities, they will need to look at other options. As for running Yammer and SharePoint 2013 simultaneously, it could be hairy to sync these two experiences for users. It will require a lot of work on the community/portal management side to do the manual integration that is required at this point. With the future of Yammer and SharePoint being so unclear at this point, I think it is going to make any decision regarding which social computing product to purchase very difficult.

Sarah Berg

I’m also having a hard time visualizing how organizations would utilize Yammer together with the social features of SharePoint 2013. I’m really impressed with the improvements Microsoft has made to the social story in SharePoint 2013, although as Ben mentioned, there was nowhere to go but up from SharePoint 2010. I would agree that Yammer has a more polished social experience, but SharePoint 2013 is definitely closing the gap.

One of the biggest things I was hoping to get out of the SharePoint Conference this year was a better understanding of how Microsoft plans to integrate Yammer into SharePoint and what that unification will actually look like for users, and I have to say I was pretty disappointed. It feels like a question that Microsoft doesn’t yet know the answer to, or they just aren’t ready to share it yet, but either way we’re left wondering. Until we have more clarity it will be hard develop an enterprise social strategy around these technologies, which is disappointing for organizations who have already invested in SharePoint and Yammer, or had been considering them for the future. In the meantime, I think the new social features in SharePoint 2013 are a great starting point for organizations that are looking to introduce social functionality into their portal environment.

Why do you think Microsoft bought Yammer?

William Hardy

In my opinion, Microsoft acquired Yammer for three main reasons:

  1. 1. Leapfrog perceived social capabilities: Regardless of how good SharePoint 2013’s social capabilities are (and I think they are great), Microsoft would constantly be battling a perception of being one step behind in the enterprise social space (as they have been). Acquiring Yammer gives Microsoft the instant perception of being a serious contender in the enterprise social space and signifies to the market that they are willing to take bold steps to get there.
  2. If you can’t beat them, buy them: By buying Yammer, Microsoft takes out a key competitor and arguably the most established brand in enterprise social. This turns them from a threat to strength.
  3. Shake things up and accelerate innovation culture: It’s clearly not business as usual for the social team in Redmond. The acquisition of some relative rock stars in the enterprise social space means that the thought leadership and opinions for SharePoint social are now coming from entirely different directions. That includes a shift in focus to rapid innovation development cycles (90 days or less) and a Silicon Valley start-up culture.

Chris Radcliffe

I suspect Microsoft sees Yammer as a core pillar of their cloud strategy to help customers move to the cloud and break down barriers IT may present. The Free-mium model of Yammer reminds me of Windows SharePoint Service (WSS), where collaboration was given away for free in SharePoint, and as a result was lit up like crazy in North America. Based on the valuation, you have to imagine that a big part of Yammer’s value proposition was modeled around the future potential of cloud-based subscription revenue in the current Micorosft Enterprise Agreements.

Another way of looking at this question is, why did Yammer let themselves be bought by Microsoft? If you suspend belief that the massive valuation was the sole reason, the only other reasons I’ve heard that sound remotely possible are the fact that Microsoft’s partnership allows Yammer to more quickly accomplish their vision, and that Microsoft brings scale both technically and from a market share perspective.

Sarah Berg

Microsoft’s acquisition of Yammer was a smart move. Yammer has been adopted in many organizations and brings a wealth of experience around enterprise social. Social functionality was almost nonexistent in SharePoint 2010 and Microsoft bringing Yammer into the fold will boost their impact and presence in a space where they desperately needed to make big advances. With over five million corporate users, Yammer is an invaluable addition to Microsoft’s portfolio.

The benefits to Yammer were a little less obvious to me upon initial consideration, and I really like Chris’s idea of approaching this question from the other perspective. If I had been asked to pick two software companies with similar identities, cultures and values, I certainly wouldn’t have chosen Microsoft and Yammer. It seemed like a sell-out by Yammer, but the Yammer team seems genuinely excited about the change. Partnering with Microsoft will extend Yammer’s reach and will give them access to the resources needed to innovate on a much larger and more impactful scale.

Ben Skelton

I agree with everyone else, although I am not quite as enamored with Yammer as the rest of the group. I think the acquisition was similar to that of Skype. Microsoft saw a best-of-breed technology for an area that was strategically important (and they were under-performing in) and decided to acquire.

It’s interesting because both of these tools don’t look or feel Microsoft-y. I wonder if that will change over time or if they will keep their own identity. It will be an interesting time over the next few years for organizations that are standardized on the Microsoft stack as Microsoft determines how these social tools will all work together (or won’t).

What is the future of social with respect to SharePoint vs. Yammer?

Ellisa Calder

This is the million dollar question! Right now, I think it’s anyone’s guess. The Yammer group and the SharePoint team were adamant at the conference that Yammer will never be an on-premise solution; it will always exist in the cloud. Microsoft and SharePoint are pushing hard for the cloud, but there are many clients that will be on premise for the foreseeable future.

Given this reality, I can see Yammer, Office 365, and SharePoint Online integrating really well and becoming a dynamic collaborative, social online environment. For clients using on-premise installations of SharePoint, they will either end up with some half-baked Yammer integration paired with out-of-the-box (OOTB) SharePoint social features, or OOTB SharePoint social features on their own. For organizations that have yet to dip into any significant enterprise social technologies, SharePoint 2013 OOTB will likely be sufficient as they wade into the social enterprise space.

William Hardy

There’s no way Microsoft can continue to offer such vastly different and competing social directions going forward — they need to communicate a clear and cohesive integration story soon. Microsoft took a fair bit of criticism post conference for not presenting a well thought out vision of integration and left customers in a fairly awkward position when approaching enterprise social on the Microsoft platform. With no explicit integration road map, the vibe at the conference was one of a shift in direction to following Yammer’s new way of doing things. Therefore I would suspect future changes to SharePoint social will be heavily dominated by Yammer capabilities, with the bulk of the thought leadership and influence coming directly from that team.

` Sarah Berg

At the end of the day, I want to see a highly usable set of social features and capabilities that are tightly integrated into SharePoint. The big issues right now with SharePoint and Yammer are the confusion between where one ends and the other begins, and why an organization might use one over the other (or how they could use both). I’m not sure how this will play out for on-premise installations vs. organizations who are leveraging Microsoft’s cloud offerings, but my hope for the future is a seamless and exceptional social experience in SharePoint.

Where would Yammer be a good fit? Are there risks to be aware of or things to consider?

Chris Radcliffe

I think the answer is easy. If an organization has an older version of SharePoint (such as SharePoint 2007) or a similar legacy platform and is interested in exploring the benefits of social collaboration in a low-cost, efficient way I’d suggest Yammer! If the organization is on SharePoint 2010 and has already developed a very strong collaboration model or perhaps has had success with some of the social concepts, I’d recommend SharePoint and not complicate the user experience. Setting up an Office 365 trial would be the fastest and easiest way to test-drive the new social capabilities in SharePoint.

Biggest risk point to consider? If your current employee portal has a rich set of social capabilities, I would be careful extending an isolated Yammer solution. The risk is that employees could become confused about what the organizational standard is for managing information, collaborating, and communicating across teams. For years, organizations have tried to simplify the personal information management strategies that employees have to deal with, and adding Yammer without the right change management and communication could make matters worse!

Sarah Berg

I agree with Chris. I think if an organization is running an older version of SharePoint or is using a non-social portal platform, Yammer could be a good fit, especially as an introduction to the world of enterprise social. In this scenario it’s still important for the organization to provide clarity to employees around the use and benefits of Yammer, what is considered acceptable (and what is not), and how Yammer can be used to supplement the communication and collaboration that is already being delivered through the portal. Without change management and governance an organization is definitely at risk of confusing and alienating users, resulting in poor adoption and continued challenges down the road!

William Hardy

If an organization were likely to move to SharePoint 2013 in the near term, I would recommend adopting the native SharePoint social features, as they are excellent and likely capable enough for most organizations. SharePoint’s social capabilities have finally been extended beyond the My Site and have been blended throughout the platform in a fairly seamless fashion.

If clients were running SharePoint 2010 or a prior version with no immediate plans to upgrade and have a limited enterprise social footprint, then I would certainly take a good look at what Yammer has to offer. While the story has changed recently, earlier versions of SharePoint including 2010 can’t really claim to have competitive enterprise social features with Yammer. Yammer can also be deployed quickly and with relatively little effort.

Risks to consider? As mentioned by the others, introducing Yammer (in its current state of integration with SharePoint) could leave users with some confusion and detract from the use of your existing employee portal and collaboration platforms. Once you rollout a tool like Yammer, there’s no going back! Employees will become accustomed to the social capabilities and they will profoundly influence future directions/options. Even pilot rollouts of Yammer should be planned carefully for this reason.

https://www.habaneroconsulting.com/insights/SharePoint-Yammer

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Works at Command Results, LLC.
Real User
Supports us in software development projects and integrates well with Microsoft Project
Pros and Cons
  • "This solution has helped us with the categorization, organization, management, discovery, and delivery of program and project related information."
  • "This solution would benefit from the implementation of enhanced online forms and template development capabilities."

What is our primary use case?

We use this solution for supporting software development programs and projects.

How has it helped my organization?

This solution has helped us with the categorization, organization, management, discovery, and delivery of program and project related information. 

What is most valuable?

The most valuable feature of this solution is the integration with MS Project.

What needs improvement?

This solution would benefit from the implementation of enhanced online forms and template development capabilities.

For how long have I used the solution?

We have been using this solution for fifteen years, off and on.

What do I think about the stability of the solution?

Again, no problems on our applications.

What do I think about the scalability of the solution?

I have never seen it hit a wall in terms of supporting our programs, and I have been the senior contractor program and project manager overseeing two large Health IT projects, both with more than 100 team members and as many as 11,000 assigned tasks.

How are customer service and technical support?

he Microsoft reps were always helpful; although they were not always up to speed with the latest offerings and capabilities from Microsoft. Persistence pays off thought. I usually eventually got the answers to my questions.

Which solution did I use previously and why did I switch?

NO, client requires use of SharePoint for content management on IT programs and projects.

How was the initial setup?

It seemed easy enough.  The one issue I had was setting up a project portal where we wanted to implement a number of SDLC Templates via SharePoint. This was a couple of years ago, but the integration of a legacy Microsoft forms product was not very clean or adequate. It looks like the previous tool has been replaced with Microsoft Forms. I haven't had a chance to use this product yet. 

What about the implementation team?

In house.

What was our ROI?

Confidential

What's my experience with pricing, setup cost, and licensing?

I don't have experience in that area.

Which other solutions did I evaluate?

No, client requires use of SharePoint for content management on IT programs and projects.

What other advice do I have?

No

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Assistant Manager, Operations Automation at a financial services firm with 10,001+ employees
Vendor
You can assign permissions, create user groups, and automate workflows. I would like to see a more intuitive way to assign permissions.

What is most valuable?

  • Flexibility to create customized lists and folders
  • Ability to assign permissions
  • Ability to create user groups and automated workflows
  • Easy to use
  • Provides flexibility to create separate user groups with specific read, write, and access for certain folders
  • Ability to restrict access: Prevents the vendors from touching our master files

How has it helped my organization?

It has allowed my team to seamlessly share requirements with one another and provide feedback while working off one version. It is a one-stop shop for all our project documents.

We are currently working with two different vendors (one from Europe and one from India). We used SharePoint as a central workspace where the different groups can upload their files respectively without restriction. They can also have a central folder where RBC and vendors can edit simultaneously.

What needs improvement?

For this version, assigning permissions should be more intuitive.

An improved user interface would be beneficial. Achieving our goals in a multi-vendor project was not an easy task because of the 2010 UI.

I’m not sure if SharePoint 2013 makes it easier to assign specific access for folders. I found a lot of help online that was mostly for 2013.

We should have the ability to create customized permissions for user groups much easier than it is today. For example, being able to specify which lists and folders a group can access. In 2010, there is no easy way to do this.

For how long have I used the solution?

I have used SharePoint for about two years now.

What do I think about the stability of the solution?

I did not have any stability issues.

What do I think about the scalability of the solution?

I did not have any scalability issues.

How are customer service and technical support?

Technical support is excellent.

Which solution did I use previously and why did I switch?

I have always used Microsoft SharePoint for my projects.

How was the initial setup?

We have an excellent onboarding process that our IT team put together, so setup was not particularly complex.

Which other solutions did I evaluate?

I was not involved in this process.

What other advice do I have?

Look at scalability and stability and see whether the features of the product really meet the needs of your organization.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free SharePoint Report and get advice and tips from experienced pros sharing their opinions.