SharePoint Server 2016 https. I want username with site action menu based on permission as below, Thanks. Tuesday, March 26, 2019 1:22 PM. Understanding SharePoint Site Actions. What is Sharepoint Site Action Menu? This is a feature that grants access to the functionality of Site Actions like permitting page editing or displaying a new RibbonBar (when using SharePoint 2010). Share Point 2010 has allowed more control to developers, through a site action menu and its features.
Recently i faced this issue that 'Readers' (people with read permissions on site) were unable to see 'Site Actions' button on site but it was working fine for Contributors and above levels. Readers were able to see the ribbon on other sites even any subsite in the problematic site. I checked for Master Pages, Page Layouts or any custom code like CSS or JS made by any champion in my team which can hide it from Readers but everything looked fine to me. So i decided to nail it.Following the basic rule 'Divide a problem into sub-problems and then solve one by one' i started checking for permissions and finally found the issue.
The reason was ,my business users (who were not SP professionals) played with site settings and permissions configurations that resulted in 'Site Actions' visibility lost for readers. I followed the below steps and issue resolved for me.
- Click on 'Site Actions -> Site Permissions'
- On the ribbon select the 'Permission Tools' tab and press the 'Permission
- Levels' button under the 'Manage' group on the far right
- Click on the 'Read' Permission Level
- Scroll down to the 'Personal Permissions' section and check the box for 'Manage Personal Views - Create, change, and delete personal views of lists. Press the 'Submit' button
Original Source : http://bernado-nguyen-hoan.com/2013/05/10/visitors-cant-access-ribbon-for-publishing-pages-in-sharepoint-2013/
Hope it save someone's day.
Happy SharePointing :)
Extra Tags:
#How to hide 'Site Actions' in SharePoint 2010 without code change or JS/CSS
#How to hide 'Site Actions' in SharePoint 2013 without code change or JS/CSS
#How to hide 'Site Actions' in SharePoint 2010
#Site Actions not visible for Readers in SharePoint 2010
#Site Actions hided by default in SharePoint 2010
Create A Sharepoint Site 2016
#Hiding Site Actions Menu Items without CSS![2016 2016](/uploads/1/1/8/5/118503889/612450148.jpg)
#Hiding Site Actions Menu Items without JavaScript
#Hiding Site Actions Menu Items without Change in Master Page05 Oct 2016 | SharePoint 2016
One of the top feature requests from day one on sharepoint.uservoice.com is Administration Auditing. The idea behind administrator auditing was that actions administrators took against the farm, creating a new Web Application, deleting a site via Remove-SPSite, changing property bag values, and so on, would be logged by SharePoint. This would allow a team of SharePoint Administrators to know who is doing exactly what and when. I’ve managed quite a few farms where there multiple SharePoint Administrators, from “tier 2” to SharePoint Architects. There are quite a few instances where it would have been helpful to know who did what, exactly. The SharePoint Server 2016 Administrative Actions Log, formerly announced for release in the November PU with Feature Pack 1, is a start in the right direction for my feature request. We’ll see a couple examples of how you might use this.
To start with, to use this functionality you will need two things: The November PU and a Usage Service Application. Administrator Actions logging stores the data in the Usage database using the 31 day retention period. Like other data written to the Usage database, the Administrator Actions logging has 32 tables; dbo.AdministrativeActions_Partition0 through dbo.AdministrativeActions_Partition31. These tables can be queried directly or query the view AdministrativeActions directly, which provides a condensed view of all tables.
Let’s move onto SharePoint. When an administrator action event occurs, it is first logged to the file system of that particular SharePoint server. This will be at the location where your Usage log files are under the AdministrativeActions folder. By default, this is located under C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions16LOGS. When actions take place, they’re logged to a .usage log. For this example, SP05-20160926-1542-20160926-15420.usage is the name of the log. It is actually just a plain text file with human readable information. But this isn’t the way we’ll interact with it.
The SharePoint Management Shell offers a way to query and sort Administrative Actions via the
Merge-SPUsageLog
cmdlet. This is a generic cmdlet for querying Usage logging information, but is fairly easy to use. To query the Administrative Actions log, simply use:From there, we can also pass in the
-StartTime
, -EndTime
, or -Servers
parameters. If you do not pass in the -StartTime parameter, the cmdlet will query data from the previous hour only. So let’s look at an example of creating a new Web Application. Now, this process creates a lot of entries in the Administrative Actions log, so I won’t show all of them, but this will give you a general idea of what the data looks like.Based on this, we can see the User who performed the action (me!). There are a lot of filters we could use here, such as
Merge-SPUsageLog -Identity 'Administrative Actions' | ?{$_.User -match 'trevor'} or Merge-SPUsageLog -Identity 'Administrative Actions' -StartTime 9/20/2016 -EndTime 9/27/2016 | ?{$_.ActionName -match 'UserPolicy'}
. Pretty simple to use and get relevant data out of the logging.What does it cover? This is a very high level list of what is covered as not all actions that you may think flow under these high level actions are logged, but a great portion of them are.
And the verbs associated with one or more of the above actions.
Create New Sharepoint Site 2016
In the above example I provided, we can see
Administration.WebApplication
is the action with New
as the verb, giving us Administration.WebApplication.New
as the Administrative Action.Hopefully this post helps with understanding what the Administrative Actions Logging is as well as how to use it. While Administrative Actions Logging doesn’t exactly match up with my original request, I’m sure the SharePoint Product Group will get there!
Sharepoint 2016 Site Owner
Trevor Seward is a Microsoft Office Apps and Services MVP who specializes in SharePoint Server administration, hybrid scenarios, and SharePoint Online. He has been working with SharePoint for 16 years from SharePoint 2003 on up, managing environments with terabytes of content for 150,000+ user organizations. Trevor is an author of Deploying SharePoint 2016 and Deploying SharePoint 2019. You can find him on Twitter and in /r/sharepoint.