Simple Content Approval Process

Edit Subject

This is why I love this forum. Awesome and simple idea. Any other takers?

Hmmm... I like the simplicity of that idea. Unfortunately for us, we could have students go for a while with no issues and then, maybe a friend "borrows" their laptop, where they have their credientials cached, and posts something inappropirate. Or, maybe there's an innocent typo that, should it go through, would be an embarrassing. "Varsity Baseball Team Captain Surpasses 500 Hats", or worse. Under the current system, if someone abuses the priviledge of posting content, you can (I assume) simply kill their account.

We would rather have a second pair of (adult) eyes on content beforegets broadcast to our community.

Thanks.

Entech let me know if I have your idea right or not. From what I can tell Entech is suggesting is that you would give the role that can publish content only to those that are authorized to make that decision. Janderson in your situation you would only give this to a Teach or two who would be able to make those updates. Students wouldn't have the ability to "publish" their revisions. Only Teachers, assuming they are the only ones that have that role, would be the ones that can do this.

Let me know if I have the idea right and that I understand the school situation correctly. Thanks

Exactly so in this case, you would just not give the students the ability to publish. Only certain teachers/admins would have the ability. The students can edit the presentations to their hearts content and when ready a teacher would have to review and hit publish before the presentation would roll out to the screens.

This works because you would give the student a different login with different rights and abilities. The teachers would have there own login with the additional credentials to publish the content.

I personally like this idea. "Publisher" as a role would be helpful. I have heard from a couple clients that having no line of control for updating displays is a downside to the new system. This would be a very simple fix, and I think would satisfy the majority.

All, thanks for the feedback. The following is how I propose that this work:

The existing Content User Role name is changed to Editor and we add a new User Role called Publisher.

An Editor can edit Presentations but they have no access to the Publish button in the Editor and they cannot create or edit Schedules.

A Publisher can edit Presentations, they have full access to the Publish button and they can create and edit Schedules.

For greater certainty an "Editor" cannot publish what they create or schedule it with a Presentation. Only a Publisher can do that.

When we deploy all existing Users with the role of Content will have the name changed to Editor and we will also give them the Publisher role so that they don't lose access.

Does the above make sense to everyone?

We currently have a release in development right now that will take to the end of February. When that is done we will tackle this. Many thanks for the very simple suggestion Entech! The comment internally has been "now why didn't we think of that" ;-).

Cheers

This sounds like the solution we've been looking for. Thanks Entech! I also know of at least one other school, with the same requirements. They are currently researching digital signage solutions. I'll pass this info along to them as well.

Thanks everyone!

Everybody,

I'm glad to announce that this functionality has been introduced.

You can read all about it here.

Thanks!