9 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Adminwss (Admin, Web-Site-Scripts.com) commented  ·  March 17, 2010  ·  Flag as inappropriate  ·  Delete

  ErikR
  That's already available. You just make an article restricted and select all groups. After update it will work in the same way.

• ErikR commented  ·  March 16, 2010  ·  Flag as inappropriate  ·  Delete

  Here's something else we'd like to see. The ability to make a specific article viewable to anyone who has access to the knowledge base (guest or front-end login), or have the article restricted based on log-in status.

• ErikR commented  ·  March 05, 2010  ·  Flag as inappropriate  ·  Delete

  I would say the easiest way to set would be to just have a Front End / Back End access setting that can be applied to a user group.

• Adminwss (Admin, Web-Site-Scripts.com) commented  ·  February 25, 2010  ·  Flag as inappropriate  ·  Delete

  Mark
  It will work pretty like you've described.
  Any ideas on how to make access by client accounts easier to manage? Currently we are planning to use the same group system that we got now, so access to each article and category can be managed separately by editing its properties. This article gives some insight about how it works and has several links to different usage scenarios:
  http://www.web-site-scripts.com/knowledge-base/article/AA-00440/37/

• Mark Coppock commented  ·  February 23, 2010  ·  Flag as inappropriate  ·  Delete

  The sooner the better on this feature. We're going to be implementing soon, and this is exactly what we need. We will not allow public (i.e., anonymous) use, all users must login. But, it would be great to be able to avoid inadvertently giving client users the ability to access the backend. Anything that can be done to make access by client accounts easier to manage (e.g., not having to create a group to provide access to client-only materials) would also be welcome.

  I'm fairly new to the solution, so I can't comment that specifically. But this will be a great feature!

• ErikR commented  ·  December 28, 2009  ·  Flag as inappropriate  ·  Delete

  As long as you can restrict client accounts from editing articles, that looks great to me.

• Adminwss (Admin, Web-Site-Scripts.com) commented  ·  December 21, 2009  ·  Flag as inappropriate  ·  Delete

  We are going to add this as follows:
  There will be two type of users and groups: Staff (current users) and Clients. Clients are read-only users that are able to login to front-end only and are not able to login to back-end. Client Groups have only profile access permissions (view/edit) and category access restrictions.

  Any additional suggestions?

• JohnP commented  ·  December 04, 2009  ·  Flag as inappropriate  ·  Delete

  This would be very useful for us

• ErikR commented  ·  September 27, 2009  ·  Flag as inappropriate  ·  Delete

  That would be a HUGE benefit.