Require login for only certain forums/articles
I see that there is a way to make the entire tender require a login to be visible. Is there a way to only make certain sections require a login?
We want to make the vast majority of our KB open to the public but the use case I am thinking of is a download area or a partners section.
Thanks!
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by rick on 29 Dec, 2009 06:02 PM
We don't have anything like that available. It's a possibility... However, this is not a highly requested feature so it's not on our roadmap currently.
2 Posted by Adam on 29 Dec, 2009 06:05 PM
No problem at all Rick. Thanks so much for getting back to me.
We love the app and will be signing up for your middle tier of service
shortly (we have done quite a bit of work in the trial).
Thanks,
Adam
3 Posted by rick on 29 Dec, 2009 07:25 PM
Cool. Just so you know, we support the ability to turn off our FAQ feature and plug in the URL to your own FAQ site.
rick closed this discussion on 29 Dec, 2009 07:25 PM.
Adam re-opened this discussion on 29 Dec, 2009 07:27 PM
4 Posted by Adam on 29 Dec, 2009 07:27 PM
We love your FAQ functionality so we will definitely be using (we just signed up for a paid account by the way).
One more quick question on permissions. Is there a way to make the tender site visible to the public but require a login (not just a form submission) to submit comments/topics?
We like everything to be visible but I am not sure we would want non-clients to post.
5 Posted by rick on 29 Dec, 2009 07:39 PM
Not really. We've gotten that request before though, and may end up
adding a config option for it. In your case, why would it be public
if it's for clients only? You want the FAQ to be public or something?
We try to keep the permission system dead simple, but we do get a few
odd questions like this one. We just have to balance these requests
with the added complexity in code and QA time that things add.
6 Posted by Adam on 29 Dec, 2009 07:42 PM
We like it to be public for a few reasons:
No worries on the permissions though. We'll use it either way. If you do get more requests for it, we'd be in favor.
Thanks.
rick closed this discussion on 30 Dec, 2009 02:00 PM.