New answers tagged user-accounts
SharePoint itself only "authorizes" account access so it has to be aware of the authentication source you use. In this case that is Active Directory. So any account you use must exist in Active Directory. The exception is if you have Anonymous access enabled - in which case SharePoint will grant access to any user or service requesting data from it. ...
There is no need to use $expand operator if you don't need to return the projected fields. The following REST endpoint demonstrates how to filter by Author Id: /_api/Web/Lists/getByTitle('Tasks')/items?$filter=(AuthorId eq 12)
You are missing ID in expand. The query should look like: _api/Web/Lists(guid'id')/items?$select=Id,Author/ID&$expand=Author/ID&$filter=(Author/ID eq 21)
I'm not sure I understand the question exactly, but if you mean showing a different top nav, left nav, and web parts per user it's probably easiest to use the "Target Audience" functionality on the individual navigation links & web parts. With that, you can use AD groups, SharePoint groups, or even individual usernames to show different content on the ...
On premises you can use this: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventreceivertype.aspx In Office 365 You can in theory create an app that will handle the administration of those groups for you. However you'd have to hide the original permission management page (master page changes).
Top 50 recent answers are included