What is your primary use case for SharePoint Designer?

My job involves using SharePoint daily. It's like my online desktop. I have shared drives, documents, and most of my work stuff there.

We primarily use it as a management system for an internal website accessible for collaboration within the organization.

When you have a group project and you want to share your document with your group members, the solution is very useful. You can share anywhere but within your organizations.

I am not a heavy user. I have a team that does it. We use the solution to set up sites within the teams we have. We do it for clients as well.

The tool helps with document management. We use the solution to create workflows.

We are using SharePoint Designer for file sharing and collaboration. The solution can be deployed on-premise and on the cloud.

I'm using the solution for creating different sites in our organization. We also use it for a file repository mainly.

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.

We have many use cases, and our intranet is on it.

I played with the Designer, and it showed recommendations for the PPT style. It was very easy for me. I am very new to the design and it was easy to use, select, and design. There are several selections to design. Those who are new, like me, will find it helpful.

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.

We are using SharePoint Designer for sharing knowledge.

The solution is used to design and customized Microsoft SharePoint websites.

I primarily use the solution for collaborating on work. For web applications, you can use it to customize some of your designs for your website or your application.

It's SharePoint 365, which is the Microsoft Suite that comes up for enterprise solutions. We are dealing with pervasive client-specific data. One of the projects that I can mention here is that we created a platform for collecting data from many different clients, then collating that data, and then further analyzing it using statistical analysis on something. This particular tool was built on SharePoint so that the clients can enter their own data. We looked at many different other solutions, for example, the web solutions. That web solution would have taken a lot of time to develop, therefore, we used SharePoint, which was a handy tool. The best part was that it could also be accessed by the client. It was an internal SharePoint tool that we created, and we got it opened for the different clients so that they can enter their own data by logging into our servers. That's how we collected the data from them. It was a three-month-long data collection process in which we did the analyses.

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

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.

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.

Within our organization, there are roughly 3,000 people, but very few of them interact with SharePoint Designer. We plan on using this solution in the future.

Our primary use is for file sharing on our intranet, as well as on the internet. We also develop internet applications.

We were reviewing this tool for one of our clients — we work with both medium and large enterprises. Currently, they are using Documentum but they are interested in migrating to SharePoint, so they asked us to compare the two. I am part of an IT company where we do a lot of solutions and service-based IT. We do things for many customers from the IT side. SharePoint Designer is for the developer or the administrator, it's not for the end product (the business user). We use SharePoint to improve sequencing and workflow design in general, and it can be used to build a workflow process from end-to-end. We also use the classic version of SharePoint to do work on the master page, pinning, and other things. We can use SharePoint Designer for that. We also copy our data from our SharePoint site by using SharePoint Designer to cut and paste.

My primary uses for this solution are attaching workflows and customizing pages. Our deployment is mostly on-premises.

We primarily use the solution as our internet and extranet platform and for our software.

I use this solution for site development.

We primarily use the it as a creative solution for document management.

We primarily use the solution for modifying SharePoint.

I use it mainly for workflows or for minor changes in SharePoint master pages.

Our primary use case for SharePoint Designer is for implementation for clients.