Sharepoint - how do you use it?
-
We use a picture gallery on there for company pictures.
-
SP has some really powerful shared calendar stuff.
-
Workflow functionality is a big deal in SP. That's stuff that most SMBs are not used to having.
-
You can actually use .NET and build whole applications on top of SP.
-
We use it as a backend for our 365 e-discovery and archive/legal hold portal. Our partner built it for us - took 2-3 days. Amazing stuff they give you in Office 365 that few people realise is in the solution
-
@IRJ said:
@Dashrender said:
I have a small business I just transitioned to Office 365 (thanks NTG).
This interests me... You seemed like you were against Office 365 in the other thread. What changed your mind?
I've never been against Office 365, as long as you have nothing today. Or you're already hosted today. This particular client of mine was hosted with a local company for $18/user/month with a 15 user minimum (they only needed 10) with none of the extra features that Office 365 offer. Not to mention the fact that their old hosting provider was still on Exchange 2007.
They've moved to the E1 plan for $8/user/month and gained access to Exchange 2013, Sharepoint, etc. and save $10/user/month.
and with the new features (which was originally outside the scope of the move, and now I'm scrambling, ug) they want to see what new things can help their business.
-
This post is deleted! -
@scottalanmiller said:
SP has some really powerful shared calendar stuff.
This is something they might be (probably are) interested in using.
-
We've been using SharePoint internally at NTG since the original 2003 release. We went 2003, 2007 and 2010 all hosted internally. Then we went to 2010 hosted with Rackspace and then 2013 with Office 365. So we've been using it a long time. We use it for everything, once you get used to it you will be addicted. It is really amazing once you start to leverage it as your central repository for everything.
-
Do you map network drives for file storage?
-
wow scott. how did
-
@Hubtech said:
wow scott. how did
your post count
-
@Hubtech said:
@Hubtech said:
wow scott. how did
your post count
get so high?
-
I'm about to start working my way through "Sams Teach Yourself SharePoint Foundation 2010 in 24 Hours". That's Sams Publishing, not Scott Alan Miller, sadly.
My biggest concern about Sharepoint is how to stop it getting out of control. This may not be a problem at somewhere like NTG, as you're mostly all IT guys. But in a typical SMB, IT skills are relatively low. I like order and structure and will spend a lot of time getting things right, but many other department heads are more laid back. I think it will be very easy for Sharepoint to become a sprawling, dis-organised free-for-all.
My book doesn't address this.
-
@Carnival-Boy
When I first started rolling out sites (again SMB level), I didn't let the site get out of control because rights were fairly restricted. I didn't allow personal sites and each sub-site was created only after discussion. It wasn't because I was power hungry. I just wanted to prevent the sprawl. It worked very well. Since you can roll out new things, whether it be a calendar, a new list, or even a sub-site, I don't feel this control process interferes with company needs or productivity. -
@Carnival-Boy said:
My biggest concern about Sharepoint is how to stop it getting out of control. This may not be a problem at somewhere like NTG, as you're mostly all IT guys. But in a typical SMB, IT skills are relatively low. I like order and structure and will spend a lot of time getting things right, but many other department heads are more laid back. I think it will be very easy for Sharepoint to become a sprawling, dis-organised free-for-all.
SharePoint would definitely spiral out of control if you give end users the ability to create their own sites and stuff. Few companies do that. Most use IT as a gateway and make end users request new sites or pages through IT. This keeps the sprawl under control and allows for central governance. At NTG, as an example, no one has ever requested a page and internal IT makes the entire collection of sites and organizes them. It's all pre-planned and very structured.
For example, we make one "site" for each division: HR, management, general "whole" company, IT, Software Engineering, Client Services, etc. About seven or eight of them. Each has the same basics but with slight variations depending on need. Some are globally visible (IT and CS are available to all staff to see, SE only to the development team to keep things tidy for other people, management only to executives, etc.) People without access to a site literally don't even know that it exists, its tabs in the menus vanish so they don't even know that they are missing anything.
Each site has its own wiki and document repository for those teams' documents. Some have calendars (like IT has a group calendar to put IT related events on like scheduled maintenance.) Some, like CS and IT, use SharePoint's database exposure features to maintain client information, asset tracking, datacenter organization, etc. in a highly organized fashion that can be consumed by other services or other parts of SharePoint when needed to keep things really well organized.
You can lock down any section. If you use a wiki, for example, you can control who can read but also who can write there. So maybe you have the whole company able to read the HR wiki full of benefit information but only HR staff can edit it to update that information.
-
@scottalanmiller said:
SharePoint would definitely spiral out of control if you give end users the ability to create their own sites and stuff. Few companies do that. Most use IT as a gateway and make end users request new sites or pages through IT.
Oh, right, that's not what I was led to believe from talking with some Sharepoint consultants. I had it in mind that department managers would manage their own sites and not be a drain on IT resources.
-
@Carnival-Boy said:
@scottalanmiller said:
SharePoint would definitely spiral out of control if you give end users the ability to create their own sites and stuff. Few companies do that. Most use IT as a gateway and make end users request new sites or pages through IT.
Oh, right, that's not what I was led to believe from talking with some Sharepoint consultants. I had it in mind that department managers would manage their own sites and not be a drain on IT resources.
Would really depend on the department manager. You CAN do that, and it can work.
-
Indeed. The first two departments I'm looking at implementing Sharepoint in are HR and QA. By the nature of their roles, these two managers are highly organised and already have good manual document control in place that they want to replicate in Sharepoint. Sharepoint effectively becomes the Quality Manual that we're audited on for ISO certification (do you have ISO in the US?). It's a lot of work, and I want the majority of it to be carried out by them, not me. They know more about what they're trying to achieve than I ever could.
But if you let them have control, how to do you prevent other departments demanding control of their own sites? I'm sure I'll figure it out.
-
@Carnival-Boy said:
@scottalanmiller said:
SharePoint would definitely spiral out of control if you give end users the ability to create their own sites and stuff. Few companies do that. Most use IT as a gateway and make end users request new sites or pages through IT.
Oh, right, that's not what I was led to believe from talking with some Sharepoint consultants. I had it in mind that department managers would manage their own sites and not be a drain on IT resources.
An option, of course. But not one that I would recommend. Non-IT people lack the oversight, training, taxonomy and other disciplines to do this alone.
