Just like how you can add tags within the control panel to label specific users, is there anyway to add the same type of tags from within the buildfire SDK?
No. This is locked down due to security reasons.
However, you can set up behavioral Tagging via the control panel that may achieve what you need.
Example: You want to unlock lesson plan Level-2 only after the user completes Level-1. You can set up a "Congratulations/Text" plugin that Tags any users that lands on it with "Level2". You cannot navigate to this plugin anywhere on the app except after you have finished the last step in the lesson plan. Once this tag has been assigned you can then unlock the Level-2 lesson plan.
I hope this helps.
Related
When I started to have a lot of build pipelines it has become more comfortable to use 'Folders' view instead of 'Recent'. But it is too annoying to switch it all the time. Is it possible to configure 'Folders' view be default one? Thanks.
As far as I know, this is not possible.
What might help you is enabling the new preview feature for Multi-stage pipelines. To do this, click your profile picture on the top right, click 'Preview features' and enable 'Multi-stage pipelines'.
This new view doesn't allow you to set the default view to folder view. However, it does give you the option to select 'Folder view' on the top right (next to the search box). This changes the URL, which enables you to create a bookmark that starts in Folder view automatically.
Your URL should look something like
https://dev.azure.com/{organization_name}/{project_name}/_build?view=pipelines&option=folders
Is it possible to make 'Folders' view default in Azure Pipelines?
Agree with rickvdbosch, we could not set the 'Folders' view as default, at least for now.
Some other communities raised the same requirement earlier on the Developer Community, and this requirement has been passed to product team, you can check the details from the ticket:
Builds - Pipelines should default to the folder view if you have one or more folders
Note:You can vote and add your comments for this feedback. When there are enough communities vote and add comments for this feedback, the product team member will take this feedback seriously.
Hopw this helps.
I'm using a 3CX v12 phone system and I would like to add to the Snom 300 provisioning template so that the Cancel button is mapped to RETRIEVE. From the web interface of the phone I can see that the setting is for "idle_cancel_key_action!: keyevent" and I'd like to change it to "F_RETRIEVE" in the provisioning template. But when I look at the current template in order to edit it, I don't see where that setting is.
I can change it on each phone using the web interface, but I'd like to automate it using the provisioning template.
What can I add to the template so that this is done during provisioning, and where in the template do I add it?
I figured it out. I added this at the bottom (but still inside) the phone-settings tag:
<idle_cancel_key_action perm="">keyevent F_RETRIEVE</idle_cancel_key_action>
That worked perfectly. I hope this may help others in the future.
Jono
I'd like to side-step some of the security filtering done by Plone but only for people with manager or site admin roles. I want regular members to be able to add content but that content should still be filtered. Specifically at this moment I'm looking at allowing iFrames for manager role but this question is also more generic. The access to Plone that I'm referring to is a person editing a site page through Plone's standard editing system, TinyMCE.
If you look at the TinyMCE code you'll see that it load some configuration from the server. through the safe_html tranform inside the portal_transforms tool (
see https://github.com/plone/Products.TinyMCE/blob/11b957652846679cf7f441cc956730bd6fc92f87/Products/TinyMCE/utility.py#L499).
You can simply patch the getValidElements method above (adding here some user permission checking before removing/adding stripped tags) but it's not enough: this will simply change TinyMCE behavior (client side) but an evil user can access your site with TinyMCE disabled (really simple to do, just disable JavaScript in the browser), then upload a custom HTML without those filters.
So: the best thing to do is to customize the safe_html transform with the same permission checking. The simple way to add new stuff here withouy monkey-patching is to register a new plone.outputfilters adapter as described here: https://pypi.python.org/pypi/plone.outputfilters#adding-a-custom-filter
Simply patching safe_html will not work for several reasons:
html is not only filtered on save but also on display. That means that admins would see your iframe but normal users would not.
The filter is only executed once at the first display and then cached for one hour. Adding code that distinguishes between roles would have no effect on the second visitor.
I have a specific requirement where-in I want only the uploader of the document and a specific team to be able to view it in list / library. 1) is it possible? 2) If yes, how...?
Ok. So I was able to resolve my issue with the steps mentioned below. Soon will be documenting it in form of a blog and share it:
Created the document library and modified the default view to only show documents that were created by/modified by [Me].
Added a new web page to the library and gave exclusive rights to access that to a certain set of users.
Restricted all users from creating a view with the help of creating special permission level where user only had access to upload or delete a document but not creating/updating/deleting lists/views. Also disabled private view creation.
Hope this may be helpful to others too who are looking for restricted views / disabling view creation.
You need to set item level permission through event handler:
http://www.chakkaradeep.com/post/SharePoint-ndash3b-Setting-Item-level-permission.aspx
http://msdnvietnam.net/blogs/quang/archive/2009/07/02/sharepoint-eventhandler-set-item-level-permission.aspx
#Ashish, in SharePoint 2007 GUI you cannot make a query that will show documents that belongs to a specific group, however CAML specification supports it (Membership tag), it wasn't documented until SP2010, but it works on SP2007 (i'm using it)
However this involves custom coding and this doesn't assign permissions automatically, it just enables you to filter documents by groups.
For a solution without custom coding you could consider making a seperate folder/list for every person/group and set permissions to folder/list accordingly. This will also help performance - it's better to have permissions set on high-level container than having fine grained permissions (i'm just assuming that, because i read everywhere that mass fine-grained permissions are bad for performance)
You may use current user filter web part to filter the document by whom logged in into the sharepoint site by passing the value Dispaly Name
How can I disallow adding item or document to a list or document library? Due to some other feature scenario I cannot break role inheritance and have custom permission set for the list. Today, we restrict the addition using event handler (Item adding) – but this leads to poor UX.
Is there a way to have Role inheritance for a list and still have a base permission mask? Something like, allow everything that parent web offers but not X,Y,Z. Breaking role inheritance in the traditional way introduces the problem of explicit User and role management. Having a SPGoup hold an another SPGoup could help here, but that too is not possible. Let me know your suggestions.
I think you are asking to allow a user to have add permissions to the list but not actually be allowed to add to the list. Event receiver is going to be the best way. The only other solution I can think of is to use a custom item form that will do the check.
You can solve your problem by creating a webpart with the below functionality.
Identify the logged user is in admin group. If he is not in that group ganarte a javascript alert that "you have no permission for add new item" and redirect to (location.href="") allitems.aspx page.
And place this webpart in Newform.aspx page.
(add &toolpaneview=2&sharedview=true in in Newform.aspx url for editing page)
Hope this helps. Let me know if you need more help.
Create an IHTTPModule and subclass the context AuthenticateRequest event.
In the AuthenticateRequest routine you can inspect what type of action is happening and then redirect the user to the SharePoint "Access Denied" page. This is exactly how SharePoint does this functionality so the UX experiance would be the same.
If you want my opinion I would go with the way SharePoint handles permissions out of the box and break role inheritiance. Sure it will add new complexities to your life. But, I think you can better manage these complexities with the SharePoint Admin Toolkit and some custom built utilities for managing permissions. I think that is a better solution than what you are trying to do.
Am I missing something here when I suggest: Just hide the toolbar (or specific button) in the view page? That's an painless CSS hook done in the view page or SharePoint Designer
If you are using a custom List Template, you could create a custom View Toolbar Template. However, you probably will not want to use this on an OOTB List Template and it doesn't look like this will work on an existing list.
Even if you implement this, I would still leave the Event Receiver in place in order to prevent URL spoofing.