1) Does everybody agree that this "Communication manager" is not only allowed to send e-mails but also able to manage forums, blogs and moderate comments? This sounds logical but I'm not sure if this is OK for everybody. Possibly, each contact with this role should also have additional fine tuning of access - so that site admin can define which communication areas are allowed - blogs, forums, e-mails.

2) Does this really deserve a separate Tab in top panel - like "Communication" - where direct access to send e-mails, drafts, blogs and forums is given?

Sounds like a good idea!

From talking to our clients it sounds like in many organizations there is typically a person who is in charge of all communications. Given that, I wonder if it would make sense to have a new separate top-level tab in the WA backend like 'Communications', e.g.:

- View sent emails and stats

- Send our emails and newsletters

- Posts on blogs

- Moderate/ post on discussion forums

Would appreciate thoughts on this.

Hmm... It's a good idea, but I can also see where the email role and the forum/blog role might need to be separated.

kimskim - also see http://forums.wildapricot.com/forums/308920-archive/suggestions/8833285-redefine-wa-admin-roles-6273

Yes, that's an even better idea because they're all part and parcel of the same thing. I like it.

This is a good idea and we have been hearing about this for some time - and thinking about this.

So far we are leaning toward creating a new role - 'Communications manager', somebody who would be able to send email balsts, manage forums and blogs.

What do you think?

Is it possible to separate out the ability to create email blasts from the "Membership manager" admin privilege? Our social chairperson and fundraising chairperson both need to be able to email the membership, but they don't need to be able to edit members' profiles, add new members and other functions related to being the Membership Manager.

I think having a separate admin privilege called "Create email blasts" or something similar would be perfect. That way, any administrator could have (or not have) email blast capabilities (some admins might ONLY have email blast capabilities and no other admin privileges, such as the secretary) without compromising the security and/or integrity of the membership database.

We've two members who take project requests from individuals, companies, and government entities, cut and paste these RFPs into emails and send them to our membership. It would be terrific to set them up as Communications Adminstrators so they don't have access to change other parts of the site.

On a going forward basis, would also want this administrator level to be able to initiate polls/votes/surveys and the things associated with that roadmap item.

This sounds like a good idea. Let's see what others say.

I would like to recommend an "Email Manager' as a Restricted Access option. This person would be responsible for draftng and sending email blasts to the general membership and/or contacts.

I would not want this person to have administrative access to view or modify other parts of the website (such as finances, invoices, etc).

By adding en Email Manager as a 'Limited Access' administrator, there would be:

1) no need to export member/contact lists from WA to a third party.
2) no need to sync/manage multiple databases.
3) a centralized email history maintained through WA's email log
4) template management/continuity.