I have a large list of projects with project dates both projected and actual. I want to share all the dates and all the projects with our internal team, but want to limit the access of our external contractors to just those projects their company is assigned to complete. I tried managing the content with folders and permissions, but discovered that because my company does not have access 2007, that function is not completely enabled. Does anyone out there have any idea how I can do this?
Thanks
Few facts
Setting permissions and folders do not have anything with Access 2007.
You cannot use folders on custom lists only with Document Libraries and Form libraries
In your scenario the best option is to have custom, item level permissions for each project:
to do it manually check this
to do it automatically you should create a workflow with SharePoint Designer. Here is an activity to do that.
In case you have just a few projects do it manually otherwise configure a workflow to do that.
You could add a dataview webpart to any sites the external companies can access. Each webpart can be configured to filter on the information they are responsible for by the metadata field.
Related
I want to create a Subsite in Sharepoint Online within a site that was automatically generated via a MS Teams team but the option to do so doesnt exist.
The option to create Subsite seems to ONLY exist if a Site was created from within Sharepoint Online.
I can understand that a workaround would be to create it as another Site within Sharepoint Online and then link the relevant Sites together under a HUB.
Am I missing something or this feature does not exist in Sharepoint Online unless I create the Subsites as Sites and then link them up via a Hub?
Thank you in advance for the help.
There is a setting in the SharePoint Online Admin Center to Hide or Show the create subsites option.
Microsoft is discouraging the use of subsites, and the creation of subsites is likely to continue to be phased out as more features and capabilities are added to Hubs. While there are still exceptions to the rule, since there are still aspects that Hubs cannot accomplish (like connecting Hubs together to a parent Hub), you should seriously consider building your solution to use separate site collections.
Depending on how the rest of your SharePoint environment is architected, a better approach would be to setup that team site as a hubsite, then create the additional site collections you need, and link it to the new hubsite. This way you kind of mimic the subsite structure ( but not all its features ) while preserving every site independent.
For more information on best practices on SharePoint site Architecture, see https://learn.microsoft.com/en-us/sharepoint/information-architecture-modern-experience.
I want to create my first SharePoint App. I am wondering, is it possible to create an app which will create SharePoint site and will build a structure (with a few lists and libraries) on this site?
Yes is possible. It depends what are your business requirements. I mean based on what rules you want to create the site (SPWeb)? Most likely you would need to create a WebPart (which is similar to a UserControl ASCX in ASP.NET) and put there the interaction with user. Then, if the sites to be created has usually the same lists and libraries and so on I would suggest you to create a Web template which contains these things and then simply create a Site based on that web template...
I can provide you some further examples if you want...
I have a calendar on a SharePoint 2010 site and I have created a custom site template based on the standard meeting workspace. I'd like to force users to only be able to use my custom template.
One option is to add Hidden="TRUE" in webtemp.xml for all other meeting workspace templates - this will leave mine as the only option. This, however, works on the farm level and I'd like to keep the templates available for other web applications. If I can do this on a web application or lower level it will do the trick.
Even better solution - if I can make the new event dialogue skip the step altogether and use my template without asking.
Background:
My custom template only contains security customizations, no UI or content changes. I want to impose it as I have requirements for the permissions of the meeting workspaces which are different from the parent site - so inheritance has to be broken. But I can't think of another way to supply default permissions other than by using a site template for the workspace.
Site Settings > Look and Feel > Page Layouts and Site Templates
choose the site templates you want to be used in the site, this can inherit all the way down the site collection or you can start in a subweb.
Is there a way to have a newly created SharePoint 2010 Site have default permissions (ie have an Active Directory group already on it).
I am using TFS 2010 and it creates a SharePoint 2010 site for new projects. But I then have to remember to go into the project and add permissions. It would be nice if I could have a default AD Group that always goes in the site. (It would be cooler if I could use TFS Groups that are specific to the project, but I realize that is asking a bit too much.)
The quickest thing that comes to mind is to create a feature that adds the permissions you need and associate it with a site template with feature stapling.
This will allow you to effectively have the permissions added automatically when you create a new site from that template. If you want more dynamic functionality regarding which security groups get added to your SharePoint groups, you could build this into the feature receiver.
You could try adding the group and members from webservices
http://msdn.microsoft.com/en-us/library/ms774470%28office.12%29.aspx
http://msdn.microsoft.com/en-us/library/ms772683%28office.12%29.aspx
Why do I need to create Multiple SSPs in MOSS?
My manager (sharepoint administrator) asked me to create another SSP which he wanted to use for TOP Management users. He didnt tell me what was the reason for it.
I was wondering what all scenarios we need to create Multiple SSPs. Any ideas?
Very vague question, please add more info!
And as a general answer, you don't need to, the concept is to share the services under the SSP between multiple web applications, what scenario do you have to need to create more than one?
Edit after question update:
An SSP host the services that will be used ( consumed ) by any associated Web applications. These services include :
Profiles
Audiences
Business Data Catalog Connections
Search and Indexing
Single Sign On
Excel Services
Usage Reporting
Source
So if your manager won't actually have something special on any of those services, I don't see a reason to do it. We had a customer once that needed the entire mysite and profiles customized, so we created a SSP just for that one web application.