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
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 would like to give only read permission for a user to entire intranet site. The user must be able to read all the list and libraries in all the sites and subsites. I saw posts related to giving permission for a specific list or library but I didn't see any post related to giving read permission for the entire intranet site. I'm using SharePoint 2013.
Thanks
If you mean Read access to everything in a single site collection, then that is hard to give generic advice to because assorted list, libraries and subwebs can have broken the permission inheritance such that it would be impossible for an outsider to tell you which groups this person needs to be a member of.
Now if you mean you want a user to have Read access to all site collections within a web application, then that is absolutely something that can be accomplished and it is very easy too. That is done via something called: Policy for Web Applications - https://technet.microsoft.com/en-us/library/ff608071.aspx
I have a search set up on my Intranet. I have not allowed certain libraries and lists to be crawled (this helps eliminate the need for so many crawl rules). However...I do need some crawl rules in place, which I added. I ran the Full Crawl and the "excluded" items from the crawl rules still showed up.
I believe this is because my administration account has full control, but I don't know how to fix it.
I went in to add another account to the service (Manage Service Applications under Central Admin - Administration tab) and the only option it gives me to select is "full control".
Under the main site accounts (Manage Web Application link on Central Admin) the user I added says full read.
Now then On the main Search Service Page there is an account called "Default Content Access Account". I changed that to be the account that is Full Read from the administration group of the manage web application page. I then cleared the indexing and ran the crawl fresh. The crawl rules are still ignored. Does anyone have any thoughts on this? I am very perplexed.
Well, I never was able to fully solve the issue. I did go into each list and library and under advanced settings selected 'No' for the search being able to crawl it. Though this solution will only go so far.
I still have the issues in my document libraries of the /Form/* content showing up in a search (Which only show up if you search for an item that also appears on the MasterPage).
Anyway, I can live with this half fixed as it is.
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.
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.