Restrict Users to Specific Presentations

  • 1
  • Idea
  • Updated 3 years ago
  • (Edited)
As Rise is a simple CMS system, it would be beneficial if Rise would add a simple function to allow administrators to protect presentations or assign users to specific presentations. 

In a simple scenario at a youth-focused non-profit, perhaps I have the following slides - 
  1. Traffic*
  2. Weather*
  3. Program Info
  4. Program Calendar* (from Google Cal)
  5. School Calendar* (from Google Cal)
  6. Highlighted Students
  7. Highlighted Volunteers 
In this case, only presentations 3, 6, & 7 would need regular changes by assigned staff.  All the others (with *) I would want to protect from edits.

In the simplest form, this would be done either manually marking specific presentations as protected (and adding just one user role 'protected publisher') or (slightly more advanced) manually assigning specific editors/publishers to specific presentations  -  

In my very simple case, I've done this by assigning people I do not wish to have access to all the presentations to sub-companies and then linking the presentation within the subcompany to the main company.  

Unfortunately for Rise, this means I'm not purchasing items like storage as I do not wish to purchase them twice for the same task of running the display or two at my organization.

If we were to expand our service a bit, I could see us partnering with local schools to provide a  parent info display for their use (with an occasional blurb about our organization every now and then as well).  There I would understand setting each school up as sub company and I could justify the added Rise storage cost to allow each school to manage their own media separately from ours, but then the school would still likely want to protect or assign certain pages to specific users as well.
Photo of Biologyben

Biologyben

  • 3,558 Points 3k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
BiologyBen,

Interesting idea, but this isn't in our development scope at this time.

I'm curious, couldn't you also just assign specific users as Content Editors, and others as Publishers? Only those Publishers can publish the content, while the Editors can edit it. The only difference I see is everyone can see all Presentations, but only Publishers can affect what is on the Display. Just a thought, thanks!
Photo of Biologyben

Biologyben

  • 3,558 Points 3k badge 2x thumb
Except I want to restrict specific presentations from being published (or edited) by people who are allowed to publish and edit other presentations.

By adding the flag for administrators to 'protect' content, it allows this granularity without resorting to sub-companies.

I don't care much if they can see the presentations, I just don't want them messing with them ;-)

As a work around - If I were to make the other staff 'editors' within the same company, is there a way for Editors to notify Publishers in rise that they feel the presentation is ready for publication?  If not, then editors must communicate that via some internal process to the Publisher that would likely get fairly overwhelming if more than a few editors were at work and making changed regularly. 

I'd think developing a full approval workflow would be more complicated than creating a flag to protect presentations where changes are not needed. 
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
Biologen,

That is not a protection of course, but meanwhile you could add something to the name that would indicate it is not to be edited or is in the process of editing. Also, You could simply add some bright-colored placeholder on top stating the status of this presentation, but make it invisible and not-published to any display.
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
BiologyBen,

Thanks for the clarifications. At this time there is no way for an Editor to inform a Publisher that content is ready for publication inside the platform. 

Interesting idea though!