SharePoint Designer Reviews

We use SharePoint Designer for our intranet knowledge management portal and training portal.

The most valuable feature of SharePoint Designer is document management.

SharePoint Designer could improve most in analytics and reporting.

In a future release, SharePoint Designer can improve by implementing a headless solution, where we can create pages without headers.

I have been using SharePoint Designer for approximately 10 years.

SharePoint Designer is stable.

The scalability of SharePoint Designer is good.

The support from SharePoint Designer is very good. When we have an issue they responded quickly and look into the situation.

I rate the support from SharePoint Designer a five out of five.

The initial setup of SharePoint Designer is simple. The full implementation of the solution took years because we slowly made changes over time.

I rate the initial setup of SharePoint Designer a four out of five.

We are using an enterprise SharePoint Designer license. 

SharePoint Designer is the best solution we have. We don't see any alternative as of now. For intranet and knowledge management purposes this is the best solution. It has great integration with Office products.

I rate SharePoint Designer a ten out of ten.

We are a consultancy and I am a project manager. We implement solutions for our customers and I have led several projects that involve SharePoint, as well as other similar technologies. My area of expertise is ECM, document management, information management, and related tasks.

The best business case for SharePoint is team collaboration. It can support a small team of people working on a project that involves an agenda, Wiki documents, and other related material. However, it's primarily used for temporary projects.

These days, I no longer work on SharePoint projects.

Using SharePoint helps our customers to better manage projects within their companies. Specifically, it allows them to easily connect people both internal and external to the organization and facilitates document exchange.

SharePoint has very good features for collaboration. 

One of the problems with SharePoint is that it claims to have so many features that people think they can do everything, and that is not correct. If you want to do everything, you're going to spend a lot of money to achieve your goals. Essentially, the marketing from Microsoft is very positive but from a consultancy point of view, it gets us in trouble because people have unrealistic expectations of the solution.

SharePoint is too complex to install and maintain.

The admin interface is poor, making it too complex to manage projects.

The integration with other products is poor. There are too many instances where we needed to call a third-party software company because functionality tried by the user in the other solution was not covered by SharePoint.

In the future, SharePoint needs to cover more of our needs for us to continue using it. For example, the workflow is not correctly integrated.

I have worked with SharePoint Designer for more than six years.

The stability of SharePoint depends on the client's architecture. If it's a simple installation then it's stable. But, in a more complex deployment, it is less reliable.

For example, I have worked with SharePoint in a highly complex organization in the financial industry. Every week, the system would crash. The IT would have to tell the users that it wasn't working and then resolve the issue.

Overall, it's not the best solution in terms of stability.

SharePoint is scalable, albeit complex.

We have approximately 10 customers that we have deployed SharePoint for. They have multidisciplinary teams, and people in many different roles use the software.

There are two levels of support for SharePoint. The first is from the company that sells it, which is the main integrator. The second level of support is from Microsoft, which is quite different.

Most of the time, the support from the integrator is valuable, whereas the support from Microsoft is too basic. I would rate the support from Microsoft a two out of five.

I have used several similar products including those from Alfresco, Laserfiche, and IBM.

The initial setup is highly complex and the deployment strategy varies depending on the needs of the client. It requires between one and three IT architects for the installation, depending on the customer's environment.

I would rate the ease of installation and setup a one out of five. 

In terms of ROI, I would rate SharePoint a one out of five.

Most of the time, our customer's license from Microsoft includes the cost of SharePoint. However, if you have to buy it then SharePoint is quite expensive.

I would rate the pricing a two out of five.

Based on my areas of expertise, I have to make recommendations to our clients about which solutions they should implement. I rarely advise my clients to use SharePoint. In fact, out of ten customers, on average, I would recommend SharePoint to two or three of them.

SharePoint is simply not dedicated enough to documentation management when people are looking for a real DMS or ECM solution.

My advice for anybody who is considering SharePoint is to first define your needs and then take quite a good look at the market. For tasks including document management, ECM, or a platform content service (PCS), most of the time, you will be better served by a solution other than SharePoint. If, on the other hand, you are looking for team collaboration, then SharePoint may be a good option.

Overall, I am not very satisfied with SharePoint.

I would rate this solution a five out of ten.

Our main use case for this solution is to develop custom SharePoint sites. SharePoint is about collaboration to help improve efficiency, collaboration within teams, document management, and search. We have thousands of users in our client organization. We are a Microsoft gold partner.

SharePoint Designer has made information available centrally 24/7. It brings offline records online. It has made searching easy, without it document search was difficult. Communication between departments has become more effective.

I find the document management and search of SharePoint the most valuable features. 

I would like to see SharePoint improve the integration with different systems. I also would like to see more customization.

We have been using SharePoint Designer for 16 years.

SharePoint is stable.

Scalability has certain limitations depending on the number of users and number of records.

The availability and quality of technical support both need improvement.

Earlier, we used Custom.NET applications however, SharePoint is much better.

The initial setup is straightforward and gets simpler with every new version. The set-up takes less than a day, but the project for full implementation takes anywhere from 4 to 12 weeks. 

We used our own consultants to set up SharePoint. You need anywhere from 2 to 5 people and even upwards of 10 depending on the size of the portal to deploy and maintain SharePoint Designer.

Most of the SharePoint implementations are for the cloud which is priced per user per month. There are different plans at different costs that you can choose from.

We reviewed Custom.NET and other PHP based solutions prior to selecting SharePoint.

If you are implementing SharePoint Designer in your organization, I would recommend that you use the best practices given by Microsoft, specifically in implementation.

I would rate SharePoint an 8 out of 10.

One of our use cases of SharePoint is designing and branding our content management system. When somebody buys an intranet portal, like a content management system, for employees or a document management system for their company, they can buy SharePoint and use it to change the branding. Microsoft gives you default features—out-of-the-box—so if you want any changes regarding your identity, HTML, CSS, colors, or brand guidelines, then SharePoint Designer can help you to complete that task. SharePoint Designer can also be used to clear workflows. This is a tool which helps us brand the SharePoint portal and our flow sites. 

In the beginning, SharePoint was deployed on-premises, but now it is deployed on the cloud, so we are always using the latest version. 

One of the most valuable features is that it's free. If you have SharePoint and you want to do some branding, then the only tool available is SharePoint Designer. Microsoft gives the portal, the content management system, and, on top of that, it gives you Designer. So we don't have a choice, but Designer is good. 

SharePoint Designer could be improved by being more user-friendly. I think that they have a new release, but the focus is on Power Automate, not Designer. Designer's interface is somewhat classical, but it should be more user-friendly. 

Designer should contain more features. Right now, we are doing the development of web parts on Visual Studio and doing the branding on Designer. If it were possible to merge them both into one tool, it would be easier. 

I have been using SharePoint Designer for 13 years. 

There is no maintenance team necessary. Users can maintain it by themselves because Designer is a tool which can be deployed on each PC to work on. 

In our organization, we have around eight to ten people who are developing on SharePoint Designer. We don't currently have plans to increase usage, but it depends. We are a project delivering company, and I am a project manager, so our SharePoint usage is on a project-based development. If we have a client we need to use SharePoint for, we may increase the usage, but otherwise we won't. 

In 13 years, we have raised tickets two or three times. They don't call us, but when we raise tickets, then the issues can be resolved. 

We also use Visual Studio from Microsoft to develop the programs for SharePoint. Designer is only for branding and workflows, but you have to use Visual Studio to actually develop the portal components and web parts. Visual Studio should be used with SharePoint. 

The installation of Designer is very simple, and it doesn't take more than 30 minutes. You can download and install it yourself. 

There is no licensing cost for Designer—it's free. 

I rate SharePoint Designer a six out of ten. There were some bugs, but when you are working on SharePoint, you have to recommend SharePoint Designer, for sure. 

We use SharePoint Designer to create SharePoint sites and applications for sharing information within our organization.

The Power App is the most valuable feature. We can design it to look exactly how we want it to be, without requiring an expert's assistance to set it up. We have the freedom to make changes on our own and can easily connect and generate leads.

Power Apps has certain limitations as it is designed primarily for tablets. When deployed on a computer, it becomes much smaller. I am currently facing the challenge of maximizing its functionality on a computer. This is one of the downsides of Power Apps.

SharePoint Designer needs filter options for lists and libraries. I want to create user groups and subgroups of users to apply properties to the metadata. Currently, I'm struggling to find a workaround.

I have been using SharePoint Designer for around three years.

SharePoint Designer seems to be stable.

I give SharePoint Designer a nine out of ten. We can create sites without having to code.

I recommend SharePoint Designer to others.

The most valuable feature of SharePoint Designer is the storing of files. In the Office 365 version, there is the capability to share files with others which is helpful. The files have cross versions capability. If the solution is shut down abruptly the file is stored on the system automatically.

The system can become slow which should be improved.

I have been using SharePoint Designer for a long time.

The solution can crash sometimes, this should improve. However, the reason could be the Microsoft operating system.

The implementation of SharePoint Designer can be difficult.

I rate SharePoint Designer a six out of ten.

When we want to do the configuration changes or customization on the SharePoint side, we do so using SharePoint Designer.

It's a very good tool when it comes to the modification of SharePoint back pages. We use a lot of the standard tools. 

It has helped us create some strong, beautiful websites for our organization.

The master page configuration is useful. 

The solution is reasonably priced.

It is scalable.

The solution has been stable.

The initial setup is not too complex. 

The integration with SharePoint online is missing certain features. 

It needs to align with PowerApps and Power Automate. 

I've used the solution since 2016. I've used it for about seven years. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

It is scalable. The solution can extend well. 

Technical support is a bit tricky to talk about. We generally get support for Microsoft products in general, which is helpful. However, we've never needed help with this product.

The initial setup is very straightforward to set up. It's not complex at all. 

We have witnessed an ROI.

The pricing is reasonable overall. It's not too expensive. 

We have been using the 2016 version. 

I'd advise others to use SharePoint Designer if they value SharePoint. 

I would rate the solution eight out of ten. It has been very useful as a tool. 

We use this solution for web applications when we need to make changes to the pages and front end. We also use it to make changes to the html, design and the user experience. 40 people use this solution in our business. 

The drag and drop feature is the most useful feature when using this solution. In addition, it is a free solution that does not require a license. 

The downside is the different versions of SharePoint which means we need to have different designers as not all versions are compatible. 

In the future, we would like to have support for SharePoint online and the latest standards of UX. 

I've been using this solution since 2006.

I would rate the initial setup an eight out of ten.