HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: How to implement a confidential category?
Use "Roles and permission" in dashboard. Either by having a member role(lvl1) and then giving some members a support/staff role(lvl2) - that way permissions stack for lvl 2 members. (Lvl1 have 1 role, lvl2 have 2 roles, lvl1 and lvl2) Or By having lvl1 have lvl1 role and lvl2 have lvl2 role. Adjust permissions accordingly.… -
Re: How to implement a confidential category?
Permissions is a great idea but not sure how to do it. We want all members to have private access to their own discussions with staff as well as public access to general discussions with other members. One way to do this is to specify which discussions each type of request displays to whom. Grant permissions to the… -
How to implement a confidential category?
Hello We recently installed Vanilla 3.3 as an intranet. Yesterday I set up another as an extranet for our staff and their customers as most are now working from home. Private messages and conversations are just not suitable, so we need a confidential category. There was some advice in a previous discussion about setting up… -
Re: How to implement a confidential category?
Coming at Vanilla from a standing start writing a plugin is not so easy. Looking at class.hooks and class.discussionscontroller I am beginning to see the way ahead. However I would appreciate some advice on how to include or exclude certain categories from a list of discussions. To clarify, the aim is to have to have a… -
Re: How to implement a confidential category?
Many thanks for your reply, Bleistivt. Conversations: we want to avoid PMs, mark discussions as resolved, and generally use the forum features. Yes, I agree about leaving permissions alone. A quick fix to introduce the business logic you aptly describe (users can create, but only view their own discussions) is to suppress…
5 results