As we were preparing to go live with our solution, we realized we should write it all down so we wouldn't forget anything. Then we realized it might be good to share the process with anyone who might be following this story.

The Environment

Our environment complicates our solution a bit, so it might help to explain it. Many of the steps below can be eliminated in a more "typical" situation.

The first installation was for a support group whose siteA logically grouped set of content - also web site. is pretty much only available to members. The "expert" was someone who had made some presentations to the group, but does not, herself, meet membership requirements. So the expert had to be kept out of most areas of the siteA logically grouped set of content - also web site., yet allowed to get to enough to be able to answer the questions. This required a new role be defined and locked down.

The siteA logically grouped set of content - also web site. already uses TAC_Lite for access control. That was some help. Another help is that the navigation is split into three separate blocks that are controlled by visibility settings.

Step-by-Step

Some of these steps may seem obvious, but I'm including them because this article stemmed from my own planning sheet.

1. Upload the latest versions of the modules.
• FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered._Ask
• FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered. (-dev version because of new features)
• Subscriptions
• Taxonomy_Image (with patch).
2. Enable the modules.
3. Turn on the taxonomy_image wrapper option.
4. Create the "expert" role.
5. Upload expert's picture.
6. Add new term to FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered. categories. Also taxo-image. Note term number.
7. Add the expert user.
• Basic settings.
• Assign to "expert" role.
• Add subscription for new FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered. category.
8. Review Access Control. Expert needs:
• access comments
• access content
• access siteA logically grouped set of content - also web site.-wide contact form
• edit faqFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered.
• view faqFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered.
• answer question
• access taxonomy images

Add "ask question" to "authenicated users" so members get it too.

9. Review FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered. settings. Make sure "use categories" is set.
10. Set up FAQFrequently Asked Question - most web sites get questions; the owner may collect the frequent ones to be easily asnwered._Ask settings
• Choose roles.
• Select users.
11. Create the "Ask the Expert" menu item (term number from above).
12. Disable the "Ask a Question" menu item.

The process is really not that different than most new moduleAn add-on, or extension, to Drupal to provide additional functionality; written in PHP. installations. We needed to be careful here because of the security concern. You probably already do most of the steps above anyway; you've just never written them down.