Control access level for specific gadget on a page - e.g. show some gadgets to specific membership levels only
Improving the process of restricting/allowing access to 1 screen.
Currently it is a complex process that often results in unanticipated results . . . or inability to properly configure that ultimately requires technical support. The process is not intuitive.
It is not easy to manage access to a gadget by membership level and/or group when a gadget is on a page that may or may not be restricted by membership level and/or group.
Allow setting permissions and access by membership levels and/or groups for pages, and for certain gadgets on one page. And make the selections obvious and intuitive so conflicting options can not be selected. Where options and/or conflicts exist the user should be presented with appropriate feedback for making informed selections E.g. Error messages or tips or tutorials or helpful information.
Erica Peterson commented
We would like permission settings on gadgets to restrict them to membership levels (similar to pages). This would allow us to keep many of our pages public (so anybody could see that we have a "document library" page for example) but anybody who isn't a member or isn't logged in would see a login prompt instead of the content of the gadget.
I would like to be able to have a button or content displayed only if logged in. Is there a cookie or variable that is set that I can check/use for that?
Georg Reichard commented
I'd like to add to this discussion as we'd also need an option to restrict for "public" view only - e.g. a page/gadget that is only visible until you are logged in.
I tried to emulate what you ask for by creating two duplicate pages, with different restriction settings - but there are two challenges:
1) if you make changes to the "identical" content, you need to do this in both instances
2) if your other page/gadget is only to show up for public users, there is no option to hide this page when users are logged in - so they see both.
Currently the "public" actually means "all" and is not a restriction - we would like to see a "Public only" as an option of a restriction for gadgets/pages.
This site provides a great example of how content (such as a webinar) is only visible to members, yet the (landing) page is public: http://www.hci.org/content/webcasts
Harvard Business Review is another example of a site that restricts certain content to members while providing "teaser preview" to the public.
Voting on this feature on behalf of some of our clients and potential Wild Apricot clients who expressed interest in this behavior.
Dale Koetke commented
Evgeny, an important use case is that I have content that I want to reuse periodically. For instance only have a widget reminding members about an activity in the two weeks before the activity. As it is now, I need to re-write such content each time (or copy out the source, save it somewhere and paste in back in to a new widget -- way too many steps!)
Dale Koetke commented
It would be great if I could leave a gadget on a page, but hide it from the public, as a way of enabling me to easily bring it back when I want to. Now I need to completely re-create it.
Keith Rice commented
Our Problem is that we would like a search gadget on the Home Page but unless I am mistaken the access levels for this page do not work the same as others. The gadget itself does not provide restrictions so it is visible to the public.
Great idea! One step closer to "dynamic" content pages......
Evgeny Zaritovskiy commented
We have it already for pages - you can define a page access per level and/or group.
So, is it about setting up more granular access within a page to specific pieces of information (gadgets)? Can you provide an example why is this important?
Dmitry Buterin commented
Thank for posting. It would help us evaluate this if you could describe a more detailed and specific example of how this would be used.
Hi, I would like to request that we be able to show members-only blocks of content (instead of whole pages).
For example, we may want everyone to see a page, but non-members to see content pieces A, B, and D, and members to see A, B, C and D when they log in.
This would be helpful in communicating different messages to different kinds of users.
Dot Net Nuke has this kind of functionality, in case that helps http://www.ace-dnn.com/knowledge-base/dnn-module-security-permissions.aspx