Scalability would be an issue. There were the minimum number of folks that we were working with, however, if you want to deploy a SharePoint site, for example, to millions of people, the servers have to be accordingly configured. It completely depends on the servers. That's the major thing when you're deploying a SharePoint site. That's why scalability might be an issue, however, I'm not sure about that as we haven't tested a fully scalable website on SharePoint.

There's a dedicated team, on the product who know the SharePoint site in and out, however, they are not all developing the websites. They're there to enhance the backend systems and understand our queries and resolve them. The SharePoint developers are within my team itself.

In my team, probably five to six people know how to develop a SharePoint site, and in my company, there's a dedicated team who do SharePoint and that's a 15-member strong team.

Just our developers use the solution. There are maybe 15 or so people using it at this time. 

The scalability is excellent, and I rate it ten out of ten.

I would rate the scalability a nine out of ten. 

Everybody in my company uses it. There are around 6,000 end users in my company. 

My initial site wasn't designed for high scalability, but I fixed it, and it can be adapted for larger workloads if needed.

Our company has around 300 end users using it. However, we don't have plans to increase the further usage. 

SharePoint Designer is scalable.

The scalability has been okay. I'd rate its scalability seven out of ten.

The product has a high scalability. I rate the scalability an eight out of ten.

The solution's scalability is fine. I don't have much confidence in SharePoint. It's easy for me to use.

There are 360 users of the solution in my organization.

It is extensively used, but we have no plans to increase its usage.

I rate the scalability of SharePoint Designer a five out of ten.

SharePoint Designer is scalable.

While I find it scalable, my use case is not something where I really use it on a large scale and enterprise level. I wouldn't be able to give a definite answer to scalability for large-scale operations.

I just use the product on a personal level. I don't have any large projects that are ongoing.

SharePoint Designer has very good scalability.

The solution is scalable. 

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.

It is scalable. The solution can extend well. 

The scalability of SharePoint Designer is good.

I would rate scalability a nine out of ten. There are more than 10,000 users using this solution in our organization.

We have possible plans to increase the usage.

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. 

The scalability is a little bit complex. We do have a lot of issues with scalability. It's not everything we hoped for.

The scalability is not a problem because this is a desktop application and it works just fine. As long as your SharePoint site is scalable, the application will work just fine. 

SharePoint Designer is a very small tool, and very clever. You install it on your computer to access SharePoint's entire platform. In that sense, it's not a technology that's scalable or that needs to be scalable.

The scalability of SharePoint is good and the program is fast. 

This solution is very scalable.

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

The solution is scalable.

We are a small company with five people using the solution. If we grow it will be approximately 10 to 15.

This is a problem that does not occur at all. SharePoint Designer puts its configuration data into a firm structure, which is parallelized by default and thread protected. It does not matter which means you use in to access the data, whether it is through direct API calls or in SharePoint Designer. It is protected against all structures within the form. You cannot override data. It is inherently parallelized by SharePoint, itself.

There are approximately ten users working within our support company, but the company using this solution has about five hundred end-users.

The scalability is okay but limited.

We have only recently deployed the solution, I am not able to give much information on the scalability.

We have approximately 200 users using this solution in my organization and we plan to increase usage.

Although I'm not in charge of scaling the solution, I've heard it's not very easy to expand the capacity.

The solution is not scalable at all.