I have created a private Google Site for a university project and I only assigned several people to be able to access to this site. The thing is I want to know who actually comes in, access the site. Is it possible?
Google doesn't release any identifying information to Gadgets, which to my knowledge, is the only way to put some of your own code on a Google Sites page. Unless there is a built-in method, I doubt this possible. As David suggested, check https://webapps.stackexchange.com/ for information on what built-in functionality that may exist.
Related
This has somewhat being answered here, but it's very outdated and the links given do not apply, at least the 2nd link.
We have a full license for Office 365 Sharepoint and I want to be able to create a web-part (Page-Viewer) to place an internal hosted website in an iframe.
For some reason the web-part has greyed-out the Zone and I cannot change it to Left or anything else. Why?
Is it possible to allow external users to access our Intranet and internal websites via Sharepoint and how please?
Another one of those, "I should have looked further", for the answer!
https://support.office.com/en-us/article/turn-external-sharing-on-or-off-for-sharepoint-online-6288296a-b6b7-4ea4-b4ed-c297bf833e30
https://support.office.com/en-us/article/manage-external-sharing-for-your-sharepoint-online-environment-c8a462eb-0723-4b0b-8d0a-70feafe4be85
The features are there and available on Office365 to turn ON or OFF sharing of internal areas to external users. However, it is risky, not knowing really who's watching over the shoulders of people.
I have a bunch of documents for which I want to determine the public links. Reading https://support.google.com/drive/answer/2494822?hl=en says I can get a "Anyone with a shareable link".
However no matter what I do I cannot find that option. The only links I can get is for ".... in the Organisation" All I need to do is get the link so I can embed it in an iFrame on another site.
Can anyone give me any pointers. This is not obvious as I think the fact it is in a Google Apps environment is preventing me getting what I need.
If you do not see the option, likely your administrator has restricted sharing with outside sources. You will need to speak with your domain administrator to either change these settings, or to figure out an alternative method of sharing the document.
Your administrator can find this in Apps > Google Apps > Drive > Sharing settings in the admin console.
https://support.google.com/a/answer/60781?hl=en
We're planning to use Sharepoint 2010 as a CMS for a website we're building. This site will also have login functionality; and my boss suggested we use Sharepoint's user profile features to store user info (username, password, contact info, etc.) for the site. How is this better then say using a standard list or a database table somewhere? I'm looking into how this could possibly work; but has anyone here tried something similar? Any anecdotes about it you could share? Any constructive input is greatly appreciated.
Thanks,
Frank
You asked for anecdotes. I have an anecdote.
A while back, I was trying to set up a Sharepoint server that exposed users' personal pages to the Internet at large. We wanted to allow authenticated access, but not to require it; that is to say, normal users would have read-only access and additionally the ability to submit InfoPath form data to Sharepoint libraries created to receive the results. The users could thus post public information and create public surveys using Infopath web forms.
When I went to make access public, I ran into a few problems. The "unauthenticated users" option on the preferences page of the document library was greyed out, even when I was logged in with a super-admin account.
In the end, I had to do a little bit of URL hacking to make this work. I had to change "DOC" to "DOCLIST" in the URL I used to access the preferences page (not that exactly, but something like that) and then the "everyone" option became available. In other words, there was actually no official way to do what I was trying to do.
The whole thing left a really sour taste in my mouth about Sharepoint for Internet-facing sites. See also things like this. Sharepoint is really designed for Intranet use only. As an additional downside, it is much more resource-hungry than normal CMSen. A full Sharepoint install can, without a single user, choke a pretty powerful virtual machine. I can't comment on its scalability as I've never done a really large rollout, but I can say that the indexing service is pretty heavy on the CPU.
Seems to me that LDAP would be a better way to store information on users; if you're using Sharepoint, you've probably already got an AD infrastructure. AD stores user profile info in LDAP anyhow - what you see in "Active Directory Users and Computers" is just a glorified LDAP browser.
Here is my initial toughts:
PRO: It's "easy" to merge infomation from outer sources like your AD, to be stored with the "other" user information in order to be displayed using the same means.
CON: I haven't come across a FBA Membership provider for User Profile Store.
I'm currently planning the migration of a Microsoft Content Management Server (MCMS) website to a SharePoint 2007 publishing site.
The top-level site is a public facing, anonymously-accessible website. It will contain two areas which need to be protected with forms-based authentication - each of which will have a distinct set of users.
There is content in the current MCMS site which uses "Connected Postings", which is the ability to use content in multiple places without duplicating it. In SharePoint, a similar concept is supported via the Reusable Content list, but this doesn't span site collections.
I'm thinking that this should be a single web application with three site collections. 1 for the public facing site, and the others for the two protected areas. However, I'm not sure if 1 site collection can be anonymous, with the other 2 implementing different FBA authentication providers.
I'd like my Urls to be something like:
www.whatever.com
www.whatever.com/protectedarea1
www.whatever.com/protectedarea2
Without Url rewriting, this would be difficult to do with separate web applications.
If I end up having to go with 3 separate web applications in order to get authentication to work as desired, I will probably have to get creative with content deployment so as not to duplicate content during authoring.
Would appreciate any thoughts, thank you!
Don't do MCMS so cannot answer specific to that, see http://www.andrewconnell.com/blog/ for alot of info.
Microsoft has a bunch of different designs for extranets, http://technet.microsoft.com/en-us/library/cc263513.aspx depending on your needs. You can set it up as you are describing, forms are a little weak put their is some a better version available on CodePlex.
For the URLS, Sharepoint has a feature called "Manged Paths" that will do what you want. No URL rewriting needed.
Our setup is a site collection for extranet and internal, where most work is done. When finished they can publish it(does make an extra copy) to the public site. Some public sites are publish only sites where they have no interaction with non-account people, some are sites were they actually do most of their work and non-account people can make contributions. All are available under MOSS.
Thanks, that extranet link will be helpful when looking at separating the authoring environment from the publishing environment.
I was trying to implement two FBA membership providers on two site collections within the same web application. Doesn't look like I can do that, gonna try using the same membership provider with different roles.
I am working on a project that is replacing an old portal system (Plumtree) with sharepoint and we want to make the transition as smooth as possible.
One thing we are look at currently is taking all the gadgets (Plumtree term for WebParts) and making sure they appear in the same place on the users new MySite.
Plumtree holds this information in a simple table containing the user, page, gadget and position information. I want to find a way to automate reading this table and putting the new WebParts on the users MySite and not have to manually set it up for hundreds of users.
I'm told modifying Sharepoint tables in SQL Server directly is not a good option as it may affect our support arrangements, but if it saves doing this by hand then I would concider it.
Other options that spring to mind are creating a equivalent table and using API calls to load the WebParts the first time the user accesses their MySite.
Any better suggestions?
You are right, messing directly with databases are not supported nor recommended.
Unfortunately, there are not much ways to modify MySites, the best way I know come from the MOSS Team Blog: http://blogs.msdn.com/sharepoint/archive/2007/03/22/customizing-moss-2007-my-sites-within-the-enterprise.aspx
The way we did it was pretty much what is described in the link above (http://blogs.msdn.com/sharepoint/archive/2007/03/22/customizing-moss-2007-my-sites-within-the-enterprise.aspx).
Your best bet is probably to staple a Feature to MySite creation and have it poll the plumtree database, find the gadgets for that user, and add a 'Page Viewer' web part for each, pointing to the gadget's location. That said, you may want to reconsider blindly migrating all your plumtree gadgets into SharePoint. There may be much better 'SharePointy' ways to provide the functionality that your gadgets are currently providing.